Create links between your requirements and various Simulink® model elements including blocks, Stateflow® objects, Simulink Test™ test objects such as test cases and test suites, Simulink data dictionary entries, MATLAB® code, and other requirements by using the linking capabilities available in Simulink Requirements™ to keep track of how your requirements relate to your model design.
You can create links to blocks and Stateflow objects directly from the Simulink Editor as you work on your model by dragging requirements from the Requirements Browser in the Requirements Perspective View. You can create links to Simulink Test test objects from the Simulink Test Test Manager or from the Requirements Editor. For more information on linking Simulink model elements to requirements, see Link Blocks and Requirements and Link to Test Cases from Requirements.
To keep track of how the various elements in your design are associated with your requirements, you can specify the link type for your requirement links. Link types also specify the nature of requirement-to-requirement links, such as where a requirement is derived from a higher-level requirement.
Simulink Requirements provides these link types.
|Related to||General relationship between requirement and model element. This link is bidirectional.|
|Implemented by||The model element implements the requirement and vice versa. These link types contribute to the Implementation Status metric.|
|Verified by||The verification model element or test case verifies that the requirement is satisfied and vice versa. These link types contribute to the Verification Status metric.|
|Derived from||The destination is derived from the source and vice versa.|
|Refines||The destination adds additional detail for the functionality specified by the source and vice versa.|
Links between requirements and your Simulink model elements have a source and a destination. Most of the link types are defined relative to the link direction. The Related to link type denotes a general relationship between two entities.
The Implements/Implemented by and Verifies/Verified by link types communicate requirement-model relationships. You must specify the source and the destination correctly for requirements with these link types because the Implementation Status and Verification Status rollup metrics are derived from these link types. For more information on the Implementation Status and Verification Status rollup metrics see Review Requirement Implementation Status Metrics Data and Review Requirement Verification Status Metrics Data.
Review your requirement links from the Links View. The Links View is available in
the Requirements Editor and the Requirements Browser in the
Requirements Perspective view. Toggle between the Requirements and Links Views by
using the View drop-down list in the toolbar. When working in
the Simulink Editor, you can review requirement links for individual requirements
by using the Property Inspector in the Requirements Perspective view. The Links View
of the Requirements Browser in the Requirements Perspective
view displays only the outgoing links from your source artifacts. Other links
associated with your requirements are available in the Links
pane in the Requirements View. All the outgoing links from a source artifact are
stored in a Link Set file (
In the Links View, unresolved links are denoted by a icon.