Introduction to Simulink Requirements

Simulink® Requirements™ integrates requirements authoring and management with your modeling environment. You can author requirements in Simulink in the Requirements Editor, where you can organize and manage them. You can also import them from Microsoft® Word or Excel®. For details, see Import Requirements from Third-Party Tools.

Link Between Requirements and Implementation

You can link from requirements to the Simulink blocks or Stateflow® objects that implement them. The connection is bidirectional, meaning that you can locate a requirement from a model element and a model element from a requirement.

You can:

  • See your progress toward implementing requirements, including identifying missing implementations.

  • React to requirement changes, for example, by updating model elements as requirements change, and clarifying requirements as your model evolves. With Simulink Requirements, you can find changed requirements by using a single command.

  • Ensure that changes that you make to the model conform to the associated requirement.

For more information, see Requirement Links.

Link Between Requirements and Simulink Test

If you have Simulink Test™, you can link between requirements and tests that verify them. You can associate a requirement or set of requirements with tests that you create in Test Manager. When you run a test in Test Manager that you linked to a requirement, you can see the pass/fail results in the Requirements Editor.

Because you can track test results in Simulink Requirements, you can see the progress toward verification. The verification status also helps you to identify missing information and clusters of requirements associated with failing tests. You can use this information to understand the impact and complexity of those requirements.

For more information, see Link Test Cases to Requirements Documents.

Additional Requirements Traceability Links

With Simulink Requirements, you can create several other types of traceability links and establish many relationships within your model and to external documents. You can create these types of traceability links:

  • Implements, in which a design element implements a requirement

  • Verifies, in which a test case verifies a requirement

  • Related to, in which you establish a trace relationship between a model element and a requirement

  • Derives, in which a requirement is derived from another requirement

  • Refines, in which one requirement refines another requirement

You can link between other types of documents, for example, HTML or DOORS® items, and requirements and to additional model elements such as dictionary objects.

For more information, see Requirement Links.

Share and Reuse Requirements

You save requirements files separately from your model files. You can then reference requirement files from multiple models, and each model can reference multiple requirement files. Saving requirements in separate files lets you modularize common requirements across models while also managing requirements that are model-specific. This approach avoids copy-and-paste errors and keeps the requirements in sync across the models that share them.

You can compare requirements files (.slreqx files) by using the MATLAB file comparison tool. This tool helps you to identify differences in similar requirement sets. For more information, see Compare Requirements Sets.

You can also include requirements files in your Simulink projects. When you open a project, you can load any included requirements sets into the Requirements Editor from the project explorer. For more information, see Manage Requirements Across a Team.

Another way to share information about requirements is to generate a report that includes the requirements definition, links, implementation details, verification status, and so on. For more information, see Generate Requirements Reports Using Simulink.

Related Topics