Loader

Ni Requirements Gateway Download

Ni Requirements Gateway Download

The secret to capturing traceability relationships is the use of request IDs. A common practice for documenting requirements is that they contain an identifier as well as textual information that describes the requirement. NI Requirements Gateway looks for request ID references in cover documents, such as TestStand sequences or LabVIEW VIs. The basic idea is similar to what is shown in Figure 6 above. Later in this document, we will describe some of the standard interactions of NI Requirements Gateway with NI requirements management, documentation, testing, measurement, and control software. In many cases, there are standard syntaxes for specifying that a CVI, LabVIEW VI, or TestStand step covers a requirement. In any case, this default interaction can be adjusted if necessary. In addition to collecting requirements and traceability information, NI Requirements Gateway provides a navigation between a selected item in NI Requirements Gateway and the appropriate specification or application. In the event that changes need to be made to the source code in response to a change in requirements, this navigation makes it easier to locate the desired section code. If the system requirements change REQ_ROM in the sample project in this section, you must return to the NI TestStand step that covers this requirement to verify that the requirements are still met or to make any necessary changes. Your TestStand sequence can contain hundreds of steps. When you choose Navigate from the shortcut menu, as shown in Figure 7, NI Requirements Gateway starts TestStand, opens the appropriate sequence file, and runs the ROM step. With multiple project documents potentially containing hundreds of requirements, the graphical view in Figure 5 could become very large and complex.

You can simplify the graphical display by choosing to display only selected relationships or documents. In addition to several views to analyze your application requirements, NI Requirements Gateway provides a variety of reports. These reports document various aspects of the project. These reports are based on customizable templates. NI Requirements Gateway also allows you to take snapshots of projects at different stages of development. These snapshots capture the current state of a project and can be used to document changes in requirements coverage and progress of development projects. This file contains important information about NI Requirements Gateway 2018, including system requirements, installation instructions, new features, bug fixes, and known issues. For more information about new features, compatibility, known issues, and fixes for earlier versions of Requirements Gateway, see What`s New in Requirements Gateway in NI Requirements Gateway Help. If you want to stick to basic software to document your needs, NI Requirements Gateway can scan text files for traceability information. In this case, your documents must conform to a formal syntax so that the software understands what it contains. NI Requirements Gateway comes with several sample projects and files.

With these examples, you can see first-hand how the software interacts with supported requirements documents. Now that you are reasonably familiar with how the software handles requirements documents, let`s take a closer look at how NI Requirements Gateway interacts with National Instruments test, measurement, and control software. Most engineering projects start with high-level specifications, followed by more detailed specifications as the project progresses. Specifications contain technical and procedural requirements that guide the product through each stage of development. In addition, working documents such as hardware schematics, simulation models, software source code, and test specifications and procedures must comply with and cover the requirements defined by the specifications. Tracking the relationship between requirements and test, measurement, and control software is critical to validating implementation, analyzing the full impact of changing requirements, and understanding the impact of test failures. Performing this coverage and impact analysis helps engineers meet their requirements and streamline development efforts. NI Requirements Gateway is ideal for applications where complex components are simulated or tested against documented requirements in industries such as automotive, defense, aerospace, and consumer electronics. This document provides a brief overview of NI Requirements Gateway and how NI Requirements Gateway interacts with applications to collect traceability information. For more information about using NI Requirements Gateway, see the Getting Started Guide and the Software User Guide. The sample test sequence in Figure 18 covers the requirements specified in the sample Word document and the DOORS module in the figures above. The sequence file is part of a TestStand workspace.

As mentioned above and shown in Figure 19, NI Requirements Gateway displays the hierarchical structure of TestStand files and displays steps in step groups and sequences in sequence files. The sequence in Figure 18 is also part of the NI Requirements Gateway project in the first section of this document. In this first section, you saw that NI Requirements Gateway can retrieve traceability information from TestStand sequences and also information from TestStand results. While previous screenshots show NI TestStand and Telelogic DOORS, NI Requirements Gateway can also be used to collect traceability information from other software. You can use NI Requirements Gateway with the NI LabVIEW graphical development environment, LabWindows/CVI for ANSI C development, NI TestStand test management software, and MATRIXx design and development tools, as well as several popular requirements management and documentation tools such as Telelogic DOORS, IBM Rational RequisitePro, and Microsoft Word. You can use Microsoft Word to define formatting styles. If you use the default font, font size, color, etc., the style is Normal. If you make formatting changes, you can save those settings with a style name. One way NI Requirements Gateway interacts with Microsoft Word is by searching for text in specific formatting styles. Standard styles used by the software include Requirement_ID and Requirement_Text. When you use Telelogic DOORS for requirements management, your requirements are stored in modules in a database. There are two standard methods for NI Requirements Gateway to retrieve information from DOORS.

In one case, NI Requirements Gateway uses the native ID of an object. In the other advanced interface of DOORS, an attribute called ReqID is referenced. The DOORS module shown in Figure 9 can be used with the advanced interface and is used in the project presented in the visit above. LabWindows/CVI is a proven ANSI C test and measurement environment that dramatically increases the productivity of engineers and scientists. Engineers and scientists use LabWindows/CVI to develop powerful and robust applications in manufacturing testing, military and aerospace, telecommunications, design validation, and automotive. NI Requirements Gateway supports LabWindows/CVI 7.0 or later and provides all the traceability information and views you saw during the visit. NI Requirements Gateway searches for traceability information in source code comments and documentation fields in the function panel. You can use C and C++ comments in your source code to indicate that a requirement is covered. If the comment precedes a function declaration or is in a function definition, the function is assumed to cover or implement the request, as shown in Figure 16. The Traceability Information Collection section of this document explains the requirements and references to requirements in more detail. Let`s explore some examples of how you can document your needs. Specifically, it examines how NI Requirements Gateway interacts with requirements documentation and management tools.

The tools discussed in this section are not the only environments supported by NI Requirements Gateway. Instead, they are used to give you an idea of how the software collects information from your requirements documents. For the specifications of a Microsoft Word document, the requirements may resemble the document in Figure 8. Request IDs appear in blue (blue is optional, of course). Requirements Gateway allows you to specify applications, tests, and simulation models that correlate with documented requirements to capture traceability information. You can use Requirements Gateway to capture and compare project snapshots to see differences and see how requirements and coverage change over time. This application software integrates with LabVIEW, LabWindows™/CVI, and TestStand, as well as popular requirements documentation tools such as Telelogic DOORS, IBM Rational RequisitePro, and Microsoft Office. We are a community of sharing. Please help us by downloading 1 new document or by downloading us: Requirements Gateway 2018 is the upgrade release of Requirements Gateway 2014. Requirements Gateway is a requirements traceability solution that links development and verification documents to formal requirements defined in documents and databases. Requirements Gateway improves the quality of the development process by effectively managing requirements traceability and impact analysis throughout a project`s lifecycle.

For more than 20 years, engineers around the world have relied on the MATRIXx family of products for control design applications in automotive, aerospace and defense, process control and academic environments.