User`s guide

22 Checking Systems Interactively
22-2
Check Model and Subsystems
You can use the Model Advisor to check a model or subsystem for adherence to modeling
guidelines or standards. The Model Advisor includes checks that help you define and
implement consistent design guidelines. Using model checks, you can apply guidelines
across projects and development teams.
When you run the checks, the Model Advisor reviews your model for conditions and
configuration settings that cause inaccurate or inefficient simulation and code generation
of the system that the model represents. Depending on which products you have
installed, the Model Advisor includes different checks.
For more information See
Checking model compliance with the
DO-178C safety standard
“Model Checks for DO-178C/DO-331
Standard Compliance” on page 22-16
Checking model compliance with theISO
®
26262, IEC 61508, or EN 50182 safety
standards
“Model Checks for IEC 61508, ISO 26262,
and EN 50128 Standard Compliance” on
page 22-20
Checking model compliance with
MathWorks Automotive Advisory Board
(MAAB) guidelines
“Model Checks for MathWorks Automotive
Advisory Board (MAAB) Guideline
Compliance” on page 22-23
Checking requirements links “Model Checks for Requirements Links” on
page 22-28
Model Advisor “Consulting the Model Advisor”
Software is inherently complex and may not be completely free of errors. Model Advisor
checks might contain bugs. MathWorks reports known bugs brought to its attention
on its Bug Report system at http://www.mathworks.com/support/bugreports/. The
bug reports are an integral part of the documentation for each release. Examine
periodically all bug reports for a release as such reports may identify inconsistencies
between the actual behavior of a release you are using and the behavior described in this
documentation.
While applying Model Advisor checks to your model will increase the likelihood that
your model does not violate certain modeling standards or guidelines, it is ultimately
your responsibility to verify, using multiple methods, that the system being developed
provides its intended functionality and does not include any unintended functionality.