Simulink Verification and Validation

Tracing Requirements to Models, Tests, and Generated Code

The Requirements Management Interface in Simulink Verification and Validation lets you link Simulink and Stateflow objects to text in requirements documents. It supports requirements stored in IBM® Rational® DOORS®, Microsoft® Word, Excel®, PDF, or HTML files. It can be customized to support additional document types and requirements management systems.

Requirements Traceability 1:51
Connect models, tests, and code with requirement definitions, using Requirements Tracebility interface in Simulink Verification and Validation™.

Creating Links

Links are references in the model that point to external documents. They are associated with model blocks unique identifiers that ensure robustness and persistence of requirements traceability information.

Requirements traceability lets you select a requirement object or bookmark in an external document and create a link via context menus in Simulink. In the Requirements dialog box you can apply keywords and descriptions to links for a more targeted analysis.

Requirements Management Interface context menu and Requirements dialog box.
Requirements Management Interface context menu and Requirements dialog box.

Reviewing Designs and Requirements

The Requirements Management Interface lets you highlight blocks in the model or generate a requirements report that combines images of model subsystems with information from requirements documents. You can customize report templates using Simulink Report Generator.

In conjunction with IBM Rational DOORS, Simulink Verification and Validation lets you replicate Simulink links as link objects in DOORS, enabling bidirectional traceability without the need to modify requirement documents. The Requirements Management Interface synchronizes your links in DOORS and Simulink. As a result, you can create links in IBM Rational DOORS or IBM Rational DOORS Web Access and then synchronize them with Simulink models.To ensure that your requirements links are consistent with their source documents, you can run requirements consistency checks that identify removed or modified requirements. These checks can be combined with other Model Advisor checks for systematic analysis of models.

Reviewing Code

Using Embedded Coder, HDL Coder, or Simulink PLC Coder to generate code from your models enables you to include requirements labels as comments in your source code and as hyperlinks in the code generation report. Hyperlinks in the code generation report provide direct navigation from code to requirements.

Visit the MathWorks Connections Program for third-party requirements management solutions that support the Requirements Management Interface and provide linking and traceability.

Annotated source code, created with Real-Time Workshop Embedded Coder, showing hyperlinks to requirements.
Annotated source code, created with Embedded Coder, showing hyperlinks to requirements.
Next: Complying with Modeling Standards

Try Simulink Verification and Validation

Get trial software

Best Practices for DO-178 Compliant Software using Model-Based Design

View webinar