Matlab Requirements Toolbox capabilities

Question

Esin 2022-8-23

回答： Paul Urban 2022-8-30

I would like to learn if it is possible with Matlab Requirements Toolbox to manage the followings:

reach history of requirements
define attributes for requirements (e.g., in order to define testing method, tagging as derived or not for safety evaluation, etc.)
take minor/major baseline to specific modules or full set of requirements from top
get the list of differences between any old baselines of the requirements
add table/chart/figure/state diagram to requirements or only verbal statements are allowed
provide bi-directional trace through sw requirements and model/code or tests/test results

Thank you, kind regards.

Answer 1

Paul Urban 2022-8-30

I will try to answer some of your questions.

I'm not sure exactly what you mean reach history, but requirements are stored as files and can be managed in a version control system, like MATLAB code or Simulink models would be. You can do differencing of these files to see the changes. See doc here: https://www.mathworks.com/help/matlab/matlab_prog/about-mathworks-source-control-integration.html
You can create your own custom attributes for requirements and links, see: Add Custom Attributes to Requirements and Add Custom Attributes to Links
Requirement sets are stored as files. You would manage requirement sets with your Source Control tool to take baselines.
You can get differences between requirements and link sets using the Compare Revisions (Simulink) tool.
You can add images to the Description and Rationale field. You can use Word as the editor for the Description and Rationale for more control over the formatting of these fields. See this documentation.
Yes, there is bi-directional traceability from the requirement to the model and then to the generated code with Embedded Coder, see Generate Code for Model with Requirement Links You can also create links to test cases in Simulink Testor defined with MATLAB Unit Test. You can also generate reports that contain traceabillity information to requirements, models and tests that includes hyperlinks to the respective artifact.

Paul