Sei sulla pagina 1di 41

DO Qualification Kit

Simulink Verification and Validation


Tool Operational Requirements
R2015b, September 2015

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
DO Qualification Kit: Simulink Verification and Validation Tool Operational Requirements

COPYRIGHT 20092015 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 governments 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.

Revision History
March 2009
September 2009
April 2010
March 2010
September 2010
April 2011
September 2011
March 2012
September 2012
March 2013
September 2013
March 2014
October 2014
March 2015
September 2015

New for Version 1.0 (Applies to Release 2009a)


Revised for Version 1.1 (Applies to Release 2009b)
Rereleased for Version 1.1.1 (Applies to Release 2009bSP1)
Revised for Version 1.2 (Applies to Release 2010a)
Revised for Version 1.3 (Applies to Release 2010b)
Revised for Version 1.4 (Applies to Release 2011a)
Revised for Version 1.5 (Applies to Release 2011b)
Revised for Version 1.6 (Applies to Release 2012a)
Revised for Version 2.0 (Applies to Release 2012b)
Revised for Version 2.1 (Applies to Release 2013a)
Revised for Version 2.2 (Applies to Release 2013b)
Revised for Version 2.3 (Applies to Release 2014a)
Revised for Version 2.4 (Applies to Release 2014b)
Revised for Version 2.5 (Applies to Release 2015a)
Revised for DO Qualification Kit Version 3.0 (Applies to Release 2015b)

Contents
1 Introduction ...................................................................................................................................... 1-1
1.1 Simulink Verification and Validation Product Description ..................................................... 1-2
2 Operational Requirements ................................................................................................................ 2-1
2.1 DO-178C/DO-331 Checks Operational Requirements ........................................................... 2-2
2.2 DO-178C/DO-331 Checks and Model Advisor User Information ........................................ 2-19
2.3 Model Coverage Operational Requirements ......................................................................... 2-20
2.4 Model Coverage User Information ........................................................................................ 2-30
3 Installation ........................................................................................................................................ 3-1
4 Operational Environment ................................................................................................................. 4-1

vi

1 Introduction
This document comprises the Tool Operational Requirements (reference DO-330 Section
10.3.1) for the following capabilities of the Simulink Verification and Validation verification
product:

DO-178C/DO-331 checks
Model coverage

The document identifies:

Features of the Simulink Verification and Validation product.


The environment in which the Simulink Verification and Validation product is installed
(reference DO-330, Sections 10.2.4 and 10.3.2).

This document is intended for use in the DO-330 tool qualification process for TQL-5 tools. The
applicant needs to:

Review the Tool Operational Requirements for applicability in the project or program
under consideration.
Configure the Tool Operational Requirements in the project or programs configuration
management system.
Complete the Tool Operational Requirements and make the document available for review.

See documentation for the following products at the MathWorks Documentation Center,
R2015b:

DO Qualification Kit (for DO-178)


Simulink Verification and Validation
Simulink
Stateflow

1.1 Simulink Verification and Validation Product


Description
Verify models and generated code

Simulink Verification and Validation automates requirements tracing, modeling standards


compliance checking, and model coverage analysis.
You can create detailed requirements traceability reports, author your own modeling style
checks, and develop check configurations to share with engineering teams. Requirements
documentation can be linked to models, test cases, and generated code. You can generate
harness models for testing model components and code, and use model coverage analysis to
ensure that models have been thoroughly tested.
Simulink Verification and Validation provides modeling standards checks for the DO-178, ISO
26262, IEC 61508 and related industry standards.
Key Features

Compliance checking for MAAB style guidelines and high-integrity system design
guidelines (DO-178, ISO 26262, IEC-61508, and related industry standards)
Model Advisor Configuration Editor, including custom check authoring
Requirements Management Interface for traceability of model objects, code, and tests to
requirements documents
Automatic test-harness generation for subsystems
Component testing via simulation, software-in-the-loop (SIL), and processor-in-the-loop
(PIL)
Programmable scripting interface for automating compliance checking, requirements
traceability analysis, and component testing

1-2

2 Operational Requirements

2.1 DO-178C/DO-331 Checks Operational


Requirements
The Simulink Verification and Validation product includes the Model Advisor
DO-178C/DO-331 modeling standards checks, which help you define and implement consistent
design guidelines. These guidelines can be applied across projects and development teams. The
Model Advisor finds unwanted model properties, such as incorrect or deprecated blocks and
block parameters, incorrect fonts, and misplaced objects.
Types of checks include:

Block parameter settings


