|
|
|
| R2012a Documentation → Simulink Verification and Validation | |
Learn more about Simulink Verification and Validation |
|
|
|
|
| R2012a Documentation → Simulink Verification and Validation | |
Learn more about Simulink Verification and Validation |
|
| Contents | Index |
| On this page… |
|---|
Creating a Default Requirements Report Reporting on Requirements in Model Blocks |
If you have a model that contains links to external requirements documents, you can create an HTML report that contains summarized and detailed information about those links. In addition, the report contains links that allow you to navigate to both the model and to the requirements documents.
You can generate a default report with information about all the requirements associated with a model and its objects.
Note If the model for which you are creating a report contains Model blocks, see Reporting on Requirements in Model Blocks. |
Before you generate the report, add a requirement to a Stateflow chart to see information that the requirements report contains about Stateflow charts:
slvnvdemo_fuelsys_officereq
Open the fuel rate controller subsystem.
Open the Microsoft Word requirements document:
matlabroot/toolbox/slvnv/rmidemos/fuelsys_req_docs/slvnvdemo_FuelSys_RequirementsSpecification.docx
Create a link from the control logic Stateflow chart to a location in this document.
Keep the demo model open, but close the requirements document.
To generate a default requirements report for the slvnvdemo_fuelsys_officereq model:
Select Tools > Requirements > Generate Report.
The Requirements Management Interface (RMI) searches through all the blocks and subsystems in the model for associated requirements. The RMI generates and displays a complete report in HTML format.
The report is saved with the default name, model_name_requirements.html. If you generate a subsequent report on the same model, the new report file overwrites any earlier report file.
The report contains the following content:
The Table of Contents lists the major sections of the report. There is one System section for the top-level model and one System section for each subsystem, Model block, or Stateflow chart.
Click a link to view information about a specific section of the model.
The List of Tables includes links to each table in the report.
The Model Information contains general information about the model, such as when the model was created and when the model was last modified.
The Documents Summary section lists all the requirements documents to which objects in the slvnvdemo_fuelsys_officereq model link, along with some additional information about each document.
ID — The ID. In this example, DOC1, DOC2, DOC3, and DOC4 are short names for the requirements documents linked from this model.
Before you generate a report, in the Settings dialog box, on the Reports tab, if you select User document IDs in requirements tables, links with these short names are included throughout the report when referring to a requirements document. When you click a short name link in a report, the requirements document associated with that document ID opens.
When your requirements documents have long path names that can clutter the report, select the User document IDs in requirements tables option. This option is disabled by default, as you can see in the examples in this section.
Document paths stored in the model — Click this link to open the requirements document in its native application.
Last modified — The date the requirements document was last modified.
# links — The total number of links to a requirements document.
Each System section includes:
An image of the model or model object. The objects with requirements are highlighted.
A list of requirements associated with the model or model object. In this example, click the target document name to open the requirements document associated with the slvnvdemo_fuelsys_officereq model.
A list of blocks in the top-level model that have requirements. In this example, only the MAP sensor block has a requirement at the top level. Click the link next to Target: to open the requirements document associated with the MAP sensor block.
The preceding table does not include these blocks in the top-level model because:
The fuel rate controller and engine gas dynamics subsystems are in dedicated chapters of the report.
The report lists Signal Builder blocks separately, in this example, in Table 3.3.
A list of requirements associated with each signal group in any Signal Builder block, and a graphic of that signal group. In this example, the Test inputs Signal Builder block in the top-level model has one signal group that has a requirement link. Click the link under Target (document name and location ID) to open the requirements document associated with this signal group in the Test inputs block.
Each Chart section reports on requirements in Stateflow charts, and includes:
A graphic of the Stateflow chart that identifies each state.
A list of elements that have requirements.
To navigate to the requirements document associated with a chart element, click the link next to Target.
If your model contains Model blocks that reference external models, the default report does not include information about requirements in the referenced models. To generate a report that includes requirements information for referenced models, you must have a license for the Simulink Report Generator™ software. The report includes the same information and graphics for referenced models as it does for the top-level model.
If you have a Simulink Report Generator license, before generating a requirements report, take the following steps:
Open the model for which you want to create a requirements report.
To open the template for the default requirements report, at the MATLAB command prompt, enter:
setedit requirements
In the Simulink Report Generator software window, in the far-left pane, click the Model Loop component.
On the far-right pane, locate the Model reference field. If you cannot see the drop-down arrow for that field, expand the pane.
In the Model reference field drop-down list, select Follow all model reference blocks.
To generate a requirements report for the open model
that includes information about referenced models, click the Report icon
.
The Requirements Management Interface (RMI) uses the Simulink Report Generator software to generate the requirements report. You can customize the requirements report using the RMI or the Simulink Report Generator software:
There are several options for customizing a requirements report using the Requirements Settings dialog box.
On the Report tab, select options that specify the contents that you want in the report.
| Requirements Settings Report Option | Description |
|---|---|
Highlight the model before generating report | Enables highlighting of Simulink objects with requirements in the report graphics. |
Show user tags for each reported link | Lists the user tags, if any, for each reported link. |
Use document IDs in requirements tables | Uses a document ID, if available, instead of a path name in the tables of the requirements report. This capability prevents long path names to requirements documents from cluttering the report tables. |
Report objects with no links to requirements | Includes lists of model objects that have no requirements. |
Include links to objects | Includes hypertext links from the report to model objects. |
Include details from linked documents | Includes additional content from linked requirements. The following requirements documents are supported:
|
To see how these options affect the content of the report:
Open the slvnvdemo_fuelsys_officereq model:
slvnvdemo_fuelsys_officereq
In the model window, select Tools > Requirements > Settings.
In the Requirements Settings dialog box, click the Report tab.
For this example, select Highlight the model before generating the report.
When you select this option, before generating the report, the graphics of the model that are included in the report are highlighted so that you can easily see which objects have requirements.
To close the Requirements Settings dialog box, click Close.
Generate a requirements report by selecting Tools > Requirements > Generate Report.
The requirements report opens in a browser window so that you can review the content of the report.
If you do not want to overwrite the current report when you regenerate the requirements report, rename the HTML file, for example, slvnvdemo_fuelsys_officereq_requirements_old.html.
The default report file name is model_name_requirements.html.
In the model window, select Tools > Requirements > Settings.
Show user tags for each reported link — The report lists the user tags (if any) associated with each requirement.
Include details from linked documents — The report includes additional details for requirements in the following types of requirements documents.
| Requirements Document Format | Includes in the Report |
|---|---|
| Microsoft Word | Full text of the paragraph or subsection of the requirement, including tables. |
| Microsoft Excel | If the target requirement is a group of cells, the report includes all those cells as a table. If the target requirement is one cell, the report includes that cell and all the cells in that row to the right of the target cell. |
| IBMRationalDOORS | By default, the report includes:
Use the RptgenRMI.doorsAttribs function to include or exclude specific attributes or groups of attributes. |
Close the Requirements Settings dialog box.
Generate a new requirements report by selecting Tools > Requirements > Generate Report.
Compare this new report to the report that you renamed in step 7:
User tags associated with requirements links are included.
Details from the requirement content are included as specified in step 9.
When you are done reviewing the report, close the report and the model.
To see a demo about including details in the requirements report, enter the following command at the MATLAB prompt:
slvnvdemo_powerwindow_report
If you have a license for the Simulink Report Generator software, you can further modify the default requirements report.
At the MATLAB command prompt, enter the following command:
setedit requirements
The Report Explorer GUI opens the requirements report template that the RMI uses when generating a requirements report. The report template contains Simulink Report Generator components that define the structure of the requirements report.
If you click a component in the middle pane, the options that you can specify for that component appear in the right-hand pane. For detailed information about using a particular component to customize your report, click Help at the bottom of the right-hand pane.
In addition to the standard report components, Simulink Report Generator provides components specific to the RMI in the Requirements Management Interface category.
| Simulink Report Generator Component | Report Information |
|---|---|
| Missing Requirements Block Loop | Applies all child components to blocks that have no requirements |
| Missing Requirements System Loop | Applies all child components to systems that have no requirements |
| Requirements Block Loop | Applies all child components to blocks that have requirements |
| Requirements Documents Table | Inserts a table that lists requirements documents |
| Requirements Signal Loop | Applies all child components to signal groups with requirements |
| Requirements Summary Table | Inserts a property table that lists requirements information for blocks with associated requirements |
| Requirements System Loop | Applies all child components to systems with requirements |
| Requirements Table | Inserts a table that lists system and subsystem requirements |
To customize the requirements report, you can:
Add or delete components.
Move components up or down in the report hierarchy.
Customize components to specify how the report presents certain information.
For more information, see Simulink Report Generator User's Guide.
When you have a model open in Simulink, the Model Editor provides two options for creating requirements reports:
The System Design Description report describes a system design represented by the current Simulink model.
You can use the System Design Description report to:
Review a system design without having the model open.
Generate summary and detailed descriptions of the design.
Assess compliance with design requirements.
Archive the system design in a format independent of the modeling environment.
Build a customized version of the report using the Simulink Report Generator software.
To generate a System Design Description report that includes requirements information:
Open the model for which you want to create a report.
Select File > Reports > System Design Description.
In the Design Description dialog box, select Requirements traceability.
Select any other options that you want for this report.
Click Generate.
As the software is generating the report, the status appears in the MATLAB command window.
The report name is the model name, followed by a numeral, followed by the extension that reflects the document type (.pdf, .html, etc.).
If your model has linked requirements, the report includes a chapter, Requirements Traceability , that includes:
Lists of model objects that have requirements with hyperlinks to display the objects
Images of each subsystem, highlighting model objects with requirements
In the Model Editor, the menu option File > Reports > Design Requirements creates a requirements report, as described in Creating a Default Requirements Report. This menu option is equivalent to Tools > Requirements > Generate report.
To specify options for the report, select Tools > Requirements > Settings. Before generating the report, on the Report tab, set the options that you want. For detailed information about these options, see Customizing the Requirements Report.
 | Navigating to Requirements from a Model | Filtering Requirements with User Tags |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
