Manage all your requirements across your project
The Requirements Editor enables you to view, create, and manage all your requirements across your project. 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
Model-Based Systems Engineering Support
While developing architecture models in System Composer, you can directly capture, view, and manage system requirements using Simulink Requirements. System requirements can be linked to different architecture model elements to establish a digital thread between requirements and architecture. The completeness of the architecture can be analyzed with requirements coverage analysis. While analyzing the architecture model, additional requirements can be derived and linked to the model.
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 System Composer, 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.
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 requirements management tools supporting that format such as Siemens Polarion® ALM™ or Jama Connect™. 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.
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 maintain 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.
Establish a digital thread by creating requirement links to model elements, MATLAB code, data dictionaries, Stateflow elements, System Composer architecture models, and other requirements. You can link requirements and test cases, test harnesses, 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 DO-254) 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.
View Implementation and Verification Status
Simulink Requirements provides implementation and verification status of requirements 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.
The requirements coverage 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.
Requirements Traceability Matrix
To manage links between large sets of requirements, models and tests, the traceability matrix summarizes the traceability in a consolidated matrix view. Each cell shows where there are links between artifacts to identify gaps. Using filters, you can scope the view to focus on specific items of interest to help manage large sets of data. You can highlight items that are missing links and view links with requirement changes to understand the impact of the change. To address gaps in coverage, you can add links between items directly in the traceability matrix.
Generate Requirement Reports
For reviews and documentation, you can create a configurable report that includes links, change information, and implementation and verification status. With Simulink Report Generator customized reports can be created.