Model configuration parameter settings
Code generator settings
Production hardware parameter settings
Simulink and Stateflow diagnostic parameter settings
Model connections
Compatibility of reference models, libraries and S-functions
Model style considerations
Requirement management interface consistency

The purpose of this capability is to verify that Simulink and Stateflow models comply with
modeling standards, and to verify that the code generator settings are set properly to provide
traceable code that complies with standards.
You can find the DO-178C/DO-331 checks in the Model Advisor > By Product > Simulink
Verification and Validation > Modeling Standards > DO-178C/DO-331 Checks subfolder.

2-2

The following table lists the Simulink Verification and Validation DO-178C/DO-331 checks
that are provided with the DO Qualification Kit, along with the corresponding DO-331 section
to which each check applies. The user is responsible for ensuring that the tool features they rely
on to eliminate, reduce or automate the process are sufficiently covered by Tool Operational
Requirements (reference DO-300 Section 6.2.1.aa).

Note The DO-178C/DO-331 checks can contain two sections: an analysis section
for reviewing the model and an action section for automatically fixing warnings
and failures. The DO Qualification Kit covers the DO-178C/DO-331 check
analysis, not the check actions.
The DO Qualification Kit does not cover Model Advisor check exclusions.

DO-178C/DO-331 Checks Operational Requirements Summary


Check Title
Check ID

Requirement Description
ID

Check safety-related optimization DO178C_01


settings
mathworks.do178.OptionSet

DO-331 References

Simulink Verification and


Validation shall verify that the
model optimization
configuration parameters
comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards
MB.6.3.1.g Algorithms are
accurate
For details, refer to Check
MB.6.3.2.g Algorithms are
safety-related optimization
accurate
settings in Simulink
MB.6.3.3.b Software
Verification and Validation DO- architecture is consistent
178C/DO-331 Checks and
MB.6.3.4.e Source code is
Model Advisor User
traceable to low-level
Information.
requirements

2-3

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for solvers

DO178C_02

mathworks.do178.SolverDiagnost
icsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to solvers
comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

DO-331 References
MB.6.3.3.b Software
architecture is consistent
MB.6.3.3.e Software
architecture conforms to
standards

For details, refer to Check


safety-related diagnostic settings
for solvers in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check safety-related diagnostic
settings for sample time
mathworks.do178.SampleTimeDi
agnosticsSet

DO178C_03

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to sample
time comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

MB.6.3.3.b Software
architecture is consistent
MB.6.3.3.e Software
architecture conforms to
standards

For details, see Check safetyrelated diagnostic settings for


sample time in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-4

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for signal data

DO178C_04

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to signal
data comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

DO178C_05

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to
parameters comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

mathworks.do178.DataValiditySi
gnalsDiagnosticsSet

Check safety-related diagnostic


settings for parameters
mathworks.do178.DataValidityPar
amDiagnosticsSet

DO-331 References

MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards
MB.6.3.1.g Algorithms are
accurate
For details, see Check safety- MB.6.3.2.g Algorithms are
related diagnostic settings for
accurate
signal data in Simulink
MB.6.3.3.b Software
Verification and Validation DO- architecture is consistent
178C/DO-331 Checks and
Model Advisor User
Information.
MB.6.3.1.g Algorithms are
accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check safetyrelated diagnostic settings for


parameters in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-5

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for data used for
debugging

DO178C_06

mathworks.do178.DataValidityD
ebugDiagnosticsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to
debugging comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

DO-331 References
MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards

For details, see Check safetyrelated diagnostic settings for


data used for debugging in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.
Check safety-related diagnostic
settings for data store memory
mathworks.do178.DataStoreMem
oryDiagnosticsSet

DO178C_07

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to data
store memory comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

MB.6.3.3.b Software
architecture is consistent

For details, see Check safetyrelated diagnostic settings for


data store memory in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-6

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for type conversions

DO178C_08

mathworks.do178.TypeConversio
nDiagnosticsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to type
conversions comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

DO-331 References
MB.6.3.1.g Algorithms are
accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check safetyrelated diagnostic settings for


type conversions in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check safety-related diagnostic
settings for signal connectivity
mathworks.do178.ConnectivitySi
gnalsDiagnosticsSet

DO178C_09

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to type
conversions comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards

For details, see Check safetyrelated diagnostic settings for


signal connectivity in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-7

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for bus connectivity

DO178C_10

mathworks.do178.ConnectivityB
ussesDiagnosticsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to bus
connectivity comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

DO-331 References
MB.6.3.3.b Software
architecture is consistent

For details, see Check safetyrelated diagnostic settings for


bus connectivity in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check safety-related diagnostic DO178C_11
settings that apply to function-call
connectivity
mathworks.do178.FcnCallDiagno
sticsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to
function-call connectivity
comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

MB.6.3.3.b Software
architecture is consistent

For details, see Check safetyrelated diagnostic settings that


apply to function-call
connectivity in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-8

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for compatibility

DO178C_12

mathworks.do178.Compatability
DiagnosticsSet

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to
compatibility comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

DO-331 References
MB.6.3.3.b Software
architecture is consistent

For details, see Check safetyrelated diagnostic settings for


compatibility in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check safety-related diagnostic
settings for model referencing
mathworks.do178.MdlRefDiagno
sticsSet

DO178C_13

Simulink Verification and


Validation shall verify that the
model diagnostic configuration
parameters pertaining to model
referencing comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

MB.6.3.1.d High-level
requirements are verifiable
MB.6.3.2.d Low-level
requirements are verifiable
MB.6.3.3.b Software
architecture is consistent

For details, see Check safetyrelated diagnostic settings for


model referencing in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-9

Check Title
Check ID

Requirement Description
ID

Check safety-related model


referencing settings

DO178C_14

mathworks.do178.MdlRefOptSet

Simulink Verification and


Validation shall verify that the
model configuration parameters
for model referencing are set to
generate code for a safetyrelated application.
For details, see Check safetyrelated model referencing
settings in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

Check safety-related code


generation settings

DO178C_15

Simulink Verification and


Validation shall verify that the
model configuration parameters
for code generation comply with
the Modeling Guidelines for
High-Integrity Systems, R2015b.

DO178C_16

Simulink Verification and


Validation shall verify that the
report displays model version
information.

mathworks.do178.CodeSet

Display model version


information
mathworks.do178.MdlChecksum

DO-331 References
MB.6.3.1.b High-level
requirements are accurate and
consistent
MB.6.3.2.b Low-level
requirements are accurate and
consistent
MB.6.3.3.b Software
architecture is consistent

MB.6.3.1.c High-level
requirements are compatible
with target computer
MB.6.3.2.c Low-level
requirements are compatible
with target computer
MB.6.3.1.e High-level
For details, see Check safety- requirements conform to
related code generation settings standards
in Simulink Verification and
MB.6.3.2.e Low-level
Validation DO-178C/DO-331
requirements conform to
Checks and Model Advisor User standards
Information.
MB.6.3.4.e Source code is
traceable to low-level
requirements
Not Applicable (for
documentation only)

For details, see Display model


version information in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-10

Check Title
Check ID

Requirement Description
ID

Check safety-related diagnostic


settings for saving

DO178C_17

mathworks.do178.SavingDiagnos
ticsSet

DO-331 References

Simulink Verification and


MB.6.3.3.b Software
Validation shall verify that the architecture is consistent
model configuration parameters
on the Diagnostics > Saving
pane are set for a safety-related
application.
For details, see Check safetyrelated diagnostic settings for
saving in Simulink Verification
and Validation DO-178C/DO331 Checks and Model Advisor
User Information.

Check for blocks that do not link DO178C_18


to requirements
mathworks.do178.RequirementIn
fo

Simulink Verification and


Validation shall verify that the
model blocks and objects link to
requirements document.
For details, see Check for
blocks that do not link to
requirements in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

Check safety-related diagnostic


settings for model initialization
mathworks.do178.InitDiagnostics
Set

DO178C_19

MB.6.3.1.f High-level
requirements trace to system
requirements
MB.6.3.2.f Low-level
requirements trace to highlevel requirements

Simulink Verification and


MB.6.3.3.b Software
Validation shall verify that the architecture is consistent
model diagnostic configuration
parameters pertaining to
initialization are set according to
the Modeling Guidelines for
High-Integrity Systems, R2015b.
For details, see Check safetyrelated diagnostic settings for
model initialization in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-11

Check Title
Check ID

Requirement Description
ID

Check state machine type of


Stateflow charts

DO178C_20

Simulink Verification and


Validation shall verify that state
machine types comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

Check Stateflow charts for


DO178C_21
ordering of states and transitions

Simulink Verification and


Validation shall verify that chart
state/transition execution order
complies with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

mathworks.do178.hisf_0001

mathworks.do178.hisf_0002

DO-331 References

MB.6.3.1.b High-level
requirements are accurate and
consistent
MB.6.3.1.e High-level
requirements conform to
standards
For details, see Check state
MB.6.3.2.b Low-level
machine type of Stateflow
requirements are accurate and
charts in Simulink Verification consistent
and Validation DO-178C/DO- MB.6.3.2.e Low-level
331 Checks and Model Advisor requirements conform to
User Information.
standards
MB.6.3.3.b Software
architecture is consistent
MB.6.3.3.e Software
architecture conforms to
standards
MB.6.3.3.b Software
architecture is consistent
MB.6.3.3.e Software
architecture conforms to
standards

For details, see Check


Stateflow charts for ordering of
states and transitions in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.

2-12

Check Title
Check ID

Requirement Description
ID

Check Stateflow debugging


options

DO178C_22

Simulink Verification and


Validation shall verify that the
Stateflow debugging options
comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

DO178C_23

Simulink Verification and


Validation shall verify that
lookup table blocks are
configured to generate out-ofrange checking code.

mathworks.do178.hisf_0011

Check usage of lookup table


blocks
mathworks.do178.LUTRangeChe
ckCode

DO-331 References

MB.6.3.1.b High-level
requirements are accurate and
consistent
MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.b Low-level
For details, see Check
requirements are accurate and
Stateflow debugging options in consistent
Simulink Verification and
MB.6.3.2.e Low-level
Validation DO-178C/DO-331
requirements conform to
Checks and Model Advisor User standards
Information.
MB.6.3.1.g Algorithms are
accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check usage of


lookup table blocks in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check Stateflow charts for
uniquely defined data objects
mathworks.do178.hisl_0061

DO178C_24

Simulink Verification and


Validation shall verify that
Stateflow charts using data
objects comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

MB.6.3.2.b Accuracy and


Consistency of Low-Level
Requirement

For details, see Check


Stateflow charts for uniquely
defined data objects in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.

2-13

Check Title
Check ID

Requirement Description
ID

Check usage of Math Operations DO178C_25


blocks
mathworks.do178.MathOperation
sBlocksUsage

Simulink Verification and


Validation shall verify that math
operations blocks comply with
the Modeling Guidelines for
High-Integrity Systems, R2015b.

DO-331 References
MB.6.3.1.g Algorithms are
accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check usage of


Math Operations blocks in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.
Check usage of Signal Routing
blocks

DO178C_26

mathworks.do178.SignalRouting
BlockUsage

Simulink Verification and


Validation shall verify that
Signal Routing blocks comply
with the Modeling Guidelines
for High-Integrity Systems,
R2015b.

MB.6.3.1.g Algorithms are


accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check usage of


Signal Routing blocks in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.
Check usage of Logic and Bit
Operations blocks
mathworks.do178.LogicBlockUs
age

DO178C_27

Simulink Verification and


Validation shall verify that
Logic and Bit Operations blocks
comply with the Modeling
Guidelines for High-Integrity
Systems, R2015b.

MB.6.3.1.g Algorithms are


accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check usage of


Logic and Bit Operations
blocks in Simulink Verification
and Validation DO-178C/DO331 Checks and Model Advisor
User Information.

2-14

Check Title
Check ID

Requirement Description
ID

Check usage of Ports and


Subsystems blocks

DO178C_28

mathworks.do178.PortsSubsyste
msUsage

Simulink Verification and


Validation shall verify that Ports
and Subsystems blocks comply
with the Modeling Guidelines
for High-Integrity Systems,
R2015b.

DO-331 References
MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards

For details, see Check usage of


Ports and Subsystems blocks in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.
Check for inconsistent vector
indexing methods

DO178C_29

mathworks.do178.hisl_0021

Simulink Verification and


MB.6.3.2.b Accuracy and
Validation shall verify that the Consistency of Low-Level
vector indexing methods comply Requirements
with the Modeling Guidelines
for High-Integrity Systems,
R2015b.
For details, see Check for
inconsistent vector indexing
methods in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

Check for blocks not


recommended for C/C++
production code deployment
mathworks.do178.PCGSupport

DO178C_30

Simulink Verification and


MB.6.3.2.b Accuracy and
Validation shall identify blocks Consistency of Low-Level
not supported by code
Requirements
generation or not recommended
for C/C++ production code
deployment.
For details, see Check for
blocks not recommended for
C/C++ production code
deployment in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-15

Check Title
Check ID

Requirement Description
ID

Check for MATLAB Function


interfaces with inherited
properties

DO178C_31

mathworks.do178.himl_0002

Simulink Verification and


Validation shall verify that
MATLAB Functions comply
with the Modeling Guidelines
for High-Integrity Systems,
R2015b.

DO-331 References
MB.6.3.2.b Accuracy and
Consistency of Low-Level
Requirements

For details, see Check for


MATLAB Function interfaces
with inherited properties in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.
Check for MATLAB Function
metrics
mathworks.do178.himl_0003

DO178C_32

Simulink Verification and


Validation shall verify that
complexity and code metrics for
MATLAB functions comply
with the Modeling Guidelines
for High-Integrity Systems,
R2015b.

