Simulink® Verification and Validation™ Release Notes

Simulink® Verification and Validation™ Release Notes
Simulink® Verification and Validation™ Release
Notes
How to Contact MathWorks
Latest news:
www.mathworks.com
Sales and services:
www.mathworks.com/sales_and_services
User community:
www.mathworks.com/matlabcentral
Technical support:
www.mathworks.com/support/contact_us
Phone:
508-647-7000
The MathWorks, Inc.
3 Apple Hill Drive
Natick, MA 01760-2098
Simulink® Verification and Validation™ Release Notes
© COPYRIGHT 2004–2015 by The MathWorks, Inc.
The software described in this document is furnished under a license agreement. The software may be used
or copied only under the terms of the license agreement. No part of this manual may be photocopied or
reproduced in any form without prior written consent from The MathWorks, Inc.
FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation
by, for, or through the federal government of the United States. By accepting delivery of the Program
or Documentation, the government hereby agrees that this software or documentation qualifies as
commercial computer software or commercial computer software documentation as such terms are used
or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and
conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and
govern the use, modification, reproduction, release, performance, display, and disclosure of the Program
and Documentation by the federal government (or other entity acquiring for or through the federal
government) and shall supersede any conflicting contractual terms or conditions. If this License fails
to meet the government's needs or is inconsistent in any respect with federal procurement law, the
government agrees to return the Program and Documentation, unused, to The MathWorks, Inc.
Trademarks
MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See
www.mathworks.com/trademarks for a list of additional trademarks. Other product or brand
names may be trademarks or registered trademarks of their respective holders.
Patents
MathWorks products are protected by one or more U.S. patents. Please see
www.mathworks.com/patents for more information.
Contents
R2015a
Coverage measurement for C S-functions . . . . . . . . . . . . . . .
1-2
Model Advisor checks for MATLAB functions . . . . . . . . . . . .
IEC 61508, ISO 26262, and EN 50128 . . . . . . . . . . . . . . . . .
DO-178C/DO-331 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MathWorks Automotive Advisory Board . . . . . . . . . . . . . . . .
1-2
1-2
1-3
1-3
R2014b
Model coverage for relational boundary values . . . . . . . . . .
2-2
Modeling standard check support for charts that use
MATLAB as the action language . . . . . . . . . . . . . . . . . . . . .
2-2
Requirements linking for Simulink data dictionary entries
2-3
Capture and display of requirements details in model
highlighting and Web view . . . . . . . . . . . . . . . . . . . . . . . . . .
2-3
R2014a
Web view option for coverage results . . . . . . . . . . . . . . . . . . .
3-2
iii
Model Advisor check authoring for model configuration
parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2
Condition coverage for Relational Operator blocks . . . . . . .
3-2
Model Advisor checks for MATLAB Code Analyzer
messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DO-178C/DO-331 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508, ISO 26262, and EN 50128 . . . . . . . . . . . . . . . . .
MathWorks Automotive Advisory Board . . . . . . . . . . . . . . . .
3-2
3-2
3-2
3-3
Japanese language localization support . . . . . . . . . . . . . . . . .
3-3
Enhanced modeling standards checks for display attributes
and Math Operations blocks . . . . . . . . . . . . . . . . . . . . . . . .
MathWorks Automotive Advisory Board check for display
attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508, ISO 26262, and EN 50128 Check usage of Math
Operations blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DO-178C/DO-331 Check usage of Math Operations blocks . . .
3-3
3-3
3-3
3-3
R2013b
iv
Contents
Requirements traceability for MATLAB code . . . . . . . . . . . .
4-2
Reset option for cumulative model coverage results . . . . . .
4-2
EN 50128 modeling standard checks for railway
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
Model Advisor checks for MATLAB Function blocks and
input/output range specifications . . . . . . . . . . . . . . . . . . . .
MATLAB Function blocks . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inport and Outport range specifications . . . . . . . . . . . . . . . .
4-2
4-2
4-3
ModelAdvisor.run option for parallel processing . . . . . . . . .
4-3
R2013a
Model coverage for saturation on integer overflow in
Stateflow, MATLAB Function blocks . . . . . . . . . . . . . . . . .
5-2
rmipref command for managing requirements traceability
preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
Inclusion of DOORS module-prefix in requirements
traceability location identifiers . . . . . . . . . . . . . . . . . . . . . .
5-2
Model Advisor navigation between Upgrade Advisor,
Performance Advisor, and Code Generation Advisor . . . .
5-2
New Model Advisor Checks for Modeling Standards . . . . . .
IEC 61508 and ISO 26262 Checks . . . . . . . . . . . . . . . . . . . .
DO-178C/DO-331 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3
5-3
5-3
R2012b
Custom labels for requirements links to IBM Rational
DOORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
Requirements linking for Simulink annotations . . . . . . . . . .
6-2
Coverage filtering for Stateflow events . . . . . . . . . . . . . . . . .
6-3
Model Advisor dashboard, providing efficient model
guideline checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
Model Advisor checks for library models and the DO-178C/
DO-331 standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Library Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DO-178C/DO-331 Standard . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6-3
6-3
HTTP navigation from generated requirements report to
requirements and Simulink objects . . . . . . . . . . . . . . . . . .
6-4
v
R2012a
Coverage Metric for Blocks with Saturate on Integer
Overflow Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Coverage Support for Simulink Design Verifier Functions
Inside Stateflow Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Cumulative Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Requirements Linking Between Simulink Objects . . . . . . . .
7-2
URL-Based Navigation From External Requirements
Documents to Simulink Objects . . . . . . . . . . . . . . . . . . . . . .
7-3
Model Advisor Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3
MathWorks Automotive Advisory Board Checks . . . . . . . . . .
7-4
R2011b
vi
Contents
Condition and MCDC Coverage for If Block Conditions . . . .
8-2
Capability to Store Requirements Information Outside the
Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-2
Selection-Based Linking for Custom Requirements
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-3
Include Requirements Document Data in the Report . . . . . .
8-3
Microsoft Excel Support for Consistency Checking of
Simulink References in Requirements Documents . . . . . .
8-3
Requirements Report Default File Names Based on Model
Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-4
Changed Format for slvnvruntest and slvnvruncgvtest
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-4
Conversion of Error and Warning Message Identifiers . . . . .
8-5
API for Creating Procedural-Based Model Advisor
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-5
New Model Advisor Checks . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISO 26262 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-6
8-6
8-6
8-6
Check Input Parameters in Model Advisor Report . . . . . . . .
8-6
R2011a
New Capability to Filter Model Objects from Coverage
Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-2
Improved RMI Support for Reference Blocks . . . . . . . . . . . .
9-2
New Function to Merge Logged Component Data . . . . . . . . .
9-2
New and Enhanced Model Advisor Checks . . . . . . . . . . . . . .
ISO 26262 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-2
9-3
9-3
9-4
R2010bSP1
Bug Fixes
vii
R2010b
New Functions for Extraction, Signal Logging, Harness
Generation, and Test Execution for Model Components .
11-2
New rmi Option to Validate Links in External Requirements
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-3
New Capability to Link a Requirement to Multiple Model
Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-3
Viewing Requirements Linked to Model Objects . . . . . . . . .
11-3
Model Coverage Support for Multiple Instances of a
Referenced Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-3
Model Coverage Support for Stateflow Atomic Subcharts .
11-4
Checking Systems Programmatically With the Model
Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-4
MathWorks Check IDs for the Model Advisor Updated . . . .
11-4
New and Enhanced Model Advisor Checks . . . . . . . . . . . . .
MathWorks Automotive Advisory Board Checks . . . . . . . . .
11-5
11-5
R2010a
Coverage Support for Dead Zone Block . . . . . . . . . . . . . . . .
12-2
Coverage Support for the Simulink Design Verifier Functions
in MATLAB Function Blocks . . . . . . . . . . . . . . . . . . . . . . .
12-2
viii
Contents
Coverage Support for Trigger Ports in Model Blocks . . . . .
12-2
Requirements Support for MuPAD Documents . . . . . . . . . .
12-2
Improved Reports About Requirements Links in Models . .
12-2
New Capability to Tag and Filter Model Requirements . . .
12-2
Improved IBM Rational DOORS Synchronization . . . . . . . .
12-3
Function rminav Removed . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-3
New and Enhanced Model Advisor Checks . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MathWorks Automotive Advisory Board Checks . . . . . . . . .
12-3
12-3
12-4
12-4
Modeling Guidelines Documentation Moved into Simulink
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-4
R2009bSP1
Bug Fixes
R2009b
New Coverage Reporting for Variable-Size Signals . . . . . .
14-2
Model Coverage for Simulink Design Verifier Blocks . . . . .
14-2
Force Block Reduction Off During Simulation . . . . . . . . . .
14-2
Improved RMI Highlighting and Reporting . . . . . . . . . . . . .
14-3
Create Custom Configurations Using the Model Advisor
Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14-3
Licensing Revised for the Model Advisor . . . . . . . . . . . . . . .
14-3
ix
New and Enhanced Model Advisor Checks . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14-4
14-4
14-4
Modeling Guidelines for High-Integrity Systems . . . . . . . . .
14-5
R2009a
Recording Coverage for External MATLAB Files . . . . . . . .
15-2
API for Customizing Model Advisor Results . . . . . . . . . . . .
15-2
New and Enhanced Model Advisor Checks . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modeling Standards for MAAB Checks . . . . . . . . . . . . . . . .
15-2
15-2
15-2
15-3
MathWorks Automotive Advisory Board Control Algorithm
Modeling Guidelines Using MATLAB, Simulink, and
Stateflow Included in Help . . . . . . . . . . . . . . . . . . . . . . . . .
15-3
R2008b
x
Contents
New and Enhanced Model Advisor Checks . . . . . . . . . . . . .
DO-178B Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEC 61508 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MathWorks Automotive Advisory Board Checks . . . . . . . . .
16-2
16-2
16-3
16-3
Improved Selection-Based Linking . . . . . . . . . . . . . . . . . . . .
16-3
Enhanced Model Coverage Report . . . . . . . . . . . . . . . . . . . .
16-4
R2008a+
Bug Fixes
R2008a
Enhanced Coverage Support for Referenced Models . . . . .
18-2
New Requirements Submenu in Model Explorer . . . . . . . . .
18-2
Model Advisor Checks for Modeling Standards Enhanced .
18-2
API for Customizing Model Advisor Enhanced . . . . . . . . . .
18-3
R2007b+
Bug Fixes
R2007b
Model Coverage Support for Referenced Models . . . . . . . .
20-2
Model Advisor Checks for Modeling Standards Enhanced .
20-2
API for Customizing Model Advisor HTML Reports . . . . . .
20-3
xi
R2007a+
Bug Fixes
R2007a
Bug Fixes
R2006b
Requirement Links Checking . . . . . . . . . . . . . . . . . . . . . . . .
23-2
Modeling Standards Checking . . . . . . . . . . . . . . . . . . . . . . . .
23-2
R2006a
No New Features or Changes
xii
Contents
R2015a
Version: 3.9
New Features
Bug Fixes
R2015a
Coverage measurement for C S-functions
Model coverage is supported for C/C++ S-Functions. The coverage results for S-Function
blocks can be viewed in the same report as the rest of the model. For each S-Function
block, the report links to a detailed coverage report for the C/C++ code in the block.
To generate coverage report for S-Function blocks:
1
When creating S-Functions, enable support for coverage.
2
When generating coverage report, enable support for S-Functions.
The following coverage metrics are reported for S-Functions:
• “Cyclomatic Complexity”
• “Condition Coverage (CC)”
• “Decision Coverage (DC)”
• “MCDC Coverage”
• Percentage of statements covered
For more information, see:
• “Model Coverage for C and C++ S-Functions”
• “View Coverage Results for C/C++ Code in S-Function Blocks”
Model Advisor checks for MATLAB functions
The Model Advisor includes checks for MATLAB® functions to comply with modeling
standards. Previously, the checks verified that only MATLAB Function blocks complied
with modeling standards.
IEC 61508, ISO 26262, and EN 50128
The Model Advisor By Task folder contains Modeling Standards for IEC 61508,
Modeling Standards for ISO 26262, and Modeling Standards for EN 50128 checks:
• “Check for MATLAB Function interfaces with inherited properties” replaces Check
for MATLAB Function block interfaces with inherited properties.
• “Check MATLAB Function metrics” replaces Check MATLAB Function block
metrics.
1-2
DO-178C/DO-331
The Model Advisor By Task folder contains Modeling Standards for DO-178C/
DO-331 checks:
• “Check for MATLAB Function interfaces with inherited properties” replaces Check
for MATLAB Function block interfaces with inherited properties.
• “Check MATLAB Function metrics” replaces Check MATLAB Function block
metrics.
MathWorks Automotive Advisory Board
The Model Advisor By Task > Modeling Standards for MAAB > MATLAB
Functions folder contains new checks:
• “Check input and output settings of MATLAB Functions” replaces Check input and
output settings of MATLAB Function blocks.
• “Check MATLAB Function metrics” replaces Check MATLAB Function block
metrics.
1-3
R2014b
Version: 3.8
New Features
Bug Fixes
R2014b
Model coverage for relational boundary values
The model coverage tool introduces a relational boundary coverage metric.
Relational boundary coverage examines blocks that have an explicit or implicit relational
operation. The coverage also examines Stateflow® transitions and MATLAB function
blocks that contain a relational operation.
For these blocks, the metric records whether a simulation tests the relational operation
with:
• Equal operand values. This part of relational boundary coverage applies only if both
operands are integers or fixed-point numbers.
• Operand values that differ by a certain tolerance. This part of relational boundary
coverage applies to all operands. For integer and fixed-point operands, the tolerance is
fixed. For floating-point operands, you can use either a predefined tolerance or specify
your own tolerance value.
For more information, see Relational Boundary Coverage.
Modeling standard check support for charts that use MATLAB as the
action language
The following Model Advisor checks now support charts that use MATLAB as the action
language.
In the By Task > Modeling Standards for IEC 61508, Modeling Standards for ISO
26262, and Modeling Standards for EN 50128 folders:
• Check usage of Stateflow constructs
In the By Task > Modeling Standards for MAAB > Stateflow folder:
• Check transition actions in Stateflow charts
• Check for unary minus operations on unsigned integers in Stateflow charts
• Check for equality operations between floating-point expressions in Stateflow charts
• Check entry formatting in State blocks in Stateflow charts
• Check return value assignments of graphical functions in Stateflow charts
• Check usage of return values from a graphical function in Stateflow charts
2-2
• Check for event broadcasts in Stateflow charts
• Check for comparison operations in Stateflow charts
• Check usage of exclusive and default states in state machines
Requirements linking for Simulink data dictionary entries
You can create requirements traceability links for entries in Simulink® data dictionaries.
In the Model Explorer, right-click a data dictionary entry. From the Requirements
Traceability context menu, use selection-based linking shortcuts or the Requirements
Link Editor.
Capture and display of requirements details in model highlighting and
Web view
Requirements traceability highlighting opens a separate Requirements Details window
that shows content from linked documents in Microsoft® Word, Microsoft Excel®, and
IBM® Rational® DOORS®. To open the Requirements Details window, in the Simulink
Editor, select Analysis > Requirements Traceability > Highlight Model. Select a
model object with requirements links to see content from linked requirements documents
in the Requirements Details window.
If you have Simulink Report Generator™ installed, you can include requirements
information in a Web view. In the Simulink Editor, select File > Export Model to >
Web In the Web View dialog box, open the Optional Views tab and select Include
Requirements view. Alternatively, in the Simulink Editor, select Analysis >
Requirements Traceability > Generate Web View.
To view requirements information in a Web view, click a highlighted block (for example,
orange highlighted blocks have requirements information). The information for that
block appears in the Informer pane underneath the model.
2-3
R2014a
Version: 3.7
New Features
Bug Fixes
R2014a
Web view option for coverage results
You can export a Model Coverage Web View for your model. A Web View is an
interactive rendition of a model that you can view in a Web browser. A Model Coverage
Web View includes model coverage highlighting and analysis information from the
Coverage Display Window, as described in View Coverage Results in a Model. For more
information, see Export Model Coverage Web View.
Model Advisor check authoring for model configuration parameters
You can create a configuration parameter check by specifying check behavior in an
XML data file. To register the check, you use an sl_customization file. Previously,
only DO-178C/DO-331 checks verified configuration parameter checks. To create the
configuration parameter check, see Create Check for Model Configuration Parameters.
Condition coverage for Relational Operator blocks
The model coverage tool records condition coverage for Relational Operator, Compare to
Constant, and Compare to Zero blocks. For more information, see Model Objects That
Receive Coverage.
Model Advisor checks for MATLAB Code Analyzer messages
DO-178C/DO-331
The Model Advisor By Task folder contains these Modeling Standards for DO-178C/
DO-331 checks:
• Check MATLAB Code Analyzer messages
• Check MATLAB code for global variables
IEC 61508, ISO 26262, and EN 50128
The Model Advisor By Task folder contains these Modeling Standards for IEC 61508,
Modeling Standards for ISO 26262, and Modeling Standards for EN 50128 checks:
• Check MATLAB Code Analyzer messages
• Check MATLAB code for global variables
3-2
MathWorks Automotive Advisory Board
The Model Advisor By Task > Modeling Standards for MAAB > MATLAB
Functions folder contains this new check:
• Check MATLAB code for global variables
Japanese language localization support
Simulink Verification and Validation™ is available in Japanese for Japanese localized
systems. For more information, see Internationalization.
Enhanced modeling standards checks for display attributes and Math
Operations blocks
MathWorks Automotive Advisory Board check for display attributes
Check the display attributes of block names checks the display attributes of all blocks
to verify compliance with MathWorks® Automotive Advisory Board guideline jc_0061:
Display of block names. Previously, the check did not verify compliance of subsystem
block names. You can find Check the display attributes of block names in the Model
Advisor By Task > Modeling Standards for MAAB > Simulink folder.
IEC 61508, ISO 26262, and EN 50128 Check usage of Math Operations blocks
IEC 61508, ISO 26262, and EN 50128 Check usage of Math Operations blocks verifies
the use of the following Math Operations blocks:
• Abs
• Assignment
• Gain
Previously, the check verified the use of only Abs and Gain blocks. Check usage of
Math Operations blocks is available in the By Task >Modeling Standards for IEC
61508, Modeling Standards for ISO 26262, and Modeling Standards for EN 50128
folders.
DO-178C/DO-331 Check usage of Math Operations blocks
DO-178C/DO-331 Check usage of Math Operations blocks verifies the use of the following
Math Operation blocks:
3-3
R2014a
• Abs
• Assignment
• Gain
• Math Function
• Natural logarithm
• Common (base 10) logarithm
• Remainder after division
• Reciprocal
Previously, the check verified the use of only Abs and Gain blocks. The DO-178C/DO-331
Check usage of Math blocks verified the use of the Math Function blocks. Check
usage of Math blocks is no longer available in the By Task > Modeling Standards
for DO-178C/DO-331 folder.
Check usage of Math Operations blocks is available in the Model Advisor By Task >
Modeling Standards for DO-178C/DO-331 folder.
3-4
R2013b
Version: 3.6
New Features
Bug Fixes
Compatibility Considerations
R2013b
Requirements traceability for MATLAB code
When you store requirements traceability data externally, you can create traceability
links to and from specific lines of MATLAB code. This capability allows you to include
finer granularity in your traceability links. For example, instead of linking between a
requirement and a MATLAB Function block, you can link between a requirement and
individual lines or sections of code inside a MATLAB Function block.
For more information, see MATLAB Code Traceability.
Reset option for cumulative model coverage results
If you have enabled cumulative model coverage data collection and have existing
cumulative coverage data, you can reset that data between simulations. In the Coverage
Settings dialog box, on the Results tab, click Clear data. For more information, see
Specify Model Coverage Options.
EN 50128 modeling standard checks for railway applications
The Model Advisor includes model checks for compliance to the EN 50128 standard. The
checks are available in the By Task > Modeling Standards for EN 50128 folder.
Model Advisor checks for MATLAB Function blocks and input/output
range specifications
MATLAB Function blocks
The Model Advisor includes checks for MATLAB Function blocks to comply with
modeling standards.
IEC 61508, ISO 26262, and EN 50128
The Model Advisor By Task folder contains Modeling Standards for IEC 61508,
Modeling Standards for ISO 26262, and Modeling Standards for EN 50128 checks:
• Check for MATLAB Function block interfaces with inherited properties
• Check MATLAB Function block metrics
DO-178C/DO-331
The Model Advisor By Task folder contains Modeling Standards for DO-178C/
DO-331 checks:
4-2
• Check for MATLAB Function block interfaces with inherited properties
• Check MATLAB Function block metrics
MathWorks Automotive Advisory Board
The Model Advisor By Task > Modeling Standards for MAAB > MATLAB
Functions folder contains new checks:
• Check input and output settings of MATLAB Function blocks
• Check MATLAB Function block metrics
Inport and Outport range specifications
The Model Advisor includes checks for MATLAB Function blocks to comply with
modeling standards.
IEC 61508, ISO 26262, and EN 50128
The Model Advisor By Task folder contains Modeling Standards for IEC 61508,
Modeling Standards for ISO 26262, and Modeling Standards for EN 50128 checks:
• Check for root Inports with missing range definitions
• Check for root Outports with missing range definitions
ModelAdvisor.run option for parallel processing
If you have a Parallel Computing Toolbox™ license, you can check multiple systems in
parallel by using the ModelAdvisor.run function with 'ParallelMode’ set to 'On'. By
default, ‘ParallelMode’ is set to ’Off’.
Compatibility Considerations
When you use ModelAdvisor.run with 'ParallelMode’ set to 'On', MATLAB
automatically creates a parallel pool. Previously, when using ModelAdvisor.run to
check multiple systems in parallel, you had to open a parallel pool.
4-3
R2013a
Version: 3.5
New Features
Bug Fixes
R2013a
Model coverage for saturation on integer overflow in Stateflow, MATLAB
Function blocks
You can use the model coverage tool to analyze saturation on integer overflow in
Stateflow charts and MATLAB Function blocks. During simulation, the software detects
the number of times saturation on integer overflow occurs in a Stateflow chart or
MATLAB function.
Saturation on integer overflow coverage for Simulink blocks has been supported since
R2012a.
To collect saturation on integer overflow coverage for your model, in the Simulink Editor,
select Analysis > Coverage > Settings. In the Coverage Settings dialog box, in the
Coverage metrics group, select Saturation on integer overflow.
rmipref command for managing requirements traceability preferences
The rmipref function provides a command-line interface that enables you to manage
requirements traceability preferences.
For more information on requirements traceability preferences, see The Requirements
Settings Dialog Box.
Inclusion of DOORS module-prefix in requirements traceability location
identifiers
Unique target identifiers for IBM Rational DOORS requirements links now include
DOORS module prefixes, if they are present.
Model Advisor navigation between Upgrade Advisor, Performance
Advisor, and Code Generation Advisor
In the Model Advisor window, you can select:
• Code Generation Advisor to help configure your model to meet code generation
objectives.
• Upgrade Advisor to help upgrade models.
• Performance Advisor to help improve the simulation performance of your model.
5-2
New Model Advisor Checks for Modeling Standards
The Simulink Model Advisor includes new modeling standards checks.
IEC 61508 and ISO 26262 Checks
The Model Advisor By Task >Modeling Standards for IEC 61508 and Modeling
Standards for ISO 26262 folders contain a new check to replace Check for
questionable constructs:
• Check for blocks not recommended for C/C++ production code deployment
DO-178C/DO-331 Checks
The Model Advisor By Task folder contains a new Modeling Standards for DO-178C/
DO-331 check to replace Identify questionable blocks within the specified system:
• Check for blocks not recommended for C/C++ production code deployment
5-3
R2012b
Version: 3.4
New Features
Bug Fixes
Compatibility Considerations
R2012b
Custom labels for requirements links to IBM Rational DOORS
You can specify custom templates for labels of your model requirements links to IBM
Rational DOORS. With these templates, in your model, you can include DOORS object
property information that you need for your project. The Simulink Verification and
Validation software uses requirements links labels in context menus, generated reports,
code comments, and consistency checks.
Using the rmi command, you can specify a custom template for new DOORS
requirements links. You can include user-defined DOORS attributes in the template. For
more information, at the MATLAB command prompt, enter:
help rmi
Under the heading
Custom labels for DOORS links
the output shows detailed examples for available template settings.
Compatibility Considerations
If you specify a custom template for labels that differs from the default template and
your model has existing requirements links to DOORS, requirements consistency
checking reports inconsistencies for these links. You can adjust labels for existing
DOORS requirements links using the rmi command.
Requirements linking for Simulink annotations
You can create requirements links to and from Simulink.Annotation objects using
the Requirements Management Interface (RMI). Annotations are free-floating text boxes
that you can place inside a Simulink model. You can use them to describe requirements
for the design. You can then use RMI linking to associate annotations with other
Simulink objects or external requirements documents.
Requirements linking for Simulink annotations is enabled only if you configure your
model to store requirements data externally. To specify external storage of requirements
data for a model, in the Requirements Settings dialog box under Storage > Default
storage location for requirements links data, select Store externally (in a
separate *.req file).
For more information, see Requirements Linking with Simulink Annotations.
6-2
Compatibility Considerations
If you have a model that already contains requirements links using the internal storage
setting, you cannot use requirements linking for Simulink annotations until you convert
that model to use external storage for RMI data. To convert the model, move all existing
requirements links in it to an external .req file by selecting Analysis > Requirements
> Move to File.
Coverage filtering for Stateflow events
You can exclude Stateflow events from recording coverage during Simulink Verification
and Validation model coverage collection. For more information, see Filter a Stateflow
Event.
Model Advisor dashboard, providing efficient model guideline checking
The Model Advisor dashboard provides a way for you to efficiently check that your model
complies with modeling guidelines. You can use the Model Advisor dashboard to run
a set of checks on your model without opening the Model Advisor window. For more
information, see Overview of the Model Advisor Dashboard.
Model Advisor checks for library models and the DO-178C/DO-331
standard
Library Models
There are Model Advisor checks available to verify the syntax of library models.
When you use the Model Advisor to check a library model, the Model Advisor window
indicates (~) checks that do not check libraries. To determine if you can run the check
on library models, you can also refer to the check documentation, “Capabilities and
Limitations”. You cannot use checks that require model compilation. You can use the
ModelAdvisor.Check.SupportLibrary API to create custom checks for library models.
DO-178C/DO-331 Standard
The Model Advisor also includes model checks for compliance to the DO-178C and
DO-331 standards. The new checks are available in the Model Advisor folders:
• By Task > Modeling Standards for DO-178C/DO-331
6-3
R2012b
• By Product > Simulink Verification and Validation > Modeling Standards >
Modeling DO-178C/DO-331 Checks
For information on the DO-178C Software Considerations in Airborne Systems and
Equipment Certification and related standards, see Radio Technical Commission for
Aeronautics (RTCA) .
Former DO-178B checks are available in the DO-178C/DO-331 Model Advisor folders.
The DO-178C/DO-331 checks replace the DO-178B checks.
HTTP navigation from generated requirements report to requirements and
Simulink objects
You can set the Requirements Management Interface (RMI) to generate requirements
reports that support navigation from system browsers to requirements documents
and model objects. You can view and navigate from your generated reports in system
browsers as long as the MATLAB internal HTTP server is active on your local host.
If you convert your generated report to a PDF file or Microsoft Word document, the
navigation links remain valid. For more information, see Customize Requirements
Report Using the RMI Settings and Link from External Applications.
6-4
R2012a
Version: 3.3
New Features
Bug Fixes
Compatibility Considerations
R2012a
Coverage Metric for Blocks with Saturate on Integer Overflow Parameter
In R2012a, the Simulink Verification and Validation model coverage tool provides
coverage for blocks when you select the Saturate on Integer Overflow Coverage
parameter option. The software reports the number of times a block saturates on integer
overflow during simulation.
To enable this feature, in the Coverage Settings dialog box, on the Coverage tab, select
the Saturate on Integer Overflow option.
Coverage Support for Simulink Design Verifier Functions Inside Stateflow
Charts
Simulink Verification and Validation now records coverage for the following Simulink
Design Verifier™ functions inside Stateflow charts:
• sldv.assume
• sldv.condition
• sldv.prove
• sldv.test
For more information, see Simulink Design Verifier Coverage.
Cumulative Coverage
Simulink Verification and Validation now provides cumulative coverage for identically
configured multiple instances of:
• Reusable subsystems
• Stateflow constructs
For more information, see Creating Cumulative Coverage for Reusable Subsystems and
Stateflow Constructs.
Requirements Linking Between Simulink Objects
You can now create requirements links between Simulink objects using selectionbased linking. This capability allows you to create requirements links between models,
enhancing traceability.
7-2
To create a requirement link from one model object to another model object:
1
Right-click the link destination model object and select Requirements > Select for
linking with Simulink.
2
Right-click the link source model object and select Requirements > Add link to
selected object.
3
Right-click the link source model object again and select Requirements. The new
link appears at the top of the Requirements submenu.
For more information, see Links Between Models and Requirements.
URL-Based Navigation From External Requirements Documents to
Simulink Objects
In R2012a, the Simulink Verification and Validation tool provides URL-based navigation
from external requirements documents to Simulink objects. Previously, the software used
ActiveX® controls to navigate from Microsoft Office documents to Simulink objects. Now,
by default, navigation links from Microsoft Office documents are hyperlinks, allowing for
export to HTML or PDF files, and manual copy-paste into other document formats. For
more information, see The Requirement Settings Dialog Box.
Compatibility Considerations
Compatibility Considerations
Simulink Verification and Validation software continues to recognize navigation links
created with ActiveX controls. Additionally, you can create navigation links with ActiveX
by selecting Use ActiveX buttons in Word and Excel (backward compatibility) in
the Requirements Settings dialog box.
Model Advisor Exclusions
You can now exclude model blocks from selected Model Advisor checks, saving time
during model development and verification. When a Model Advisor analysis is complete,
you can use Model Advisor highlighting to indicate the analysis results for individual
Model Advisor checks in the model window. You can exclude blocks from selected checks
by right-clicking blocks and selecting exclusions options. For more information, see
Limiting the Scope of a Model Advisor Analysis.
7-3
R2012a
MathWorks Automotive Advisory Board Checks
In R2012a, the Model Advisor By Task > Modeling Standards for MAAB > Stateflow
folder no longer includes:
• Check for annotations with drop shadows.
• Check for tunable parameters in Stateflow charts.
• Check whether Stateflow events are defined at the chart level or below. This
check is relevant only for software versions previous to release R2009b.
For more information, see MathWorks Automotive Advisory Board Checks in the
Simulink Verification and Validation documentation.
7-4
R2011b
Version: 3.2
New Features
Bug Fixes
Compatibility Considerations
R2011b
Condition and MCDC Coverage for If Block Conditions
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
.
Capability to Store Requirements Information Outside the Model File
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.
8-2
Selection-Based Linking for Custom Requirements Documents
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.
Include Requirements Document Data in the Report
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.
Microsoft Excel Support for Consistency Checking of Simulink References
in Requirements 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 IBM Rational
DOORS databases.
8-3
R2011b
Requirements Report Default File Names Based on Model Names
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.
Changed Format for slvnvruntest and slvnvruncgvtest Output
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:
• Signals that are connected to outports
• Signals that are configured for logging
on the model
Compatibility Considerations
Compatibility Considerations
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);
8-4
Conversion of Error and Warning Message Identifiers
For R2011b, error and warning message identifiers have changed in Simulink
Verification and Validation.
Compatibility Considerations
Compatibility Considerations
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.
API for Creating Procedural-Based Model Advisor Configurations
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
8-5
R2011b
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.
New Model Advisor Checks
The Simulink Model Advisor includes new modeling standards checks.
ISO 26262 Checks
The Model Advisor By Task folder contains a new Modeling Standards for ISO 26262
check:
• Check for inconsistent vector indexing methods
IEC 61508 Checks
The Model Advisor By Task folder contains a new Modeling Standards for IEC 61508
check:
• Check for inconsistent vector indexing methods
DO-178B Checks
The Model Advisor By Task folder contains a new Modeling Standards for DO-178B
check:
• Check for inconsistent vector indexing methods
Check Input Parameters in Model Advisor Report
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.
8-6
R2011a
Version: 3.1
New Features
Bug Fixes
R2011a
New Capability to Filter Model Objects from Coverage Collection
When you simulate your Simulink model, coverage filtering allows you to filter certain
model objects from recording coverage. The objects that you specify to exclude are stored
in an external file.
• Individual Simulink blocks that receive coverage
• All blocks of a certain type
• Subsystems and all their contents
• Stateflow charts, states, transitions, and temporal events
• Individual library-linked blocks or Stateflow charts
• All reference blocks from a specific block library
Improved RMI Support for Reference Blocks
The Requirements Management Interface (RMI) provides improved support for
managing requirements links on reference blocks.
• The new Library Block Requirements menu option allows you to view and
navigate to requirements associated only with the library block. These links are
available to all models that have reference blocks linked to library blocks that
themselves have requirements links.
• When you create links from reference blocks to requirements, those links are only
associated with the reference block in the current model. You cannot push the
requirements links associated with reference blocks back to the library.
New Function to Merge Logged Component Data
The slvnvmergedata function allows you to combine logged test cases and
counterexamples into a single structure. You can use logged data created by running
slvnvlogsignals, or by running a Simulink Design Verifier analysis.
New and Enhanced Model Advisor Checks
The Simulink Model Advisor includes new and updated modeling standards checks.
9-2
ISO 26262 Checks
In the Model Advisor By Task folder, there is a new Modeling Standards for ISO
26262 subfolder.
The subfolder includes the following checks:
• Display model metrics and complexity report
• Check for fully defined interface
• Check for unconnected objects
• Check for questionable constructs
• Check state machine type of Stateflow charts
• Check for model objects that do not link to requirements
• Display configuration management data
• Check usage of Math Operations blocks
• Check usage of Stateflow constructs
• Check usage of Signal Routing blocks
• Check usage of Logic and Bit Operations blocks
• Check usage of Ports and Subsystems blocks
For more information, see the IEC 61508 and ISO 26262 Checks in the Simulink
Verification and Validation documentation.
IEC 61508 Checks
Previously, the IEC 61508 Checks included the check:
• Check usage of Simulink constructs
This check is replaced by the following new checks:
• Check usage of Math Operations blocks
• Check usage of Signal Routing blocks
• Check usage of Logic and Bit Operations blocks
• Check usage of Ports and Subsystems blocks
For more information, see the IEC 61508 and ISO 26262 Checks in the Simulink
Verification and Validation documentation.
9-3
R2011a
DO-178B Checks
Previously, the DO-178B Checks included the following checks:
• Check for proper usage of For Iterator blocks
• Check for proper usage of While Iterator blocks
• Check for proper usage of Relational Operator blocks
• Check for proper usage of blocks that compute absolute values
These previously available checks are replaced by the following new checks:
• Check usage of Math Operations blocks
• Check usage of Signal Routing blocks
• Check usage of Logic and Bit Operations blocks
• Check usage of Ports and Subsystems blocks
Also available are the new checks:
• Check usage of lookup table blocks
• Check Stateflow charts for uniquely defined data objects
For more information, see the DO-178B Checks in the Simulink Verification and
Validation documentation.
If, Switch, and Switch Case blocks are now searched. See the “Check usage of Port and
Subsystems” and “Check usage of Signal Routing blocks” checks for more information.
9-4
R2010bSP1
Version: 3.0.1
Bug Fixes
R2010b
Version: 3.0
New Features
Bug Fixes
Compatibility Considerations
R2010b
New Functions for Extraction, Signal Logging, Harness Generation, and
Test Execution for Model Components
Several new functions allow you to test the following model components:
• Models referenced from Model blocks
• Atomic subsystems
• Stateflow atomic subcharts
Using these functions, you can create and execute test cases that verify components in
order to:
• Debug the component
• Test the robustness of the component
• Achieve 100% model coverage for the component
The new functions perform the following tasks.
11-2
Use...
To...
slvnvextract
Extract an atomic subsystem or Stateflow atomic subchart
into a new model. This allows you to apply testing and
verification techniques that use models or an isolated model
component.
slvnvlogsignals
Simulate a Simulink model and log input signals to a model
referenced by a Model block. This allows you to capture
component inputs when you run a closed-loop system
simulation.
slvnvmakeharness
Create a harness model for a component, using logged input
signals if specified, or using the default signals. Harness
models support graphical editing of input values using
Signal Builder blocks.
slvnvmergeharness
Merge test cases and initializations from multiple harness
models into a single harness model.
slvnvruntest
Simulate a model, executing the specified test cases to
record model coverage and output values.
slvnvruncgvtest
Invoke the Code Generation Verification (CGV) API and
execute the specified test cases on the generated code for the
model.
New rmi Option to Validate Links in External Requirements Documents
The rmi function has a new option, 'checkdoc', that allows you to validate links from
Microsoft Word or IBM Rational DOORS requirements documents to Simulink models.
rmi generates a report of the problems that it detects. The report includes hyperlinks
that navigate to the requirements with problems so you can investigate and fix any
invalid links.
For more information, see Checking and Fixing ActiveX-Based Links in Requirements
Documents.
New Capability to Link a Requirement to Multiple Model Objects
The Requirements Management Interface (RMI) allows you to establish links to selected
requirements in Microsoft Word, Microsoft Excel, or IBM Rational DOORS. When you
create a link to a selected requirement for multiple model objects, the RMI inserts a
single navigation control into the requirements document that links to all the selected
model objects. When you activate the navigation control, all linked model objects are
highlighted.
Viewing Requirements Linked to Model Objects
If your model, or blocks in your model, has links to requirements in external documents,
you can now perform the following tasks without a Simulink Verification and Validation
license:
• Highlight objects in a model that have links to requirements
• View information about a requirement
• Navigate from a model object to associated requirements
• Filter requirements highlighting based on keywords
Model Coverage Support for Multiple Instances of a Referenced Model
The Simulink Verification and Validation software records coverage for all instances of a
referenced model in Normal simulation mode. The software combines the coverage data
from each instance and reports one set of coverage data for the referenced model.
11-3
R2010b
Model Coverage Support for Stateflow Atomic Subcharts
The Simulink Verification and Validation software records coverage for Stateflow
atomic subcharts. Atomic subcharts allow you to reuse the same state or subchart across
multiple Stateflow charts.
Checking Systems Programmatically With the Model Advisor
Previously, you could check systems programmatically using the
Simulink.ModelAdvisor class, requiring many steps to check only one system at
a time. Now you can check systems using the ModelAdvisor.run function. Using this
function, you can create a MATLAB file for distribution that specifies a list of checks or a
Model Advisor configuration file to run against any number of systems simultaneously.
Additionally, the following functions are available for reviewing results. You can use
these functions to determine which checks failed on which systems and archive the
results for accessing at a later time.
Use...
To...
ModelAdvisor.run
Run Model Advisor checks on systems.
ModelAdvisor.summaryReport
Open Model Advisor Command-Line
Summary report in a web browser.
view
View Model Advisor check results for a
system in a web browser.
viewReport
View Model Advisor run results for a
system in a web browser, the Model
Advisor GUI, or the Command Window.
If you have a Parallel Computing Toolbox license and a multicore machine, to improve
performance, you can run the Model Advisor on multiple systems in parallel.
For details, see the ModelAdvisor.run reference page and Checking Systems
Programmatically in the Simulink Verification and Validation documentation.
MathWorks Check IDs for the Model Advisor Updated
The check IDs for MathWorks checks in the Model Advisor are updated to use a
consistent format. To easily determine check IDs, use the:
11-4
• Model Advisor context menu to return the check ID to the workspace.
• ModelAdvisor.lookupCheckID function to look up the new check ID.
For details, see Finding Check IDs in the Simulink Verification and Validation
documentation.
Compatibility Considerations
The Model Advisor continues to recognize check IDs that were available prior to R2010b.
Using the previous IDs in scripts and functions requires more processing time than if you
use the new check IDs. To avoid a performance impact, update scripts and functions to
use the new check IDs.
In prior releases, the following Simulink.ModelAdvisor methods returned the
previous check IDs. In R2010b, the methods return the new check IDs:
getCheckAll
getCheckForGroup
getCheckForTask
getSelectedCheck
verifyCheckRan
New and Enhanced Model Advisor Checks
The Simulink Model Advisor includes new and updated verification and validation
checks.
MathWorks Automotive Advisory Board Checks
The MathWorks Automotive Advisory Board subfolder now includes Check
transition actions in Stateflow charts. Use this check to review your system against
MAAB guideline db_0151: State machine patterns for transition actions.
For more information, see MathWorks Automotive Advisory Board Checks in the
Simulink Verification and Validation User's Guide.
11-5
R2010a
Version: 2.7
New Features
Bug Fixes
Compatibility Considerations
R2010a
Coverage Support for Dead Zone Block
The Simulink Verification and Validation software now records coverage for the Dead
Zone block.
Coverage Support for the Simulink Design Verifier Functions in MATLAB
Function Blocks
The Simulink Verification and Validation software now records coverage for the following
Simulink Design Verifier functions in MATLAB Function blocks:
• sldv.assume
• sldv.condition
• sldv.prove
• sldv.test
Coverage Support for Trigger Ports in Model Blocks
The Simulink Verification and Validation software records coverage for a triggered Model
block.
Requirements Support for MuPAD Documents
The Requirements Management Interface (RMI) now allows you to create requirements
links from Simulink model objects to link targets in MuPAD® notebooks.
Improved Reports About Requirements Links in Models
In the requirements reports, the Requirements Management Interface (RMI) reporting
capability includes the following improvements:
• Navigation to Simulink model objects with requirements
• Improved table design in requirements reports to accommodate additional detail
about requirements
New Capability to Tag and Filter Model Requirements
The Requirements Management Interface (RMI) now allows filtered highlighting and
reporting through the user tag attribute. Use this feature to review links with certain
12-2
associated user tags. You can configure your settings to automatically apply specified
tags when using selection-based linking. Manage these user tags with the new rmitag
function.
Improved IBM Rational DOORS Synchronization
The Requirements Management Interface (RMI) synchronization of Simulink models
with the IBM Rational DOORS software now provides control of change propagation
for requirements links created in DOORS or Simulink. You can configure the
synchronization to remove outdated links in DOORS whose corresponding links you have
already deleted from Simulink. You can also configure the synchronization to remove
outdated links in Simulink whose corresponding links you have already deleted from
DOORS. When you delete objects with requirements from your Simulink model, you can
automatically remove links in DOORS.
Function rminav Removed
The Simulink Verification and Validation software no longer supports the rminav
function. To view model requirements, open the Model Explorer by selecting View >
Model Explorer or entering the daexplr command. In the Model Explorer, click the
Highlight items with requirements on model icon.
Compatibility Considerations
In R2009b, the rminav command opened the Model Explorer.
New and Enhanced Model Advisor Checks
The Simulink Model Advisor includes new and updated verification and validation
checks.
DO-178B Checks
The DO-178B Check subfolder now includes:
• Check state machine type of Stateflow charts
• Check Stateflow charts for ordering of states and transitions
• Check Stateflow debugging settings
12-3
R2010a
The checks in the DO-178B Checks subfolder are reformatted for consistency in the
results format.
For more information, see DO-178B Checks in the Simulink Verification and Validation
documentation.
IEC 61508 Checks
The IEC 61508 Checks subfolder now includes Check state machine type of Stateflow
charts.
For more information, see IEC 61508 and ISO 26262 Checks in the Simulink Verification
and Validation documentation.
MathWorks Automotive Advisory Board Checks
The MathWorks Automotive Advisory Board subfolder now includes:
• Check usage of return values from a graphical function in Stateflow charts
• Check for pointers in Stateflow charts
• Check for event broadcasts in Stateflow charts
• Check for MATLAB expressions in Stateflow charts
• Check for bitwise operations in Stateflow charts
• Check for comparison operations in Stateflow charts
• Check for unary minus operations on unsigned integers in Stateflow charts
• Check for equality operations between floating-point expressions in Stateflow charts
The checks in the MathWorks Automotive Advisory Board subfolder are reformatted
for consistency in the results format.
For more information, see MathWorks Automotive Advisory Board Checks.
Modeling Guidelines Documentation Moved into Simulink Documentation
The Modeling Guidelines for High-Integrity Systems and MathWorks Automotive
Advisory Board Control Algorithm Modeling Guidelines Using MATLAB, Simulink, and
Stateflow documentation is now in the Simulink documentation.
For more information, see Modeling Guidelines in the Simulink documentation.
12-4
R2009bSP1
Version: 2.6.1
Bug Fixes
R2009b
Version: 2.6
New Features
Bug Fixes
Compatibility Considerations
R2009b
New Coverage Reporting for Variable-Size Signals
In R2009b, signal sizes in Simulink models can change during execution to facilitate
modeling systems with varying environments, resources, and constraints. The Simulink
Verification and Validation software can report the minimum, maximum, and allocated
space for all variable-size signals in a model, as recorded during simulation.
To enable this feature, in the Coverage Settings dialog box, on the Coverage tab, select
the Signal Size option.
Model Coverage for Simulink Design Verifier Blocks
The Simulink Verification and Validation model coverage tool can collect model coverage
data for Simulink Design Verifier blocks. Using this feature during simulation, you can
verify Simulink Design Verifier generated test harnesses and user-defined requirements.
The model coverage tool collects model coverage data for the following Simulink Design
Verifier blocks:
• Proof Assumption
• Proof Objective
• Test Condition
• Test Objective
To enable this feature, in the Coverage Settings dialog box, on the Coverage tab, select
Simulink Design Verifier.
Force Block Reduction Off During Simulation
The Simulink Verification and Validation software can override the value of the Simulink
Block reduction parameter. When you set this option, the simulation records coverage
for all blocks in the model.
To enable this feature, in the Coverage Settings dialog box, on the Options tab, select
Force block reduction off.
Compatibility Considerations
Previously, model coverage ignored the value of the Simulink Block reduction
parameter, creating incompatibilities between the model coverage data and the
14-2
generated code coverage data. In R2009b, you can select Force block reduction off to
override the Block reduction parameter and collect coverage for all blocks in the model.
Improved RMI Highlighting and Reporting
The Requirements Management Interface (RMI) has the following improvements to its
highlighting and reporting capabilities:
• Differential highlighting of blocks and subsystems to easily locate model objects with
requirements links
• Real-time update of highlighted view to reflect the current state of the model
requirements links
• Improved requirements report that includes a document summary, and details about
signal group requirements and objects with missing requirements
• New interface for modifying settings for the requirements report generation that is
available to users who do not have a Simulink Report Generator license
• IBM Rational DOORS module paths stored with the requirements information
for easier review. For requirement links created before R2009b, the module path
information is still saved only in the DOORS module.
Create Custom Configurations Using the Model Advisor Configuration
Editor
The Model Advisor Configuration Editor expedites creating and deploying custom
configurations of the Model Advisor. The Configuration Editor assists with:
• Adding MathWorks and custom checks to your custom configuration with drag and
drop.
• Creating new folders in your custom configuration from a toolbar icon.
• Deploying custom configurations in a MAT file.
For more information, see Organizing Checks and Folders Using the Model Advisor
Configuration Editor and How to Deploy Custom Configurations in the Simulink
Verification and Validation documentation.
Licensing Revised for the Model Advisor
Previously, the Model Advisor populated the list of checks and folders based on the
licenses available to you. When you ran checks, the software did not require a license
14-3
R2009b
checkout. In R2009b, the Model Advisor performs a checkout of the Simulink Verification
and Validation license when you run Simulink Verification and Validation checks. For
a list of Simulink Verification and Validation checks, see Model Advisor Checks in the
Simulink Verification and Validation documentation.
Compatibility Considerations
The Model Advisor performs a checkout of a Simulink Verification and Validation license
when you run:
• Checks in the Simulink Verification and Validation folder
• Custom checks
If you do not have a Simulink Verification and Validation license available, when you run
the check, you see an error message that the required license is not available.
New and Enhanced Model Advisor Checks
The Simulink Model Advisor includes new and updated verification and validation
checks.
DO-178B Checks
The DO-178B Check subfolder now includes Check safety-related diagnostic settings for
model initialization.
The checks in the DO-178B Checks subfolder are reformatted for a consistent look and
feel to the results.
For more information, see DO-178B Checks in the Simulink Verification and Validation
User's Guide.
IEC 61508 Checks
The IEC 61508 Checks subfolder now includes Check for model objects that do not link
to requirements.
For more information, see IEC 61508 and ISO 26262 Checks in the Simulink Verification
and Validation documentation.
14-4
Modeling Guidelines for High-Integrity Systems
MathWorks intends this document for engineers developing models and generating
code for high-integrity systems using Model-Based Design with MathWorks products.
This document describes creating Simulink models that are complete, unambiguous,
statistically deterministic, robust, and verifiable. The document focus is on model
settings, block usage, and block parameters that impact simulation behavior or code
generated by the Real-Time Workshop® Embedded Coder™ product.
These guidelines do not assume that you use a particular safety or certification standard.
The guidelines reference some safety standards where applicable, including DO-178B,
IEC 61508, and MISRA C.
You can use the Model Advisor to support adhering to these guidelines. Each guideline
lists the checks that are applicable to that guideline.
For more information, see “Modeling Guidelines for High-Integrity Systems” in the
Simulink Verification and Validation documentation.
14-5
R2009a
Version: 2.5
New Features
Bug Fixes
R2009a
Recording Coverage for External MATLAB Files
MATLAB Function blocks and functions can call external program files. The Model
Coverage Tool extends the model coverage capabilities to record coverage for these files.
By default, this option is disabled; coverage is not collected for external program files.
Enable this option if you want the software to collect and report coverage for all program
files associated with the MATLAB Function blocks. To enable this option, in the
Coverage Settings dialog box, select Coverage for MATLAB files.
API for Customizing Model Advisor Results
In R2009a, there is a new API to customize the results of the Model Advisor for a
common look and feel for all of your customized checks. The API includes templates for
you to organize the results in tables or lists. For more information, see Customizing the
Model Advisor in the Simulink Verification and Validation User's Guide.
New and Enhanced Model Advisor Checks
The Simulink Model Advisor includes new and updated verification and validation
checks.
DO-178B Checks
The DO-178B Check subcategory includes the following new checks:
• Check for blocks that do not link to requirements
• Check usage of Math blocks
For more information, see DO-178B Checks in the Simulink Verification and Validation
documentation.
IEC 61508 Checks
The checks in the IEC 61508 Checks subfolder are reformatted for a consistent look and
feel to the results. For more information, see IEC 61508 and ISO 26262 Checks in the
Simulink Verification and Validation documentation.
15-2
Modeling Standards for MAAB Checks
There is a new Modeling Standards for MAAB subfolder in the By Task folder of the
Model Advisor, which includes subfolders that organize the MAAB checks so you can
more easily determine which checks you want to run.
MathWorks Automotive Advisory Board Control Algorithm Modeling
Guidelines Using MATLAB, Simulink, and Stateflow Included in Help
The MathWorks Automotive Advisory Board (MAAB) involves major automotive original
equipment manufacturers (OEMs) and suppliers in the process of evolving MathWorks
controls, simulation, and code generation products, including the Simulink, Stateflow,
and Real-Time Workshop products. An important result of the MAAB has been the
“MathWorks Automotive Advisory Board Control Algorithm Modeling Guidelines Using
MATLAB, Simulink, and Stateflow.” Help for the Simulink Verification and Validation
product now includes these guidelines. The MAAB guidelines link to relevant Model
Advisor MAAB check help and MAAB check help links to relevant MAAB guidelines.
For more information on the MAAB guidelines, see “MathWorks Automotive Advisory
Board Control Algorithm Modeling Guidelines Using MATLAB, Simulink, and
Stateflow”. For information on the Model Advisor MAAB checks, see “MathWorks
Automotive Advisory Board Checks.”
15-3
R2008b
Version: 2.4
New Features
Bug Fixes
R2008b
New and Enhanced Model Advisor Checks
Context-sensitive help is now available for all Model Advisor checks.
DO-178B Checks
The DO-178B Check subcategory includes these new and enhanced checks:
• Check safety-related diagnostic settings for saving — This new check helps enforce
and document adherence to coding standards for DO-178B, Software Considerations
in Airborne Systems and Equipment Certification.
• Check safety-related diagnostic settings for signal data — This check now checks
whether the parameter SignalRangeChecking is set to error.
• New Action box for the following checks that you can use to automatically fix failures:
• Check safety-related optimization settings
• Check safety-related diagnostic settings for solvers
• Check safety-related code generation settings
• Check safety-related diagnostic settings for compatibility
• Check safety-related diagnostic settings for bus connectivity
• Check safety-related diagnostic settings for signal connectivity
• Check safety-related diagnostic settings for data store memory
• Check safety-related diagnostic settings for data used for debugging
• Check safety-related diagnostic settings for parameters
• Check safety-related diagnostic settings for signal data
• Check safety-related diagnostic settings that apply to function-call connectivity
• Check safety-related diagnostic settings for model referencing
• Check safety-related model referencing settings
• Check safety-related diagnostic settings for sample time
• Check safety-related diagnostic settings for type conversions
• Check safety-related diagnostic settings for saving
For more information, see DO-178B Checks in the Simulink Verification and Validation
documentation.
16-2
IEC 61508 Checks
The IEC 61508 Checks subcategory includes a new check, Check usage of Stateflow,
that helps enforce and document compliance with coding standards for functional
safety in electrical, electronic, and programmable electronic systems, as the IEC 61508
standard outlines.
For more information, see IEC 61508 and ISO 26262 Checks in the Simulink Verification
and Validation documentation.
MathWorks Automotive Advisory Board Checks
The MathWorks Automotive Advisory Board Checks subcategory includes new
checks that have been implemented to support the MathWorks Automotive Advisory
Board (MAAB) 2.0 rules:
• Check for difference in font and font sizes
• Check Transition orientations in Flowcharts
• Check for display of non-default block attributes
• Check signal line labels
• Check for propagated labels on Signal lines
• Check default Transition placement on Stateflow Charts
• Check setting Stateflow Graphical Function return value
• Check for proper use of Switch Blocks
• Check for proper use of Signal Busses and Mux block usage
For more information, see MathWorks Automotive Advisory Board Checks in the
Simulink Verification and Validation documentation.
Improved Selection-Based Linking
To create links between a model and a Microsoft Word or Microsoft Excel file, you
can open the file from within both the model and the requirements document. The
Requirements Management Interface (RMI) establishes communication with the
application when you initiate selection-based linking.
For more information, see Links Between Models and Requirements in the Simulink
Verification and Validation documentation.
16-3
R2008b
Enhanced Model Coverage Report
The Model Coverage report now includes information about:
• Model being analyzed
• Simulation optimization options
• Model coverage options
For more information, see Creating Requirements Reports in the Simulink Verification
and Validation documentation.
16-4
R2008a+
Version: 2.3.1
Bug Fixes
R2008a
Version: 2.3
New Features
Bug Fixes
R2008a
Enhanced Coverage Support for Referenced Models
The previous release introduced coverage support for referenced models, but only by
means of functions that you invoke programmatically. This release includes the following
enhancements to coverage support for referenced models:
• Redesigned Coverage Settings dialog box now includes controls that allow you to
enable coverage for referenced models graphically.
• New Coverage by Model summary that allows you to navigate easily to coverage
reports associated with referenced models in a hierarchy.
New Requirements Submenu in Model Explorer
Full access to the Requirements Management Interface is now available from within
the Model Explorer. In this release, a Requirements submenu replaces the Edit
requirements item that appears in Model Explorer context menus. This new submenu
provides several options for adding requirements to model elements and specifying link
preferences. This same submenu is available by right-clicking objects in a Simulink
model or a Stateflow chart.
Model Advisor Checks for Modeling Standards Enhanced
The Simulink Model Advisor has been enhanced with new and updated verification and
validation checks.
• In the Task Hierarchy tree, the check category By Product > Simulink
Verification and Validation > Modeling Standards includes the new subcategory
IEC 61508 Checks.
• The IEC 61508 Checks subcategory includes new checks that help enforce and
document adherence to coding standards for functional safety in electrical, electronic,
and programmable electronic systems, as the IEC 61508 standard outlines. For
descriptions of the IEC 61508 checks, see Model Advisor Checks in the Simulink
Verification and Validation documentation.
• The IEC 61508 checks also appear under the new category By Task > Model-Based
Design for IEC 61508.
• Some MathWorks Automotive Advisory Board Checks have been updated.
18-2
For Information on How To...
See...
Develop models and code that comply with Guidelines and Standards in the Real-Time
industry standards and guidelines, such as Workshop Embedded Coder documentation
the IEC 61508 standard and MathWorks
Automotive Advisory Board (MAAB)
guidelines
Use the Model Advisor
Consulting the Model Advisor in Simulink
User's Guide
Customize the Model Advisor with your
own tasks and checks
Customizing the Model Advisor in the
Simulink Verification and Validation
User's Guide
API for Customizing Model Advisor Enhanced
R2008a provides an enhanced API that allows you to customize the behavior of the Model
Advisor for checking and reporting on how well your Simulink models are optimized
for simulation and code generation. The API provides classes and functions for defining
custom checks and tasks, and writing your own callback functions. For more information,
see Customizing the Model Advisor in the Simulink Verification and Validation User's
Guide.
18-3
R2007b+
Version: 2.2.1
Bug Fixes
R2007b
Version: 2.2
New Features
Bug Fixes
R2007b
Model Coverage Support for Referenced Models
This release introduces model coverage support for referenced models that operate in
Normal mode. That is, you can now record coverage for Model blocks whose Simulation
mode parameter specifies Normal. Toward that end, this release provides three new
functions:
• cvsimref
• cv.cvdatagroup
• cv.cvtestgroup
For more information, see Using Model Coverage Commands for Referenced Models in
the Simulink Verification and Validation User's Guide.
Model Advisor Checks for Modeling Standards Enhanced
The Simulink Model Advisor has been enhanced with new and updated verification and
validation checks.
• In the Task Hierarchy tree, the check category By Product > Simulink
Verification and Validation > Modeling Standards includes two new
subcategories: DO-178B Checks and MathWorks Automotive Advisory Board
Checks.
• The DO-178B Checks subcategory includes new checks that help enforce and
document adherence to coding standards for DO-178B, Software Considerations in
Airborne Systems and Equipment Certification. If a piece of software will be flying
on a commercial aircraft, the development and verification process must comply with
DO-178B. For descriptions of the DO-178B checks, see Model Advisor Checks in the
Simulink Verification and Validation documentation.
• The DO-178B checks also appear under the new category By Task > Safety Critical
for DO-178B.
• Checks listed under By Product > Simulink Verification and Validation
> Modeling Standards in earlier releases, appear under the new subcategory
MathWorks Automotive Advisory Board Checks. These checks verify that
Simulink block diagrams adhere to style guidelines published by the MathWorks
Automotive Advisory Board (MAAB).
• Some MathWorks Automotive Advisory Board Checks have been updated. For
example, the check for “hd_0001, Prohibited Simulink Sink and Data Store blocks”
20-2
was modified to allow Data Store Memory, Data Store Read, and Data Store Write
blocks and the check for “db_0146, Triggered or enabled subsystems” was modified to
include For Iterator, While Iterator, and Case blocks.
For Information on How To...
See...
Use the Model Advisor
Consulting the Model Advisor in Simulink
User's Guide
Customize the Model Advisor with your
own tasks and checks
Customizing the Model Advisor in the
Simulink Verification and Validation
User's Guide
API for Customizing Model Advisor HTML Reports
This release provides a new API that allows you to customize Model Advisor HTML
reports. The API provides classes and methods for formatting custom HTML reports,
making it easier to create, understand, and maintain Model Advisor HTML reports. See
Formatting Model Advisor Results in the Simulink Verification and Validation User's
Guide.
20-3
R2007a+
Version: 2.1.1
Bug Fixes
R2007a
Version: 2.1
Bug Fixes
R2006b
Version: 2.0
New Features
Bug Fixes
R2006b
Requirement Links Checking
This release introduces Model Advisor tasks for ensuring the consistency and validity of
requirement links in a Simulink block diagram. These checks enable you to identify and
fix the following situations:
• The requirements document is missing.
• The location (e.g., bookmark, line number, anchor) specified within the requirements
document is invalid.
• The description of a selection-based link does not match its requirements document
text.
• The requirements document path does not match your preferred path type (i.e.,
absolute or relative).
See Consulting the Model Advisor in Simulink User's Guide for more information about
using Model Advisor.
Modeling Standards Checking
This release introduces Model Advisor tasks for ensuring that a Simulink block diagram
adheres to the style guidelines published by the MathWorks Automotive Advisory
Board (MAAB). See Consulting the Model Advisor in Simulink User's Guide for more
information about using Model Advisor. For information about the MAAB modeling style
guidelines, see http://www.mathworks.com/industries/auto/maab.html.
23-2
R2006a
Version: 1.1.2
No New Features or Changes
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement