Documentation

Simulink Verification and Validation Release Notes

R2016a

New Features, Bug Fixes

Model Metric APIs: Programmatically run and create metrics

的DO-331, IEC 61508, IEC 62304, ISO 26262, and EN 50128 standards recommend that your model and code comply with size, complexity, and readability requirements. To help you assess your model, use the model metrics available with万博1manbetx®Verification and Validation™. You can also use APIs to create your own model metrics, compute metrics, and export metric data.

Action Use See

Create your own model metrics.

Model metric customization APIs

Create Model Metrics by Using APIs

New classes:

Programmatically assess the size, complexity, and readability of your model.

Model metric APIs

收集度量模型编程

New classes:

Interactively assess the size, complexity, and readability of your model. Previously available in R2015b.

Model Advisor metric checks

Run Checks for Model Metrics

Model Advisor Checks for Medical Standard IEC 62304: Check models to comply with medical standards

To check for model compliance to medical standard IEC 62304, run the Model Advisor checks in theBy Task>Modeling Standards for IEC 62304folder.

Model Advisor Standards Checks: Check models for naming standard compliance

模型顾问包括标准检查哟u can use to verify that your model complies with high-integrity modeling guidelinehisl_0032: Model object names.

You can use the Model Advisor Configuration Editor to specify the naming standard and model objects that the checks flag.

DO-178C/DO-331

的Model AdvisorBy Taskfolder contains theModeling Standards for DO-178C/DO-331check,Check model object names.

IEC 61508, IEC 62304, ISO 26262, and EN 50128

的Model AdvisorBy Taskfolder containsModeling Standards for IEC 61508,Modeling Standards for IEC 62304,Modeling Standards for ISO 26262, andModeling Standards for EN 50128check,Check model object names.

Model Advisor Check Parameterization: Control check behavior by using input parameters

In the Model Advisor Configuration Editor, to specify conditions that control check behavior, select input parameters.

Modeling Standard Check Input Parameters
DO-178C / DO-331 Check model object names

To specify the check naming standard and model objects, selectMAAB,Custom, orNonefor each of the following model objects:

  • Blocks

  • Signals

  • Parameters

  • Busses

  • Stateflow®objects

如果you selectCustom, you can enter your own regular expression for flagging the specified model object names.

IEC 61508, IEC 62304, ISO 26262, and EN 50128 Check model object names
MAAB Check character usage in block names

To specify the checkNaming standardfor blocks, selectMAAB 3.0orCustom. If you selectCustom, you can enter your own regular expression for flagging the block names.

Check port block names

To specify the checkNaming standardfor Inport and Outport blocks, selectMAAB 3.0orCustom. If you selectCustom, you can enter your own regular expression for flagging the Inport and Outport block names.

Check subsystem names

To specify the checkNaming standardfor subsystem names, selectMAAB 3.0orCustom. If you selectCustom, you can enter your own regular expression for flagging the subsystem block names.

Check for mixing basic blocks and subsystems In theInput Parameterspane, to:
  • Allow the blocks specified by MAAB, fromStandard, selectMAAB 3.0. TheBlock type listtable provides the blocks that MAAB 3.0 allows at any model level.

  • To specify blocks to either allow or prohibit, fromStandard, selectCustom. InTreat blocktype list as, selectAllowedorProhibited. In theBlock type listtable, you can add or remove blocks.

Previously, you specified only blocks and subsystems that the check allowed.

Check for prohibited blocks in discrete controllers

In theInput Parameterspane, to:

  • Prohibit the blocks as specified in MAAB, fromStandard, selectMAAB 3.0. TheBlock type listtable provides the blocks that MAAB 3.0 prohibits inside controllers.

  • To specify blocks to either allow or prohibit, fromStandard, selectCustom. InTreat blocktype list as, selectAllowedorProhibited. In theBlock type listtable, you can add or remove blocks.

Previously, you specified only blocks and subsystems that the check prohibited.

Check for prohibited sink blocks

In theInput Parameterspane, to:

  • Prohibit the blocks as specified by MAAB 3.0, fromStandard, selectMAAB 3.0. TheBlock type listtable provides the sink blocks that MAAB 3.0 prohibits.

  • To specify blocks to either allow or prohibit, fromStandard, selectCustom. InTreat blocktype list as, selectAllowedorProhibited. In theBlock type listtable, you can add or remove blocks.

Previously, you specified only blocks and subsystems that the check prohibited.

To specify the input parameters, use the Model Advisor Configuration Editor.

  1. Open the Model Configuration Editor and navigate to the check.

  2. In theInput Parameterpane, specify the parameters.

  3. ClickApply.

  4. 保存配置。当您运行检查with this configuration, the checks flag the model conditions that you specified.

Code Coverage for Generated Code: Measure testability of generated code with coverage analysis

如果you have Embedded Coder®installed,Simulink Verification and Validationmeasures the coverage of code generated from models in SIL mode. For more information, seeCoverage for Models in Software-in-the-Loop (SIL) Mode.

要求的事情uirements Linking: Trace requirements to objects in test harnesses and steps in Test Sequence blocks

如果you haveSimulink Test™installed, you can associate requirements with objects in test harnesses and with steps in Test Sequence blocks in Simulink diagrams. For more information, seeLink Test Cases to Requirements Documents.

Coverage Data Collection: Automatically save cumulated coverage data to file

When you record coverage for a model,Simulink Verification and Validationrecords the current coverage data and cumulated coverage data to a .cvdata file on the disk.

Model Coverage Analysis: Justification editor to identify acceptable instances of incomplete coverage from report

When you create a coverage filter for a construct, you choose betweenExcludedandJustifiedfiltering modes.Simulink Verification and Validationincludes justified constructs in the coverage report as a subset of the constructs that achieve coverage.

For more information, see:

Coverage results for test files, test suites, and test cases inSimulink Test

如果you have aSimulink Testlicense, you can aggregate coverage results for test cases, test suites, and test files using the test manager. You can include coverage in the test manager results report. SeeCollect Coverage in Tests.

R2015aSP1

Bug Fixes

R2015b

New Features, Bug Fixes, Compatibility Considerations

Model Advisor checks for size, cyclomatic complexity, and readability model metrics

To display model information and help you assess your model and code, you can run the count, complexity and readability model metrics checks in the applicableBy Task>Model Metricssubfolder. The following table lists the model metric checks. For an example of running checks for model metrics, seeRun Checks for Model Metrics.

Model Advisor reports in Adobe PDF and Microsoft Word formats

When the Model Advisor runs checks, by default, it generates an HTML report of check results. On Windows®platforms, you can now generate Model Advisor reports in Adobe®PDF and Microsoft®词。docx格式。当你运行一个模型顾问analysis, to generate a Model Advisor report in PDF or .docx format, in the right-pane of the Model Advisor window, selectGenerate Report. For more information, seeGenerate Model Advisor Reports in Adobe PDF and Microsoft Word Formats.

Model Advisor check support for JMAAB Guidelines, Version 4.0

的MathWorks®Automotive Advisory Board (MAAB) checks support compliance with MAAB Control Algorithm Modeling Guidelines, Version 3.0. A subset of the MAAB checks support compliance with the Japan MBD Automotive Advisory Board (JMAAB) Control Algorithm Modeling Guidelines, Version 4.0. For a summary of the MAAB check support for the MAAB and JMAAB Guidelines, seeModel Checks for MathWorks Automotive Advisory Board (MAAB) Guideline Compliance.

To download the JMAAB Control Algorithm Modeling Guidelines, Version 4.0, see theJMAABwebsite.

Block execution recorded during model coverage analysis

Simulink Verification and Validationcan perform several types of coverage analysis. The model coverage tool now records execution coverage for each block in a model. Block execution coverage determines whether or not a block is executed during model simulation. For more information, seeTypes of Model Coverage.

.

Manage model coverage parameters within a model configuration set

A model configuration set stores model coverage parameters for a model when you load or create a model. This feature allows for the storage of model coverage configuration parameters that you can reuse for multiple models or model variants. For more information, seeAbout Model Configurations.

Model Advisor support for MISRA C:2012

Model Advisor checks support compliance with MISRA C:2012. Previously, Model Advisor checks supported compliance with MISRA C:2004. The check documentation references the applicable MISRA C:2012 directive or rule. For information about MISRA C®versions and updates, seeMISRA C Guidelinesin the Embedded Coder documentation.

API to run Model Advisor across model hierarchy

Use instances ofAdvisor.Applicationto run Model Advisor checks across a model hierarchy. You can useAdvisor.Applicationto:

  • Run checks on referenced models.

  • Select model components for Model Advisor analysis.

  • Select checks to run during Model Advisor analysis.

如果you have a large model with subsystems and model references, consider usingAdvisor.Application. If you want to leverage parallel processing, useModelAdvisor.runto run Model Advisor checks on your model.

Model Advisor check exclusions saved to model SLX file

When you exclude blocks and charts from Model Advisor checks, you can save the exclusion information to the model SLX file. In the Model Advisor Exclusion Editor dialog box, selectStore exclusions in model file. When you open a model SLX file, the model contains the Model Advisor check exclusions. Previously, the exclusion information was stored only in Model Advisor exclusion files<model_name>_exclusions.xmlattached to a model. For more information, seeLimit Model Checks.

Compatibility Considerations

You can still use Model Advisor exclusion files<model_name>_exclusions.xmlto store exclusion information for your Model Advisor analysis. When you open a model that has an attached exclusion file, to help you manage exclusions, consider saving the exclusions in the model file.

Model Advisor check input parameterization

You can use input parameters to control the blocks that are flagged when you run the following checks.

To change the list of blocks that the checks flag, use the Model Advisor Configuration Editor.

  1. Open the Model Configuration Editor and navigate to the check.

  2. In theInput Parameterpane, add or remove blocks.

  3. ClickApply.

  4. 保存配置。When you run the checks using this configuration, the checks flag the blocks that you specified.

R2015a

New Features, Bug Fixes

Coverage measurement for C S-functions

Model coverage is supported for C/C++ S-Functions. The coverage results forS-Functionblocks 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.

为功能块生成覆盖率报告:

  1. When creating S-Functions, enable support for coverage.

  2. When generating coverage report, enable support for S-Functions.

的following coverage metrics are reported for S-Functions:

For more information, see:

Model Advisor checks for MATLAB functions

的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

的Model AdvisorBy Taskfolder containsModeling Standards for IEC 61508,Modeling Standards for ISO 26262, andModeling Standards for EN 50128checks:

DO-178C/DO-331

的Model AdvisorBy Taskfolder containsModeling Standards for DO-178C/DO-331checks:

MathWorks Automotive Advisory Board

的Model AdvisorBy Task > Modeling Standards for MAAB > MATLAB Functionsfolder contains new checks:

R2014b

New Features, Bug Fixes

Model coverage for relational boundary values

的model coverage tool introduces a relational boundary coverage metric.

关系边界覆盖检查块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, seeRelational Boundary Coverage.

要求的事情uirements 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

要求的事情uirements traceability highlighting opens a separate Requirements Details window that shows content from linked documents in Microsoft Word,Microsoft Excel®, and IBM®理性的®DOORS®. To open the Requirements Details window, in the Simulink Editor, selectAnalysis>要求的事情uirements Traceability>Highlight Model. Select a model object with requirements links to see content from linked requirements documents in the Requirements Details window.

如果you haveSimulink Report Generator™installed, you can include requirements information in a Web view. In the Simulink Editor, selectFile>Export Model to>WebIn the Web View dialog box, open theOptional Viewstab and selectInclude Requirements view. Alternatively, in the Simulink Editor, selectAnalysis>要求的事情uirements 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 theInformerpane underneath the model.

R2014a

New Features, Bug Fixes

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 inView Coverage Results in a Model. For more information, seeExport 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, seeCreate Check for Model Configuration Parameters.

Condition coverage for Relational Operator blocks

的model coverage tool records condition coverage forRelational Operator,比较恒定的, andCompare to Zeroblocks. For more information, seeModel Objects That Receive Coverage.

Model Advisor checks for MATLAB Code Analyzer messages

DO-178C/DO-331

的Model AdvisorBy Taskfolder contains theseModeling Standards for DO-178C/DO-331checks:

IEC 61508, ISO 26262, and EN 50128

的Model AdvisorBy Taskfolder contains theseModeling Standards for IEC 61508,Modeling Standards for ISO 26262, andModeling Standards for EN 50128checks:

MathWorks Automotive Advisory Board

的Model AdvisorBy Task > Modeling Standards for MAAB > MATLAB Functionsfolder contains this new check:

Japanese language localization support

Simulink Verification and Validationis available in Japanese for Japanese localized systems. For more information, seeInternationalization.

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 nameschecks the display attributes of all blocks to verify compliance with MathWorks Automotive Advisory Board guidelinejc_0061: Display of block names. Previously, the check did not verify compliance of subsystem block names. You can findCheck the display attributes of block names在模型中顾问By Task > Modeling Standards for MAAB > Simulinkfolder.

IEC 61508, ISO 26262, and EN 50128 Check usage of Math Operations blocks

IEC 61508, ISO 26262, and EN 50128Check usage of Math Operations blocksverifies 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 blocksis available in theBy Task>Modeling Standards for IEC 61508,Modeling Standards for ISO 26262, andModeling Standards for EN 50128folders.

DO-178C/DO-331 Check usage of Math Operations blocks

DO-178C/DO-331Check usage of Math Operations blocksverifies the use of the following Math Operation blocks:

  • 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-331Check usage of Math blocksverified the use of the Math Function blocks.Check usage of Math blocksis no longer available in theBy Task > Modeling Standards for DO-178C/DO-331folder.

Check usage of Math Operations blocksis available in the Model AdvisorBy Task > Modeling Standards for DO-178C/DO-331folder.

R2013b

New Features, Bug Fixes, Compatibility Considerations

要求的事情uirements 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, seeMATLAB Code Traceability.

Reset option for cumulative model coverage results

如果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 theResultstab, clickClear data. For more information, seeSpecify Model Coverage Options.

EN 50128 modeling standard checks for railway applications

的Model Advisor includes model checks for compliance to the EN 50128 standard. The checks are available in theBy Task > Modeling Standards for EN 50128folder.

Model Advisor checks for MATLAB Function blocks and input/output range specifications

MATLAB Function blocks

的Model Advisor includes checks for MATLAB Function blocks to comply with modeling standards.

IEC 61508, ISO 26262, and EN 50128

的Model AdvisorBy Taskfolder containsModeling Standards for IEC 61508,Modeling Standards for ISO 26262, andModeling Standards for EN 50128checks:

DO-178C/DO-331

的Model AdvisorBy Taskfolder containsModeling Standards for DO-178C/DO-331checks:

MathWorks Automotive Advisory Board

的Model AdvisorBy Task > Modeling Standards for MAAB > MATLAB Functionsfolder contains new checks:

Inport and Outport range specifications

的Model Advisor includes checks for MATLAB Function blocks to comply with modeling standards.

IEC 61508, ISO 26262, and EN 50128

的Model AdvisorBy Taskfolder containsModeling Standards for IEC 61508,Modeling Standards for ISO 26262, andModeling Standards for EN 50128checks:

ModelAdvisor.runoption for parallel processing

如果you have a Parallel Computing Toolbox™ license, you can check multiple systems in parallel by using theModelAdvisor.runfunction with'ParallelMode'set to'On'. By default,‘ParallelMode'is set to'Off'.

Compatibility Considerations

When you useModelAdvisor.runwith'ParallelMode'set to'On', MATLAB automatically creates a parallel pool. Previously, when usingModelAdvisor.runto check multiple systems in parallel, you had to open a parallel pool.

R2013a

New Features, Bug Fixes

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, selectAnalysis>Coverage>Settings. In the Coverage Settings dialog box, in the Coverage metrics group, selectSaturation on integer overflow.

rmiprefcommand for managing requirements traceability preferences

rmipreffunction provides a command-line interface that enables you to manage requirements traceability preferences.

For more information on requirements traceability preferences, see的要求的事情uirements 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 Advisorto help configure your model to meet code generation objectives.

  • Upgrade Advisorto help upgrade models.

  • Performance Advisorto help improve the simulation performance of your model.

New Model Advisor Checks for Modeling Standards

的Simulink Model Advisor includes new modeling standards checks.

IEC 61508 and ISO 26262 Checks

的Model AdvisorBy Task>Modeling Standards for IEC 61508andModeling Standards for ISO 26262folders contain a new check to replaceCheck for questionable constructs:

DO-178C/DO-331 Checks

的Model AdvisorBy Taskfolder contains a newModeling Standards for DO-178C/DO-331check to replaceIdentify questionable blocks within the specified system:

R2012b

New Features, Bug Fixes, Compatibility Considerations

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. TheSimulink Verification and Validationsoftware uses requirements links labels in context menus, generated reports, code comments, and consistency checks.

Using thermicommand, 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

如果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 thermicommand.

要求的事情uirements linking for Simulink annotations

You can create requirements links to and fromSimulink.Annotationobjects 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.

要求的事情uirements 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 underStorage>Default storage location for requirements links data, selectStore externally (in a separate *.req file).

Compatibility Considerations

如果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.reqfile by selectingAnalysis>要求的事情uirements>Move to File.

Coverage filtering for Stateflow events

You can exclude Stateflow events from recording coverage duringSimulink Verification and Validationmodel coverage collection. For more information, seeFilter a Stateflow Event.

Model Advisor dashboard, providing efficient model guideline checking

的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, seeOverview of the Model Advisor Dashboard.

Model Advisor checks for library models and the DO-178C/DO-331 standard

Library Models

有顾问检查可用来验证模型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 theModelAdvisor.Check.SupportLibraryAPI to create custom checks for library models.

DO-178C/DO-331 Standard

的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

  • 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, seeRadio 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, seeCustomize Requirements Report Using the RMI SettingsandLink from External Applications.

R2012a

New Features, Bug Fixes, Compatibility Considerations

Coverage Metric for Blocks with Saturate on Integer Overflow Parameter

In R2012a, theSimulink Verification and Validationmodel coverage tool provides coverage for blocks when you select theSaturate on Integer Overflow Coverageparameter 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 theCoveragetab, select theSaturate on Integer Overflowoption.

Coverage Support forSimulink Design VerifierFunctions Inside Stateflow Charts

Simulink Verification and Validationnow records coverage for the followingSimulink Design Verifier™functions inside Stateflow charts:

For more information, seeSimulink Design Verifier Coverage.

Cumulative Coverage

Simulink Verification and Validationnow provides cumulative coverage for identically configured multiple instances of:

  • Reusable subsystems

  • Stateflow constructs

要求的事情uirements Linking Between Simulink Objects

您现在可以创建请求uirements links between Simulink objects using selection-based linking. This capability allows you to create requirements links between models, enhancing traceability.

To create a requirement link from one model object to another model object:

  1. Right-click the link destination model object and select要求的事情uirements > Select for linking with Simulink.

  2. Right-click the link source model object and select要求的事情uirements > Add link to selected object.

  3. Right-click the link source model object again and select要求的事情uirements. The new link appears at the top of the要求的事情uirementssubmenu.

For more information, seeLinks Between Models and Requirements.

URL-Based Navigation From External Requirements Documents to Simulink Objects

In R2012a, theSimulink Verification and Validationtool 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的要求的事情uirement Settings Dialog Box.

Compatibility Considerations

Compatibility Considerations

Simulink Verification and Validationsoftware continues to recognize navigation links created with ActiveX controls. Additionally, you can create navigation links with ActiveX by selectingUse 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, seeLimiting the Scope of a Model Advisor Analysis.

MathWorks Automotive Advisory Board Checks

In R2012a, the Model AdvisorBy Task > Modeling Standards for MAAB > Stateflowfolder 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, seeMathWorks Automotive Advisory Board Checksin theSimulink Verification and Validationdocumentation.

R2011b

New Features, Bug Fixes, Compatibility Considerations

Condition and MCDC Coverage for If Block Conditions

的如果block now receives condition and MCDC coverage on anyifconditions orelseifconditions that contain logical expressions with multiple conditions. Previously, the If block only received decision coverage.

的如果block receives coverage as follows:

  • 的software measures decision coverage for theifcondition and allelseifconditions.

  • 如果theifcondition or any of theelseifconditions contain a logical expression with multiple conditions, such asu1 & u2 & u3, the software also measures condition and MCDC coverage for each condition in the expression, for example,u1,u2, andu3.

Capability to Store Requirements Information Outside the Model File

的要求的事情uirements Management Interface (RMI) now provides an option to store requirements links information in an external file. The default name for this file ismodel_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 theStoragetab, selectStore externally (in a separate .req file). After setting this option, all models for which you create new requirements links will use external storage.

的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.

Selection-Based Linking for Custom Requirements Documents

如果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要求的事情uirements>Edit/Add Linksand create new requirements using the Requirements dialog box.

For more information, seeCustom Types of Requirements Documents.

Include Requirements Document Data in the Report

的要求的事情uirements 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 theObject TextandObject Headingattributes 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 newRptgenRMI.doorsAttribsfunction.

Before you generate the requirements report, in the Requirements Settings dialog box, on theReporttab, selectInclude details from linked documents.

Microsoft ExcelSupport for Consistency Checking of Simulink References in Requirements Documents

rmifunction has a'checkdoc'option that checks links from requirements documents to Simulink model objects. This option now checksMicrosoft Excelrequirements documents, in addition to Microsoft Word documents and IBM Rational DOORS databases.

要求的事情uirements 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 ismodel_name_report.html.

Changed Format for slvnvruntest and slvnvruncgvtest Output

的output format forslvnvruntestandslvnvruncgvtestchanged in R2011b. In R2011b, the output argument contains the following data for each test case executed in an array ofSimulink.SimulationOutputobjects:

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

如果you have scripts that depend on the output fromslvnvruntestandslvnvruncgvtest, you can temporarily specify the output format. Use the nonvisible fieldoutputFormatin therunOptsstructure thatslvnvruntestoptscreates as follows:

runOpts = slvnvruntestopts; runOpts.outputFormat = 'TimeSeries'; slvnvruntest(model_name, sldvData, runOpts);

or

runOpts = slvnvruntestopts; runOpts.outputFormat = 'StructureWithTime'; slvnvruntest(model_name, data, runOpts);

Conversion of Error and Warning Message Identifiers

For R2011b, error and warning message identifiers have changed inSimulink Verification and Validation.

Compatibility Considerations

Compatibility Considerations

如果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 atry/catchstatement and performs an action based on a specific error identifier.

For example, theSLVNV:simcoverage:InvalidFirstArgumentidentifier has changed toSLVNV:simcoverage:complexityinfo:InvalidFirstArgument. If your code checks forSLVNV:simcoverage:InvalidFirstArgument, you must update it to check forSLVNV:simcoverage:complexityinfo:InvalidFirstArgumentinstead.

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 variableMSGID.

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 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, seeCreating Procedural-Based Model Advisor Configurations.

New Model Advisor Checks

的Simulink Model Advisor includes new modeling standards checks.

ISO 26262 Checks

的Model AdvisorBy Taskfolder contains a newModeling Standards for ISO 26262check:

IEC 61508 Checks

的Model AdvisorBy Taskfolder contains a newModeling Standards for IEC 61508check:

DO-178B Checks

的Model AdvisorBy Taskfolder contains a newModeling Standards for DO-178Bcheck:

Check Input Parameters in Model Advisor Report

In R2011b, the Model Advisor report now displays the check input parameters. For more information, seeViewing and Saving Model Advisor Reportsin the Simulink documentation.

R2011a

New Features, Bug Fixes

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

的要求的事情uirements Management Interface (RMI) provides improved support for managing requirements links on reference blocks.

  • 的newLibrary Block Requirementsmenu 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

slvnvmergedatafunction allows you to combine logged test cases and counterexamples into a single structure. You can use logged data created by runningslvnvlogsignals, or by running aSimulink Design Verifieranalysis.

New and Enhanced Model Advisor Checks

的Simulink Model Advisor includes new and updated modeling standards checks.

IEC 61508 Checks

Previously, theIEC 61508 Checksincluded the check:

  • Check usage of Simulink constructs

This check is replaced by the following new checks:

For more information, see theIEC 61508 and ISO 26262 Checksin the Simulink Verification and Validation documentation.

DO-178B Checks

Previously, theDO-178B Checksincluded 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

的se previously available checks are replaced by the following new checks:

Also available are the new checks:

For more information, see theDO-178B Checksin the Simulink Verification and Validation documentation.

如果,Switch, andSwitch Caseblocks are now searched. See the "Check usage of Port and Subsystems" and "Check usage of Signal Routing blocks" checks for more information.

R2010bSP1

Bug Fixes

R2010b

New Features, Bug Fixes, Compatibility Considerations

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

的new functions perform the following tasks.

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

rmifunction has a new option,'checkdoc', that allows you to validate links from Microsoft Word or IBM Rational DOORS requirements documents to Simulink models.

rmigenerates 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.

New Capability to Link a Requirement to Multiple Model Objects

的要求的事情uirements 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

如果your model, or blocks in your model, has links to requirements in external documents, you can now perform the following tasks without aSimulink Verification and Validationlicense:

  • 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

Simulink Verification and Validationsoftware 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.

Model Coverage Support for Stateflow Atomic Subcharts

Simulink Verification and Validationsoftware 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

以前,你可以检查系统programmatically using theSimulink.ModelAdvisorclass, requiring many steps to check only one system at a time. Now you can check systems using theModelAdvisor.runfunction. 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.

如果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 theModelAdvisor.runreference page andChecking Systems Programmaticallyin theSimulink Verification and Validationdocumentation.

MathWorks Check IDs for the Model Advisor Updated

的check IDs for MathWorks checks in the Model Advisor are updated to use a consistent format. To easily determine check IDs, use the:

  • Model Advisor context menu to return the check ID to the workspace.

  • ModelAdvisor.lookupCheckIDfunction to look up the new check ID.

For details, seeFinding Check IDsin theSimulink Verification and Validationdocumentation.

Compatibility Considerations

的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 followingSimulink.ModelAdvisormethods 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

的Simulink Model Advisor includes new and updated verification and validation checks.

MathWorks Automotive Advisory Board Checks

MathWorks Automotive Advisory Boardsubfolder now includesCheck transition actions in Stateflow charts. Use this check to review your system against MAAB guidelinedb_0151: State machine patterns for transition actions.

For more information, seeMathWorks Automotive Advisory Board Checks.

R2010a

New Features, Bug Fixes, Compatibility Considerations

Coverage Support for Dead Zone Block

Simulink Verification and Validationsoftware now records coverage for the Dead Zone block.

Coverage Support for theSimulink Design VerifierFunctions in MATLAB Function Blocks

Simulink Verification and Validationsoftware now records coverage for the followingSimulink Design Verifierfunctions in MATLAB Function blocks:

Coverage Support for Trigger Ports in Model Blocks

Simulink Verification and Validationsoftware records coverage for a triggered Model block.

要求的事情uirements Support for MuPAD Documents

的要求的事情uirements 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

的要求的事情uirements Management Interface (RMI) now allows filtered highlighting and reporting through the user tag attribute. Use this feature to review links with certain associated user tags. You can configure your settings to automatically apply specified tags when using selection-based linking. Manage these user tags with the newrmitagfunction.

Improved IBM Rational DOORS Synchronization

的要求的事情uirements 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

Simulink Verification and Validationsoftware no longer supports therminavfunction. To view model requirements, open the Model Explorer by selectingView>Model Exploreror entering thedaexplrcommand. In the Model Explorer, click theHighlight items with requirements on modelicon.

Compatibility Considerations

In R2009b, therminavcommand opened the Model Explorer.

New and Enhanced Model Advisor Checks

的Simulink Model Advisor includes new and updated verification and validation checks.

DO-178B Checks

DO-178B Checksubfolder now includes:

的checks in theDO-178B Checkssubfolder are reformatted for consistency in the results format.

For more information, seeDO-178B Checksin theSimulink Verification and Validationdocumentation.

IEC 61508 Checks

IEC 61508 Checkssubfolder now includesCheck state machine type of Stateflow charts.

For more information, seeIEC 61508 and ISO 26262 Checksin theSimulink Verification and Validationdocumentation.

Modeling Guidelines Documentation Moved into Simulink Documentation

Modeling Guidelines for High-Integrity SystemsandMathWorks Automotive Advisory Board Control Algorithm Modeling Guidelines Using MATLAB, Simulink, and Stateflowdocumentation is now in the Simulink documentation.

For more information, seeModeling Guidelinesin the Simulink documentation.

R2009bSP1

Bug Fixes

R2009b

New Features, Bug Fixes, Compatibility Considerations

New Coverage Reporting for Variable-Size Signals

在R2009b信号大小在仿真软件模型可以查万博1manbetxnge during execution to facilitate modeling systems with varying environments, resources, and constraints. TheSimulink Verification and Validationsoftware 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 theCoveragetab, select theSignal Sizeoption.

模型覆盖Simulink Design VerifierBlocks

Simulink Verification and Validationmodel coverage tool can collect model coverage data forSimulink Design Verifierblocks. Using this feature during simulation, you can verifySimulink Design Verifiergenerated test harnesses and user-defined requirements. The model coverage tool collects model coverage data for the followingSimulink Design Verifierblocks:

To enable this feature, in the Coverage Settings dialog box, on theCoveragetab, selectSimulink Design Verifier.

Force Block Reduction Off During Simulation

Simulink Verification and Validationsoftware can override the value of the SimulinkBlock reductionparameter. 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 theOptionstab, selectForce block reduction off.

Compatibility Considerations

Previously, model coverage ignored the value of the SimulinkBlock reductionparameter, creating incompatibilities between the model coverage data and the generated code coverage data. In R2009b, you can selectForce block reduction offto override theBlock reductionparameter and collect coverage for all blocks in the model.

Improved RMI Highlighting and Reporting

的要求的事情uirements 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 aSimulink Report Generatorlicense

  • 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

的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, seeOrganizing Checks and Folders Using the Model Advisor Configuration EditorandHow to Deploy Custom Configurations.

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 checkout. In R2009b, the Model Advisor performs a checkout of theSimulink Verification and Validationlicense when you runSimulink Verification and Validationchecks. For a list ofSimulink Verification and Validationchecks, seeModel Advisor Checksin theSimulink Verification and Validationdocumentation.

Compatibility Considerations

的Model Advisor performs a checkout of aSimulink Verification and Validationlicense when you run:

  • Checks in theSimulink Verification and Validationfolder

  • Custom checks

如果you do not have aSimulink Verification and Validationlicense available, when you run the check, you see an error message that the required license is not available.

New and Enhanced Model Advisor Checks

的Simulink Model Advisor includes new and updated verification and validation checks.

DO-178B Checks

DO-178B Checksubfolder now includesCheck safety-related diagnostic settings for model initialization.

的checks in theDO-178B Checkssubfolder are reformatted for a consistent look and feel to the results.

For more information, seeDO-178B Checks.

IEC 61508 Checks

IEC 61508 Checkssubfolder now includesCheck for model objects that do not link to requirements.

For more information, seeIEC 61508 and ISO 26262 Checks.

Modeling Guidelines for High-Integrity Systems

MathWorks计划工程师开发的这个文档loping 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.

的se guidelines do not assume that you use a particular safety or certification standard. The guidelines reference some safety standards where applicable, includingDO-178B,IEC 61508, andMISRA 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 theSimulink Verification and Validationdocumentation.

R2009a

New Features, Bug Fixes

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, selectCoverage 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, seeCustomizing the Model Advisor.

New and Enhanced Model Advisor Checks

的Simulink Model Advisor includes new and updated verification and validation checks.

DO-178B Checks

DO-178B Checksubcategory includes the following new checks:

  • Check for blocks that do not link to requirements

  • Check usage of Math blocks

For more information, seeDO-178B Checks.

IEC 61508 Checks

的checks in theIEC 61508 Checkssubfolder are reformatted for a consistent look and feel to the results. For more information, seeIEC 61508 and ISO 26262 Checks.

Modeling Standards for MAAB Checks

的re is a newModeling Standards for MAABsubfolder in theBy Taskfolder 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

的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 theSimulink Verification and Validationproduct 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."

R2008b

New Features, Bug Fixes

New and Enhanced Model Advisor Checks

Context-sensitive help is now available for all Model Advisor checks.

DO-178B Checks

DO-178B Checksubcategory 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 parameterSignalRangeCheckingis set toerror.

  • 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, seeDO-178B Checksin theSimulink Verification and Validationdocumentation.

IEC 61508 Checks

IEC 61508 Checks子类别包含了一个新的检查,检查使用tateflow, 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, seeIEC 61508 and ISO 26262 Checksin theSimulink Verification and Validationdocumentation.

MathWorks Automotive Advisory Board Checks

MathWorks Automotive Advisory Board Checkssubcategory includes new checks that have been implemented to support theMathWorks 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, seeMathWorks Automotive Advisory Board Checksin theSimulink Verification and Validationdocumentation.

Improved Selection-Based Linking

To create links between a model and a Microsoft Word orMicrosoft Excelfile, 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, seeLinks Between Models and Requirementsin theSimulink Verification and Validationdocumentation.

Enhanced Model Coverage Report

的Model Coverage report now includes information about:

  • Model being analyzed

  • Simulation optimization options

  • Model coverage options

For more information, seeCreating Requirements Reportsin theSimulink Verification and Validationdocumentation.

R2008a+

Bug Fixes

R2008a

New Features, Bug Fixes

Enhanced Coverage Support for Referenced Models

的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要求的事情uirementssubmenu replaces theEdit requirementsitem 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

的Simulink Model Advisor has been enhanced with new and updated verification and validation checks.

  • In the Task Hierarchy tree, the check categoryBy Product>Simulink Verification and Validation>Modeling Standardsincludes the new subcategoryIEC 61508 Checks.

  • IEC 61508 Checkssubcategory 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, seeModel Advisor Checksin theSimulink Verification and Validationdocumentation.

  • 的IEC 61508 checks also appear under the new categoryBy Task>Model-Based Design for IEC 61508.

  • SomeMathWorks Automotive Advisory Board Checkshave been updated.

For Information on How To... See...
Develop models and code that comply with industry standards and guidelines, such as the IEC 61508 standard and MathWorks Automotive Advisory Board (MAAB) guidelines

Guidelines and Standardsin the Real-Time Workshop®Embedded Coder documentation

Use the Model Advisor Consulting the Model AdvisorinSimulink User's Guide
Customize the Model Advisor with your own tasks and checks Customizing the Model Advisorin theSimulink 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, seeCustomizing the Model Advisorin theSimulink Verification and Validation User's Guide.

R2007b+

Bug Fixes

R2007b

New Features, Bug Fixes

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 forModelblocks whoseSimulation modeparameter specifiesNormal. Toward that end, this release provides three new functions:

Model Advisor Checks for Modeling Standards Enhanced

的Simulink Model Advisor has been enhanced with new and updated verification and validation checks.

  • In the Task Hierarchy tree, the check categoryBy Product>Simulink Verification and Validation>Modeling Standardsincludes two new subcategories:DO-178B ChecksandMathWorks Automotive Advisory Board Checks.

  • DO-178B Checkssubcategory 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, seeModel Advisor Checks.

  • 的DO-178B checks also appear under the new categoryBy Task>Safety Critical for DO-178B.

  • Checks listed underBy Product>Simulink Verification and Validation>Modeling Standardsin earlier releases, appear under the new subcategoryMathWorks Automotive Advisory Board Checks. These checks verify that Simulink block diagrams adhere to style guidelines published by theMathWorks Automotive Advisory Board (MAAB).

  • SomeMathWorks Automotive Advisory Board Checkshave been updated. For example, the check for "hd_0001, Prohibited Simulink Sink and Data Store blocks" 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 AdvisorinSimulink User's Guide
Customize the Model Advisor with your own tasks and checks Customizing the Model Advisorin theSimulink 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. SeeFormatting Model Advisor Resultsin theSimulink Verification and Validation User's Guide.

R2007a+

Bug Fixes

R2007a

Bug Fixes

R2006b

New Features, Bug Fixes

要求的事情uirement 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:

  • 的requirements document is missing.

  • 的location (e.g., bookmark, line number, anchor) specified within the requirements document is invalid.

  • 的description of a selection-based link does not match its requirements document text.

  • 的requirements document path does not match your preferred path type (i.e., absolute or relative).

SeeConsulting the Model AdvisorinSimulink User's Guidefor 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). SeeConsulting the Model AdvisorinSimulink User's Guidefor more information about using Model Advisor. For information about the MAAB modeling style guidelines, see//www.tianjin-qmedu.com/industries/auto/maab.html.

R2006a

No New Features or Changes

Compatibility Summary

Release Features or Changes with Compatibility Considerations
R2016a None
R2015aSP1 None
R2015b Model Advisor check exclusions saved to model SLX file
R2015a None
R2014b None
R2014a None
R2013b ModelAdvisor.runoption for parallel processing
R2013a None
R2012b
R2012a URL-Based Navigation From External Requirements Documents to Simulink Objects
R2011b
R2011a None
R2010bSP1 None
R2010b MathWorks Check IDs for the Model Advisor Updated
R2010a Function rminav Removed
R2009bSP1 None
R2009b
R2009a None
R2008b None
R2008a+ None
R2008a None
R2007b+ None
R2007b None
R2007a+ None
R2007a None
R2006b None
R2006a None
Was this topic helpful?