MB.6.3.1.e High-level
requirements conform to
standards
MB.6.3.2.e Low-level
requirements conform to
standards

For details, see Check for


MATLAB Function metrics in
Simulink Verification and
Validation DO-178C/DO-331
Checks and Model Advisor User
Information.

2-16

Check Title
Check ID

Requirement Description
ID

Check MATLAB Code Analyzer DO178C_33


messages
mathworks.do178.himl_0004

Simulink Verification and


Validation shall verify that
MATLAB Functions for
%#codegen directive,
MATLAB Code Analyzer
messages, and justification
message IDs comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.

DO-331 References
MB.6.3.1.g Algorithms are
accurate
MB.6.3.2.g Algorithms are
accurate

For details, see Check


MATLAB Code Analyzer
messages in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.
Check MATLAB code for global DO178C_34
variables
mathworks.do178.himl_0005

Simulink Verification and


MB.6.3.3.b Software
Validation shall verify that
architecture is consistent
global variables comply with the
Modeling Guidelines for HighIntegrity Systems, R2015b.
For details, see Check
MATLAB code for global
variables in Simulink
Verification and Validation DO178C/DO-331 Checks and
Model Advisor User
Information.

2-17

Check Title
Check ID

Requirement Description
ID

Check for variant blocks with


Generate preprocessor
conditionals active

DO178C_35

mathworks.do178.VariantBlock

Simulink Verification and


Validation shall verify that
variant blocks are not
configured to generate preprocessor conditionals.

DO-331 References
MB.6.3.4.e Source code is
traceable to low-level
requirements

For details, see Check for


variant blocks with Generate
preprocessor conditionals
active in Simulink Verification
and Validation DO-178C/DO331 Checks and Model Advisor
User Information.

2-18

2.2 DO-178C/DO-331 Checks and Model Advisor User


Information
The Simulink Verification and Validation user information for the DO-178C/DO-331 checks
is in the Simulink Verification and Validation DO-178C/DO-331 Checks and Model Advisor
User Information.
To access the user information document, on the MATLAB command line, type qualkitdo
to open the Artifacts Explorer. The document is in Simulink Verification and Validation.

2-19

2.3 Model Coverage Operational Requirements


The Simulink Verification and Validation product includes model coverage, which helps you
assess the extent to which test cases exercise the pathways through a model. Model coverage
works for Simulink blocks, including the MATLAB Function block, and Stateflow charts.
The following table lists the Simulink Verification and Validation model coverage capabilities
supported by the DO Qualification Kit. Also listed are the corresponding DO-178C or DO-331
(references that include MB prefix) section to which each capability applies. The user is
responsible for ensuring that the tool features they rely on to eliminate, reduce or automate the
process are sufficiently covered by Tool Operational Requirements (reference DO-300 Section
6.2.1.aa).

Model Coverage Operational Requirements Summary


Model Coverage
Capability

Requirement Description
ID

Cumulative Coverage MC_SL_CUMC Simulink Verification and


Validation shall determine the
accumulated coverage results
of model coverage analysis.
For details, see Cumulative
Coverage in Simulink
Verification and Validation
Model Coverage User
Information.

Simulink Cyclomatic MC_SL_CYC


Complexity

Simulink Verification and


Validation shall determine the
cyclomatic complexity of a
model.
For details, see Cyclomatic
Complexity in Simulink
Verification and Validation
Model Coverage User
Information.

DO-178C/DO-331 References
MB.6.3.1.d High-level requirements are
verifiable
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.3.d Software architecture is
verifiable
6.4.5 Test cases and procedures are
correct
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
requirements is achieved
MB.6.3.1.d High-level requirements are
verifiable
MB.6.3.1.e High-level requirements
conform to standards
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.2.e Low-level requirements
conform to standards
MB.6.3.3.d Software architecture is
verifiable
MB.6.3.3.e Software architecture
conforms to standards

2-20

Model Coverage
Capability

Requirement Description
ID

Decision Coverage
(DC)

MC_SL_DC

DO-178C/DO-331 References

Simulink Verification and


MB.6.3.1.d High-level requirements are
Validation shall determine the verifiable
DC of a model.
For details, see Decision
Coverage (DC) in Simulink
Verification and Validation
Model Coverage User
Information.

Condition Coverage
(CC)

MC_SL_CC

Simulink Verification and


Validation shall determine the
CC of a model.
For details, see Condition
Coverage (CC) in Simulink
Verification and Validation
Model Coverage User
Information.

Modified
Condition/Decision
Coverage (MC/DC)

Saturation on integer
overflow coverage

MB.6.3.2.d Low-level requirements are


MC_SL_MCDC Simulink Verification and
Validation shall determine the verifiable
MC/DC of a model.
MB.6.3.3.d Software architecture is
verifiable
For details, see Modified
MB.6.3.2.a Low-level requirements
Condition/Decision Coverage comply with high-level requirements
(MCDC) in Simulink
6.4.5 Test cases and procedures are
Verification and Validation
correct
Model Coverage User
6.4.4.1 Test coverage of high-level
Information.
requirements is achieved
MC_SATINT Simulink Verification and
6.4.4.1 Test coverage of low-level
Validation shall provide
requirements is achieved
saturation on integer overflow
coverage.
For details, see Saturation on
integer overflow coverage in
Simulink Verification and
Validation Model Coverage
User Information.

2-21

Model Coverage
Capability

Requirement Description
ID

DO-178C/DO-331 References

Lookup Table
Coverage (LUT)

MC_SL_LUT

Simulink Verification and


6.4.5 Test cases and procedures are
Validation shall provide LUT correct
coverage.
6.4.4.1 Test coverage of high-level
requirements is achieved
For details, see Lookup
6.4.4.1 Test coverage of low-level
Table Coverage in Simulink requirements is achieved
Verification and Validation
Model Coverage User
Information.

Signal Range
Coverage

MC_SL_SR

Simulink Verification and


Validation shall provide
signal range coverage.
For details, see Signal Range
Coverage in Simulink
Verification and Validation
Model Coverage User
Information.

Signal Size Coverage MC_SL_SS

Simulink Verification and


Validation shall provide
signal size coverage.
For details, see Signal Size
Coverage in Simulink
Verification and Validation
Model Coverage User
Information.

Relational Boundary
Coverage

MC_SL_RELB Simulink Verification and


MB.6.3.2.d Low-level requirements are
OUND
Validation shall provide
verifiable
relational boundary coverage. MB.6.3.3.d Software architecture is
verifiable
For details, see Relational
6.4.5 Test cases and procedures are
Boundary Coverage in
correct
Simulink Verification and
6.4.4.1 Test coverage of high-level
Validation Model Coverage requirements is achieved
User Information.
6.4.4.1 Test coverage of low-level
requirements is achieved

2-22

Model Coverage
Capability

Requirement Description
ID

Abs block

MC_SL_ABS

Combinatorial Logic
block

Dead Zone block

DO-178C/DO-331 References

Simulink Verification and


Validation shall provide DC,
saturate on integer overflow,
and relational boundary
coverage for the Abs block.*

MB.6.3.1.d High-level requirements are


verifiable
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.3.d Software architecture is
verifiable
MB.6.3.2.a Low-level requirements
comply with high-level requirements
MC_SL_COMB Simulink Verification and
LOGIC
Validation shall provide DC 6.4.5 Test cases and procedures are
and CC for the Combinatorial correct
Logic block.*
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
MC_SL_DEAD Simulink Verification and
Validation shall provide DC, requirements is achieved
saturate on integer overflow,
and relational boundary
coverage for the Dead Zone
block.*

Direct Lookup Table


(n-D) block

MC_SL_DLUT Simulink Verification and


ND
Validation shall provide LUT
coverage for the Direct
Lookup Table (n-D) block.*

Discrete-Time
Integrator block

MC_SL_DINT Simulink Verification and


Validation shall provide DC
and saturate on integer
overflow coverage for the
Discrete-Time Integrator
block.*

6.4.5 Test cases and procedures are


correct
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
requirements is achieved

MB.6.3.1.d High-level requirements are


verifiable
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.3.d Software architecture is
verifiable
MB.6.3.2.a Low-level requirements
Enabled and Triggered MC_SL_ENTR Simulink Verification and
comply with high-level requirements
G
Validation shall provide DC, 6.4.5 Test cases and procedures are
Subsystem block
CC, and MCDC for the
correct
Enabled and Triggered
6.4.4.1 Test coverage of high-level
Subsystem block.*
requirements is achieved

2-23

Model Coverage
Capability

Requirement Description
ID

DO-178C/DO-331 References

Enabled Subsystem
block

6.4.4.1 Test coverage of low-level


MC_SL_ENAB Simulink Verification and
Validation shall provide DC, requirements is achieved
CC, and MCDC for the
Enabled Subsystem block.*

Fcn block

MC_SL_FCN

Simulink Verification and


Validation shall provide CC,
MCDC, and relational
boundary coverage for the
Fcn block.*

For Iterator, For


Iterator
Subsystem blocks

MC_SL_FOR

Simulink Verification and


Validation shall provide DC
for the For Iterator, For
Iterator Subsystem blocks.*

If, If Action
Subsystem blocks

MC_SL_IF

Simulink Verification and


Validation shall provide DC,
CC, MCDC, and relational
boundary coverage for the If,
If Action Subsystem blocks.*

Interpolation Using
Prelookup block

MC_SL_PREL Simulink Verification and


UT
Validation shall provide LUT
and saturate on integer
overflow coverage for the
Interpolation Using Prelookup
blocks.*

6.4.5 Test cases and procedures are


correct
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
requirements is achieved

Logical Operator
block

MC_SL_LOGI Simulink Verification and


C
Validation shall provide CC
and MCDC coverage for the
Logical Operator blocks.*

MB.6.3.1.d High-level requirements are


verifiable
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.3.d Software architecture is
verifiable
MB.6.3.2.a Low-level requirements
comply with high-level requirements
6.4.5 Test cases and procedures are
correct
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
requirements is achieved

2-24

Model Coverage
Capability

Requirement Description
ID

DO-178C/DO-331 References

1-D Lookup Table


block

MC_SL_LUT1 Simulink Verification and


D
Validation shall provide
lookup table and saturate on
integer overflow coverage for
the 1-D Lookup Table block.*

2-D Lookup Table


block

MC_SL_LUT2 Simulink Verification and


D
Validation shall provide
lookup table and saturate on
integer overflow coverage for
the 2-D Lookup Table block.*

6.4.5 Test cases and procedures are


correct
6.4.4.1 Test coverage of high-level
requirements is achieved
6.4.4.1 Test coverage of low-level
requirements is achieved

n-D Lookup Table


block

MC_SL_LUTN Simulink Verification and


D
Validation shall provide
lookup table and saturate on
integer overflow coverage for
the n-D Lookup Table block.*

MATLAB Function
block

MC_SL_EML

MinMax block

Model block

Simulink Verification and


Validation shall provide DC,
CC, MCDC, and relational
boundary coverage for the
MATLAB Function block.*

MB.6.3.1.d High-level requirements are


verifiable
MB.6.3.2.d Low-level requirements are
verifiable
MB.6.3.3.d Software architecture is
MC_SL_MINM Simulink Verification and
verifiable
AX
Validation shall provide DC MB.6.3.2.a Low-level requirements
and saturate on integer
comply with high-level requirements
overflow coverage for the
6.4.5 Test cases and procedures are
MinMax block.*
correct
MC_SL_MDLR Simulink Verification and
6.4.4.1 Test coverage of high-level
EF
Validation shall provide DC, requirements is achieved
CC, MCDC, LUT, Simulink 6.4.4.1 Test coverage of low-level
Design Verifier, saturate on requirements is achieved
integer overflow coverage,
and relational boundary
coverage for the Model
block.*

Multiport Switch
block

MC_SL_MPSW Simulink Verification and


ITCH
Validation shall provide DC
and saturate on integer
overflow coverage for the
Multiport Switch block.*

Rate Limiter block

MC_SL_RATLI Simulink Verification and


M
Validation shall provide DC
relational boundary coverage
for the Rate Limiter block.*

2-25

Model Coverage
Capability

Requirement Description
ID

Relational Operator
block

MC_SL_RELO Simulink Verification and


P
Validation shall provide
condition and relational
boundary coverage for the
Relational Operator block.*

Relay block

MC_SL_RELA Simulink Verification and


Y
Validation shall provide DC
and relational boundary
coverage for the Relay
block.*

Saturation block

MC_SL_SATU Simulink Verification and


RATE
Validation shall provide DC
and relational boundary
coverage for the Saturation
block.*

Sqrt, Signed Sqrt,


Reciprocal Sqrt

MC_SL_SQRT Simulink Verification and


Validation shall provide
saturate on integer overflow
coverage for the Sqrt, Signed
Sqrt, Reciprocal Sqrt blocks.*

Switch block

MC_SL_SWIT Simulink Verification and


CH
Validation shall provide DC,
saturate on integer overflow
coverage, and relational
boundary coverage for the
Saturation block.*

Switch Case, Switch


Case Action
Subsystem blocks

MC_SL_CASE Simulink Verification and


Validation shall provide DC
for the Switch Case, Switch
Case Action Subsystem
blocks.*

DO-178C/DO-331 References

Triggered Subsystem MC_SL_TRIG Simulink Verification and


block
GER
Validation shall provide DC,
CC, and MCDC for the
Triggered Subsystem block.*
While Iterator, While MC_SL_WHIL Simulink Verification and
Iterator Subsystem
E
Validation shall provide DC
blocks
for the While Iterator, While
Iterator Subsystem blocks.*

