Requirements Management Interface

Using the Requirements Management Interface for QSS's DOORS

Overview of the Process

This diagram depicts how the Requirements Management Interface associates objects with DOORS requirements.

Figure 2-1: How the Requirements Management Interface and DOORS Work Together

Note The Requirements Management Interface and DOORS both use the term object, but each uses the term differently. In the Requirements Management Interface, and in this document, object refers to a Simulink model, Stateflow diagram, or MATLAB M-file. In DOORS, object refers to each numbered element in the exported formal module, sometimes called a surrogate module, for a Simulink model, Stateflow diagram, or MATLAB M-file. DOORS assigns each of these objects a unique object identifier. In this document, these objects will be referred to as DOORS objects.

Summary of Steps to Use the Requirements Management Interface

Step
Description

Start the Requirements Management Interface - see Startup.

In the Requirements Management Interface Navigator, open an object (Simulink model, Stateflow diagram, or MATLAB M-file) - see Opening an Object in the Navigator.

In the Navigator, synchronize the object with DOORS. Synchronizing causes DOORS to create an exported formal module for that project. This surrogate exported module provides the mapping from DOORS to the Navigator. See Synchronizing the Navigator with DOORS.

Create links between the surrogate exported module and other formal modules in DOORS. See Linking an Object to a DOORS Requirement.

For an object that has associated DOORS requirements, you can use the Navigator to:
See which nodes have requirements associated with them - see Indication of Requirements.

View only nodes that have requirements - see Changing the View in the Navigator.

Go to DOORS - see Going from the Navigator to DOORS.

Go to an element in a object - see Going from the Navigator to a MATLAB Object.

Indicate in an object which elements have requirements associated with them - see Highlighting Subsystems and Blocks That Have Requirements.

In DOORS, you can go from DOORS to an object - see Going from DOORS to an Object.

From DOORS, you can run a script in MATLAB - see Running a Script from DOORS.

Step	Description
	Start the Requirements Management Interface - see Startup.
	In the Requirements Management Interface Navigator, open an object (Simulink model, Stateflow diagram, or MATLAB M-file) - see Opening an Object in the Navigator.
	In the Navigator, synchronize the object with DOORS. Synchronizing causes DOORS to create an exported formal module for that project. This surrogate exported module provides the mapping from DOORS to the Navigator. See Synchronizing the Navigator with DOORS.
	Create links between the surrogate exported module and other formal modules in DOORS. See Linking an Object to a DOORS Requirement.
	For an object that has associated DOORS requirements, you can use the Navigator to: See which nodes have requirements associated with them - see Indication of Requirements. View only nodes that have requirements - see Changing the View in the Navigator. Go to DOORS - see Going from the Navigator to DOORS. Go to an element in a object - see Going from the Navigator to a MATLAB Object. Indicate in an object which elements have requirements associated with them - see Highlighting Subsystems and Blocks That Have Requirements.
	In DOORS, you can go from DOORS to an object - see Going from DOORS to an Object.
	From DOORS, you can run a script in MATLAB - see Running a Script from DOORS.

Highlighting Subsystems and Blocks That Have Requirements Startup