|
|
|
| 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 |
This table summarizes what's new in Version 3.2 (R2011b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
| Yes Details below | Yes Summary | Bug
Reports Includes fixes |
New features and changes introduced in this version are:
Capability to Store Requirements Information Outside the Model File
Microsoft Excel Support for Consistency Checking of Simulink References in Requirements Documents
API for Creating Procedural-Based Model Advisor Configurations
The If block now receives condition and MCDC coverage on any if conditions or elseif conditions that contain logical expressions with multiple conditions. Previously, the If block only received decision coverage.
The If block receives coverage as follows:
The software measures decision coverage for the if condition and all elseif conditions.
If the if condition or any of the elseif conditions contain a logical expression with multiple conditions, such as u1 & u2 & u3, the software also measures condition and MCDC coverage for each condition in the expression, for example, u1, u2, and u3 .
The Requirements Management Interface (RMI) now provides an option to store requirements links information in an external file. The default name for this file is model_name.req. External storage allows you to:
Associate information about links to external requirements documents without modifying the timestamp and version of your model (.mdl) file.
Use different sets of requirements links with the same model by loading links from different files.
To enable external storage of requirements links, in the Requirements Settings dialog box, on the Storage tab, select Store externally (in a separate .req file). After setting this option, all models for which you create new requirements links will use external storage.
The RMI provides several new functions that allow you to manage the links in external files:
rmidata.map — Update link information in an external file.
rmidata.default — Set the option for storing requirements link information ('internal' or 'external').
rmidata.export — Move link information for a model to an external file.
If you link to requirements in custom requirements documents, you can now define link type properties that provide selection-based linking capabilities for these documents. Selection-based linking will be available when you:
Right-click a model object and select Requirements in the context menu.
Select Requirements > Edit/Add Links and create new requirements using the Requirements dialog box.
For more information, see Custom Types of Requirements Documents.
The Requirements Management Interface (RMI) can now include details from requirements text in the requirements report, depending on the type of requirements document:
Microsoft Word — Include entire paragraph or subsection associated with each linked requirement.
Microsoft Excel® — If the requirement is a single cell in a workbook, include the content from all the preceding cells in that row as a table. If the requirements are in a cell range, include all the content from the cells in that range as a table.
IBM® Rational® DOORS® — Include the Object Text and Object Heading attributes for the linked requirements object, and other attributes as specified by the user.
You can specify which DOORS attributes to include or omit from the report using the new RptgenRMI.doorsAttribs function.
Before you generate the requirements report, in the Requirements Settings dialog box, on the Report tab, select Include details from linked documents.
The rmi function has a 'checkdoc' option that checks links from requirements documents to Simulink model objects. This option now checks Microsoft Excel requirements documents, in addition to Microsoft Word documents and IBMRationalDOORS databases.
When the Requirements Management Interface (RMI) generates an HTML report file, it now uses the model name in the file name. The default name for a requirements report is model_name_report.html.
The output format for slvnvruntest and slvnvruncgvtest changed in R2011b. In R2011b, the output argument contains the following data for each test case executed in an array of Simulink.SimulationOutput objects:
Field | Description |
|---|---|
tout_slvnvruncgvtest | Simulation time |
xout_slvnvruncgvtest | State data |
yout_slvnvruncgvtest | Output signal data |
logsout_slvnvruncgvtest | Signal logging data for:
|
If you have scripts that depend on the output from slvnvruntest and slvnvruncgvtest, you can temporarily specify the output format. Use the nonvisible field outputFormat in the runOpts structure that slvnvruntestopts creates as follows:
runOpts = slvnvruntestopts; runOpts.outputFormat = 'TimeSeries'; slvnvruntest(model_name, sldvData, runOpts);
or
runOpts = slvnvruntestopts; runOpts.outputFormat = 'StructureWithTime'; slvnvruntest(model_name, data, runOpts);
For R2011b, error and warning message identifiers have changed in Simulink Verification and Validation.
If you have scripts or functions that use message identifiers that changed, you must update the code to use the new identifiers. Typically, message identifiers are used to turn off specific warning messages, or in code that uses a try/catch statement and performs an action based on a specific error identifier.
For example, the SLVNV:simcoverage:InvalidFirstArgument identifier has changed to SLVNV:simcoverage:complexityinfo:InvalidFirstArgument. If your code checks for SLVNV:simcoverage:InvalidFirstArgument, you must update it to check for SLVNV:simcoverage:complexityinfo:InvalidFirstArgument instead.
To determine the identifier for a warning, run the following command just after you see the warning in the MATLAB command window:
[MSG,MSGID] = lastwarn;
This command saves the message identifier to the variable MSGID.
To determine the identifier for an error that appears at the MATLAB prompt, run the following commands just after you see the error:
exception = MException.last; MSGID = exception.identifier;
Note Warning messages indicate a potential issue with your code. While you can turn off a warning, a suggested alternative is to change your code so it runs warning-free. |
In R2011b, there is a new API you can use to create a procedural-based Model Advisor configuration. A procedural-based configuration allows you to specify the order in which you make changes to your model. You do this by organizing checks into procedures using the procedures API. A check in a procedure does not run until the previous check passes. A procedural-based configuration runs until a check fails, requiring you to modify the model to pass the check and proceed on to the next check. For more information, see Creating Procedural-Based Model Advisor Configurations.
The Simulink Model Advisor includes new modeling standards checks.
The Model Advisor By Task folder contains a new Modeling Standards for ISO 26262 check:
The Model Advisor By Task folder contains a new Modeling Standards for IEC 61508 check:
The Model Advisor By Task folder contains a new Modeling Standards for DO-178B check:
In R2011b, the Model Advisor report now displays the check input parameters. For more information, see Viewing and Saving Model Advisor Reports in the Simulink documentation.
 | Version 3.3 (R2012a) Simulink Verification and Validation Software | Version 3.1 (R2011a) Simulink Verification and Validation Software |  |
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 |