2-26

Model Coverage
Capability

Requirement Description
ID

Stateflow Cyclomatic MC_SF_CYC


Complexity

Simulink Verification and


Validation shall determine the
cyclomatic complexity of
Stateflow objects.**

Chart as triggered
Simulink block

MC_SF_TRIG
GER

Simulink Verification and


Validation shall provide DC
for Charts used as a triggered
Simulink block.**

Chart with Exclusive


OR Substates

MC_SF_CHAR Simulink Verification and


TSUB
Validation shall provide DC
for Charts containing
exclusive OR substates.**

Superstate with
Exclusive OR
Substates

MC_SF_SUPE Simulink Verification and


RSUB
Validation shall provide DC
for Superstates containing
exclusive OR substates.**

State with On
Event_Name Action
Statement

MC_SF_ONEV Simulink Verification and


ENT
Validation shall provide DC
for States with ON
Event_Name Action
Statement.**

DO-178C/DO-331 References

Conditional transition MC_SF_TRAN Simulink Verification and


decision
DEC
Validation shall provide DC
for conditional transitions.**
Condition coverage of MC_SF_TRAN Simulink Verification and
transition decision
COND
Validation shall provide CC
for transition decisions.**
MC/DC coverage of
transition decision

MC_SF_TRAN Simulink Verification and


MCDC
Validation shall provide
MCDC for transition
decisions.**

Relational boundary MC_SF_BOUN Simulink Verification and


coverage for Stateflow DCOV
Validation shall provide
boundary coverage for
Stateflow.**

2-27

Model Coverage
Capability

Requirement Description
ID

DO-178C/DO-331 References

Truth Table conditions MC_SF_TTCO Simulink Verification and


ND
Validation shall provide CC
for Truth Tables.
For details, see Model
Coverage for Stateflow Truth
Tables in Simulink
Verification and Validation
Model Coverage User
Information.
Truth Table decisions MC_SF_TTDE Simulink Verification and
C
Validation shall provide DC
for Truth Tables.
For details, see Model
Coverage for Stateflow Truth
Tables in Simulink
Verification and Validation
Model Coverage User
Information.
Truth Table MC/DC

MC_SF_TTMC Simulink Verification and


DC
Validation shall provide
MCDC for Truth Tables.
For details, see Model
Coverage for Stateflow Truth
Tables in Simulink
Verification and Validation
Model Coverage User
Information.

2-28

Model Coverage
Capability

Requirement Description
ID

DO-178C/DO-331 References

Simulink Design
Verifier Coverage

MC_SLDV_SL Simulink Verification and


DV
Validation shall provide
Simulink Design Verifier
Coverage.

6.4.5 Test cases and procedures are


correct

For details, see Simulink


Design Verifier Coverage in
Simulink Verification and
Validation Model Coverage
User Information.
Proof Assumption
block

MC_SLDV_PR Simulink Verification and


OOFASM
Validation shall provide
Simulink Design Verifier
coverage for the Proof
Assumption block.*

Proof Objective block MC_SLDV_PR Simulink Verification and


OOFOBJ
Validation shall provide
Simulink Design Verifier
coverage for the Proof
Objective block.*
Test Condition block

MC_SLDV_TE Simulink Verification and


STCON
Validation shall provide
Simulink Design Verifier
coverage for the Test
Condition block.

Test Objective block

MC_SLDV_TE Simulink Verification and


STOBJ
Validation shall provide
Simulink Design Verifier
coverage for the Test
Objective block.*

* See Model Objects That Receive Coverage in Simulink Verification and Validation Model Coverage User
Information.
** See Model Coverage for Stateflow Charts in Simulink Verification and Validation Model Coverage User
Information.

2-29

2.4 Model Coverage User Information


The Simulink Verification and Validation user information for the model coverage is in the
Simulink Verification and Validation Model Coverage User Information.
To access the user information document, on the MATLAB command line, type qualkitdo
to open the Artifacts Explorer. The document is in Simulink Verification and Validation.

2-30

3 Installation
To use the Simulink Verification and Validation product, install the following MathWorks
products:

MATLAB
Simulink
Simulink Verification and Validation

Instructions for installing the products are available at the MathWorks Documentation Center,
R2015b:
Installation

3-2

4 Operational Environment
The DO Qualification Kit product supports the following operating environments for the
Simulink Verification and Validation product:

Personal computer
One of the following operating systems:
- Microsoft Windows
- Linux1
MATLAB Software
Simulink Software
Simulink Verification and Validation software

Linux is a registered trademark of Linus Torvalds.

Potrebbero piacerti anche