Coupling NI Requirements Gateway with LabVIEW

Publish Date: Aug 09, 2013 | 0 Ratings | 0.00 out of 5 | Print | Submit your review

Overview



Microsoft Access


Coupling Series Home


Unit Test Framework


Note: This document applies to NI Requirements Gateway versions 1.1 and earlier. For information on newer Requirements Gateway versions, refer to the Coupling External Applications with NI Requirements Gateway topic in the NI Requirements Gateway help.

NI LabVIEW graphical programming has been enabling engineers and scientists to more rapidly design, prototype, and deploy test, measurement, and control applications for over 20 years. With LabVIEW, engineers around the world can interface with measurement and control hardware to collect data, analyze data, and share results. Applications that implement requirements in LabVIEW can be integrated with NI Requirements Gateway in order to create a software link between specification documents and their LabVIEW implementations.

Table of Contents

  1. Including LabVIEW Files in an NI Requirements Gateway Project
  2. Specifying Coverages in LabVIEW
  3. Additional Resources

1. Including LabVIEW Files in an NI Requirements Gateway Project

LabVIEW documents are traditionally used to implement requirements rather than specify requirements, so LabVIEW documents will almost always be added to a project in the form of a covering document.

When adding a LabVIEW document to your NI Requirements Gateway project, the Select Files to Include in Document dialog box allows you to specify different types of LabVIEW files with one single document node.

Figure 1 - NI Requirements Gateway allows users to specify multiple LabVIEW documents within a single project node

When selecting multiple LabVIEW files within one document node that covers a specification document, the requirements set forth in the specification document are not considered covered unless the combination of all files cover the requirements (Boolean OR functionality).

Within the Select Files to Include In Document dialog box, you have the option of associating NI Requirements Gateway with a directory in which your LabVIEW files are located, in which case NI Requirements Gateway will include all *.vi, *.ctl, *.vit, *.ctt, and *.llb files in that directory in the project.  Furthermore, the user can add one individual LabVIEW file, which includes all of the previously mentioned file extensions in addition to LabVIEW project (*.lvproj) and LabVIEW library (*.lvlib) files.  Lastly, users can select individual *.llb files using the Add LLB button.  In the instance that the user adds a project or library file to the NI Requirements Gateway project, all associated files will be automatically included.  If the user chooses to add an *.llb file to the project, the Choose VIs window will allow them to select one or more VIs to analyze with NI Requirements Gateway.  You can <Shift-Click> or <Ctrl-Click> to select multiple files.

Figure 2 - When selecting to include a LabVIEW *.llb file, you can specify individual VIs to associate with the NI Requirements Gateway project

Figure 3 - An example NI Requirements Gateway Management View with LabVIEW covering documents

Password Lists

When the LabVIEW documents associated with the NI Requirements Gateway project include one or more password protected files, the Passwords button will allow users to configure a list of one or more passwords to try when accessing protected files.  Password lists streamline the analysis of protected LabVIEW files, as the user will no longer be faced with continued prompts for passwords upon every subsequent project reanalysis.

Figure 4 - Password lists simplify LabVIEW project analysis so that the user no longer has to input passwords upon every reanalysis

LabVIEW Type Variables

The LabVIEW type allows access to two project variables.

  1. Analyze Diagrams
  2. With Images

As of NI Requirements Gateway 1.1, users have the ability to optionally analyze block diagram elements.  Analysis of LabVIEW block diagrams extend the precision of requirements coverage options, as elements such as labels, nodes, and loops can contain references to requirements.  This option is not enabled by default, as choosing to analyze LabVIEW block diagrams may potentially slow project analysis.

Enabling the With Images variable will allow users to capture the front panel and block diagram images of project VIs.

Figure 5 - The Analyze Diagrams variable allows the user to specify whether LabVIEW block diagrams should be analyzed for references to requirements

Back to Top

2. Specifying Coverages in LabVIEW

When specifying coverages within LabVIEW files, syntax should be used.  The default syntax for specification of coverages in LabVIEW is as follows, where reqid is the requirement ID of the requirement being covered:

[Covers: reqid]

Figure 6 - VI documentation as a whole is only one location in which references to requirements can be stored

Coverage information can be stored in numerous different locations within your LabVIEW files, allowing for a vast array of options for referencing requirements in LabVIEW.  References can be stored in the following locations:

  1. VI Documentation (as seen in the above image)
  2. Documentation or label field for a control or indicator
  3. Documentation or label field for a block diagram function, node, or wire

Figure 7 - Block diagram element documentation and even loops can contain references to requirements

Figure 8 - Using NI Requirements Gateway, block diagram labels can specify portions of code that cover requirements

To simplify the coverage specification process, NI Requirements Gateway gives users the ability to copy requirements for coverage using LabVIEW.   When you select Copy For » LabVIEW Description Reference or Copy For » LabVIEW Text Reference from the right-click context menu, NI Requirements Gateway places the appropriate coverage string for the requirement in the system clipboard so that the user can simply paste the string into LabVIEW documents and no longer has to worry about the appropriate coverage string syntax.

Figure 9 - NI Requirements Gateway allows users to copy the syntactically correct coverage string for LabVIEW references

Back to Top

3. Additional Resources

NI Requirements Gateway

Requirements Management for NI Software (15 min. Web Demo)

LabVIEW and CMMI-Compliant Requirements Management

Managing Requirements and Developing Large LabVIEW Applications

Download Free Evaluation Software

 

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit