Simulink Requirements

[Clint Callas]

Youcan formalize requirements and analyze them for consistency, completeness, and correctness using the Requirements Table. The Requirements Perspective enables you to view and manage requirements together with design. When used with Simulink, you can create links to blocks with a simple drag and drop.

What Is Requirements Toolbox?

You can use Requirements Toolbox to author, import, and validate requirements in MATLAB and Simulink, track their implementation and verification status, and quickly respond to requirements changes.

Work with Requirements and Design Using Requirements Perspective

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

Create a digital thread that links requirements, model elements, MATLAB code, data dictionaries, test cases, and test harnesses. Trace to external requirements tools. Include links in code generation reports from Embedded Coder.

Specify formal requirements using logical expressions with the Requirements Table block (3:53) in Simulink. Use simulation to validate these formal requirements and perform analysis of correctness, consistency, and completeness. Bind formal requirements to design models for verifying compliance. Generate tests with Simulink Design Verifier linked to the corresponding requirements.

Use the Requirements Perspective to view, author, and organize requirements directly in Simulink, System Composer, or Stateflow editors. Create links by using drag and drop without modifying the model, use badges to view where links in the model exist, and annotate diagrams with requirements.

Identify gaps in implementation and testing, missing requirements, and design errors. Use the Traceability Matrix to review links between large sets of requirements, models, and tests; then, address gaps by adding links.

Create, manage, and navigate traceability links between individual lines in your MATLAB code, requirements information in external documents and test cases in MATLAB Test. Highlight traceability in the MATLAB editor to identify gaps in implementation or testing.

You can create, view, and organize hierarchies of requirements. Requirements from external sources can be imported and bidirectional traceability established. You can exchange data with other tools using an industry-standard interchange format.

Establishing full lifecycle traceability with Requirements Toolbox enables you to document that requirements are being met, understand the impact of any changes, and bidirectionally navigate between requirements, designs, generated code, and test cases.

In this tutorial, you use the Requirements Editor to create a requirement set, organize related requirements, and add requirements to the set. If you have Simulink, you can also use the Requirements Perspective to author requirements without leaving the Simulink Editor. For more information about using the Requirements Perspective, see View and Link Requirements in Simulink.

If you do not specify a custom ID, the Requirements Editor numbers requirements in order. Custom IDs enable you to use your company standards for labeling requirements and to set the numeric order. (Custom IDs cannot contain a # character.) You can also use an ID to help locate a requirement when searching. Keywords aid in searching for a requirement.

On the Edit field toolbar, in either the Description or Rationale fields, click the icon. Save the changes to your requirements content within Microsoft Word to see them reflected in Requirements Toolbox.

You can view or hide columns in the Requirements Editor when you click Columns > Select Attributes. Add, remove, and reorder attribute columns in the Column Selector. The view configuration is saved across sessions. You can export view settings to a MAT-file by using the slreq.exportViewSettings function and import them by using the slreq.importViewSettings function. You can reset view configurations by using the slreq.resetViewSettings function.

To filter for requirements for which a specific attribute has a specific value, type the attribute name, followed by a colon (:), then the value. For example, to filter the contents to display only the requirements where the Summary attribute has a value that includes Aircraft, enter Summary: Aircraft (alternatively, you could put the whole string in quotation marks to enforce case sensitivity).

We've tried synchronising the Simulink model with our SysML Model in Modeler, but so far we have only achieved to import entire modules and their i/o flows. Is there a way of importing Simulink items below the "Module" level, so that one can see the actual functional model created in Simulink in Modeler? We would then like to be able to link the Simulink blocks (say a certain switch or gain block) with the requirements they satisfy.

As a next step, we would like to synchronize the "linked to" information back into Simulink, such that the items in the functional model might show a label "satisfies Requirement Req_123" or something along those lines. Do you think that is feasible?

Thanks for your reply, and I'm sorry if I wasn't quite clear about Modeler LC Manager. We are using the Modeler only, and thus want to link requirements we have in the Modeler (imported from our RM tool) to Simulink elements. There is a Simulink Synchronizer Tool within the Modeler, but so far we haven't gotten very far using it. However, at least it seems that later versions of Matlab are supported.

One possible option (requiring product customization) would involve Asset Library with a Simulink import. This would show the Simulink blocks as e.g. SysML parts, allowing to link them with requirements. However, this does not exist and would need to be implemented based on the file interface of Asset Library.

The new Polarion Connector for Simulink allows for a much-improved user experience over earlier versions of the connector. For the first time, Polarion itself has been directly embedded into the Simulink desktop client to support a larger set of customer use cases and reduce inconvenient App context switching.

Working with the Simulink Requirements Toolbox

Also, another first for the new connector is that it will work with the Simulink Requirements Toolbox. Users can then use the popular drag-and-drop approach to create traceability between requirements and model elements. Then, depending on the connector settings, surrogate Simulink items can be created in Polarion for any linked model elements. These surrogate Simulink items are rich in information too with block parameter data and where applicable model diagrams. The integration automatically links the surrogate Simulink items back to the original Polarion Requirements as well.

Extending the supported use cases even further, users can work with Polarion Live Documents directly or across the entire Polarion project scope. When working with Polarion LiveDoc documents it is possible to work with document baselines or earlier revisions.

Backward compatibility with older releases of the connector

To maintain backward compatibility with earlier connector releases, the new connector also supports publishing and direct linking to existing Polarion Work Items and Requirements. This mode can work with or without surrogates Simulink items as well.

The connector allows you to execute Simulink Tests, collect results, and publish these back to Polarion in the form of a Test Run and Test Record. This can all be done directly from the connector control panel.

With adding support for Simulink Test, we can leverage Polarion's powerful Quality Management capabilities. Polarion becomes a one-stop place for all your Test Management and Test evidence of your Simulink models.

Changes for 3.1.0

New Features:

- Support the ability to map Polarion work-item types to Simulink requirement types (Functional, container, and informational)

- Added support for Polarion personal authentication tokens (PAT) for authentication with Polarion

- Added ability to customize how Simulink block information is presented and ordered in the Polarion surrogate item

- Added a new Start page configuration property to allow users to specify a start page URL for Polarion when Polarion first opens on the launch of the connector pane

- Added a new customizations folder to the installation that includes several customization scripts to support extended functionality. Please refer to the folder for more details

Fixes:

- SC-503 - There is an [syntax] error shown when the user defines several configurations for the same server URL and calls Polarion Context Selector

- SC-464 - Optimize "Open in Polarion" behavior not to refresh Polarion views on each request

- SC-492 - Improve behavior of progress indicator on loading of LiveDocs

- SC-491 - If there is an explicit link between the "Import1" node and the top-level diagram, there is a warning in the console

- SC-466 - Extra parameters in URL (like 'hide_navigator' or 'selection=wi-123') may be considered as change of ReqSet configuration

- SC-465 - Fix issues with models, which keep linking data internally

- SC-451 - If problems (e.g., network connectivity) problems occur during "Refresh" - it may lead to an empty ReqSet and loss of all the links to it

- SC-449 - If there was an error during initial import to a ReqSet, there is no possibility to overwrite broken ReqSet

3a8082e126