Key Features

  • Requirements Editor for requirements authoring, editing, and organization
  • Requirements Perspective for viewing, linking, and managing requirements within the Simulink® graphical editor
  • Requirements import and synchronization from third-party tools such as Microsoft® Word® and Microsoft® Excel®
  • Change tracking and differencing to automatically identify and manage changing requirements
  • Consolidated status metrics for requirements implementation and verification
  • Reports documenting requirement attributes, traceability, and status
  • Bidirectional traceability between requirements, designs, generated code, and tests

Simulink Requirements™ enables you to work with requirements in your Model-Based Design environment to make it easier to communicate and trace requirements with design, code, and tests. Requirements and their rationales can be described with rich text including images, numbered lists, and bullets. Additional attributes such as ID, keywords, revision information, and comments enable you to refine and detail your requirements. Custom attributes let you extend requirements with your unique requirement data types.

The Requirements Editor enables you to view, create, and manage all your requirements across multiple models. It includes:

  • Requirements browser to organize hierarchies of requirements
  • Links view to manage links across the project
  • Property Inspector to view and edit details of requirements and links
  • Customizations to configure column display and sorting
  • Search tool to filter large sets of requirements
  • Report generation to document requirements

The requirements browser provides a tabular view of requirements associated with the model. You can see a summary of requirements information such as attributes, implementation status, and verification status. Requirement sets let you organize requirements in hierarchies with multiple levels of nesting. For example, a requirement set might contain high-level user requirements and another requirement set contains software requirements. A requirement set is stored as a separate file, and you can use Simulink Projects to manage file versions. Links are stored in a separate file, which enables you to establish traceability between requirements, design, and test without modifying the source or destination.

A demonstration of Simulink Requirements™ to enable the requirements traceability, consistency checking, verification, and reporting required to support high-integrity workflows.

Requirements Editor for creating, editing, and organizing your requirements.


Work with Requirements and Models

The Requirements Perspective provides a single view where you can view, author, and organize requirements while also performing your design activities in Simulink or Stateflow®. The perspective includes:

  • Embedded Requirements browser to view requirements associated with the model
  • Requirements Property Inspector to view and edit details of a requirement or link
  • Badges to indicate blocks or states with requirements links
  • Requirements annotations to show requirement details on the diagram

Requirements Perspective, for managing requirements within your Simulink development environment.


Establish Traceability with Drag and Drop

You can create links between requirements and your design by dragging a requirement from the requirements browser and dropping it on Simulink or Stateflow model objects. A badge appears on the model object to indicate a link and enables navigation to the linked requirement. You can choose to display the requirement and its connector on the model diagram from the badge.

The Requirements Perspective allows you to view, edit, link and organize requirements from within Simulink or Stateflow.

Import and Synchronize External Requirements

Requirements from other sources, such as IBM Rational DOORS, Microsoft Word or Microsoft Excel, can be imported as read-only references or for further modification within Simulink. You can use the Requirements Interchange Format (ReqIF) to import and work with requirements from third-party tools supporting that format. During import you can control the mapping of fields from the external document into Simulink Requirements. You can specify to import fields mapped to custom attributes to match the content in the external document. A synchronize operation maintains consistency with the referenced requirements. If a requirement change occurs, notification is given to let you assess the impact of the change.

Change detection to alert you when requirements imported from external documents are changed. 


Identify and Respond to Changes

When a requirement changes, it is important that it be communicated across the team to avoid downstream errors. Each requirement and link maintains revision history of when it was modified. Simulink Requirements detects changes in requirements linked to models, including those imported from external sources, enabling you to assess the impact of the change on your designs and take appropriate action. You can perform a differencing operation on a requirement set to view changes in requirements.


Trace Requirements to Design, Code, and Test

Requirements traceability with other tools in the development lifecycle is provided, including code generation and testing tools for bidirectional navigation from requirements, design, implementation, and test. You can link requirements and test cases, test suites, and test sequences in Simulink Test™, and access links from the Simulink model or the Test Manager. Code generated from Embedded Coder®, HDL Coder™, or Simulink PLC Coder™ can be hyperlinked from the code generation report to the requirements. These links are presented as comment labels in the code. The hyperlinks in the code generation report provide direct navigation from code to requirements.

You can link and trace Simulink model elements to requirements in IBM® Rational® DOORS® or IBM® Rational® DOORS® Next Generation.

With DO Qualification Kit (for DO-178) and IEC Certification Kit (for ISO 26262 and IEC 61508), you can generate a traceability matrix spreadsheet showing requirements-to-model-to-code bidirectional traceability paths and file information.

Traceability between requirements, Simulink and Stateflow objects, and test artifacts across the development lifecycle for impact analysis and documentation.


Track Status of Model-Based Design Activities


View Implementation and Verification Status

Simulink Requirements provides implementation and verification status of requirements within Simulink to identify gaps in implementation, missing requirements, or errors in the design. Implementation and verification metrics quantify the proportion of requirements that have been implemented in the design and associated with test cases, as well as the proportion of test cases that have passed.

These traceability and verification metrics quantify the completeness of your development activities in Model-Based Design. The status metrics are displayed as a column in the requirements browser with colors indicating status. A requirement with child requirements is not completely implemented or verified until all its child requirements are implemented or verified. Hovering over the status displays cumulative metrics for the requirements and its child requirements. If there are missing links in the status, it indicates where the implementation or verification needs to be completed.

Justifications can be linked to requirements that are not implemented or verified in the model. For example, a nonfunctional requirement can be linked to a justification to filter it from the status. A common set of justifications can be shared and reused within the model.

Viewing status of implementation and verification status to gain insight into project status. 


Generate Requirement Reports

When a requirement changes, it is important that it be communicated across the team to avoid downstream errors. Each requirement and link maintains revision history of when it was modified. Simulink Requirements detects changes in requirements linked to models, including those imported from external sources, enabling you to assess the impact of the change on your designs and take appropriate action. You can perform a differencing operation on a requirement set to view changes in requirements.