IEC Certification Kit

Simulink® Verification and Validation™

Conformance Demonstration Template

R2014a
How to Contact MathWorks
www.mathworks.com Web
comp.soft-sys.matlab Newsgroup
www.mathworks.com/contact_TS.html Technical Support
suggest@mathworks.com Product enhancement suggestions
bugs@mathworks.com Bug reports
doc@mathworks.com Documentation error reports
service@mathworks.com Order status, license renewals, passcodes
info@mathworks.com Sales, pricing, and general information

508-647-7000 (Phone)
508-647-7001 (Fax)
The MathWorks, Inc.
3 Apple Hill Drive
Natick, MA 01760-2098
For contact information about worldwide offices, see the MathWorks Web site.

IEC Certification Kit: Simulink® Verification and Validation™ Conformance Demonstration Template
© COPYRIGHT 2011–2014 by The MathWorks, Inc.
The software described in this document is furnished under a license agreement. The software may be used or copied only under
the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written
consent from The MathWorks, Inc.
FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the
federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees
that this software or documentation qualifies as commercial computer software or commercial computer software documentation
as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and
conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification,
reproduction, release, performance, display, and disclosure of the Program and Documentation by the federal government (or
other entity acquiring for or through the federal government)and shall supersede any conflicting contractual terms or conditions.
If this License fails to meet the government’s needs or is inconsistent in any respect with federal procurement law, the
government agrees to return the Program and Documentation, unused, to The MathWorks, Inc.
Trademarks
MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See www.mathworks.com/trademarks for a list of
additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective holders.
Patents
MathWorks products are protected by one or more U.S. patents. Please see www.mathworks.com/patents for more information.
Revision History
September 2011 New for Version 2.0 (Applies to Release R2011b)
March 2012 Revised for Version 2.1 (Applies to Release R2012a)
September 2012 Revised for Version 3.0 (Applies to Release R2012b)
March 2013 Revised for Version 3.1 (Applies to Release R2013a)
September 2013 Revised for Version 3.2 (Applies to Release R2013b)
March 2014 Revised for Version 3.3 (Applies to Release R2014a)
Contents
1 Introduction.......................................................................................................................................1-1
1.1 Conformance Demonstration Template Overview...................................................................1-2
1.2 Application Identification.........................................................................................................1-3
2 Model Compliance Checking and Automated Fixing of Reported Issues........................................2-1
3 Model Coverage Analysis.................................................................................................................3-1
4 Additional Considerations.................................................................................................................4-1

v
vi
1 Introduction
1.1 Conformance Demonstration Template Overview
This Conformance Demonstration Template can be used to demonstrate conformance with the
parts of ISO 26262-6/8, IEC 61508-3, or EN 50128 covered in the document

Simulink® Verification and Validation™ Reference Workflow

To access the reference workflow document, on the MATLAB® command line, type
certkitiec to open the Artifacts Explorer. The reference workflow document is in the
following folder:

matlabroot/toolbox/qualkits/iec/slvnv/r2014a

For each technique or measure:

 In the third column, state to what degree you applied the technique or measure for the
application under consideration by using one of the phrases: Used, Used to a limited
degree, or Not used.

 In the fourth column, state how you used the technique or measure in the application under
consideration. If the reference workflow includes alternative means for compliance,
indicate what variant you used. In addition, enter a reference to the document (for example,
test report or review documentation).
1.2 Application Identification
Applicant: <Insert information>
Application: <Insert information>

3
4
2 Model Compliance Checking and
Automated Fixing of Reported
Issues
 Checklist 1: Model Compliance Checking
Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
1 Adherence to modeling  Designation of modeling
guidelines guidelines
 Review of modeling guidelines
as suitable for use
 Evidence for using the
modeling guidelines
2 Model compliance  Designation of model
checking (Static analysis compliance checks in Model
at the model level) Advisor

(See “Tool Use Cases” in  Static analysis of model to

the Simulink® verify compliance with
Verification and specified modeling guidelines
Validation™ Reference using Model Advisor
Workflow)  Generation of Model Advisor
report to document results of
model compliance checking
 Review of Model Advisor
report for detected guideline
violations and errors
 Corrective action on guideline
violations and errors
3 Preceding or  Execution of specified test
subsequent dynamic cases against model
verification (testing)
of the model  Documentation of the results of
model tests
(See “Error Prevention
 Corrective action on failure of
and Detection Measures”
model tests
in the Simulink
Verification and
Validation Reference
Workflow)
 Checklist 2: Automated Fixing of Reported Issues
Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
4 Fixing of issues reported  Automatic fixing of reported
during compliance issues using capabilities
checking provided by model compliance
checks
(See “Tool Use Cases”
in the Simulink®
Verification and
Validation™ Reference
Workflow)
5a Subsequent model  Designation of model
compliance checking compliance checks in Model
(Static analysis at the Advisor
model level)
 Static analysis of model to
(See “Error Prevention verify compliance with
and Detection Measures” specified modeling guidelines
in the Simulink using Model Advisor
Verification and  Generation of Model Advisor
Validation Reference report to document results of
Workflow) model compliance checking
 Review of Model Advisor
report for detected guideline
violations and errors
 Corrective action on guideline
violations and errors

3
 Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
5b Subsequent dynamic  Designation of model
verification (testing) of compliance checks in Model
the model Advisor

(See “Error Prevention  Static analysis of model to

and Detection Measures” verify compliance with
in the Simulink specified modeling guidelines
Verification and using Model Advisor
Validation Reference  Generation of Model Advisor
Workflow) report to document results of
model compliance checking
 Review of Model Advisor
report for detected guideline
violations and errors
 Corrective action on guideline
violations and errors
5c Subsequent comparison  Comparison of XML files
of the XML files generated from model before
exported from the and after automated fixing of
original and fixed reported issues
Simulink® models
 Generation of XML
(See “Error Prevention comparison report
and Detection Measures”  Review of XML comparison
in the Simulink report for unintended
Verification and modifications
Validation Reference
Workflow)

4
3 Model Coverage Analysis
 Checklist 3: Model Coverage Analysis
Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
6 Model coverage  Model coverage analysis of
analysis model test cases

(See “Tool Use Cases”  Review of the model coverage

in the Simulink® reported for uncovered model
Verification and elements and their impact
Validation™ Reference  Justification of and corrective
Workflow) action on uncovered elements
7 Subsequent code  Code coverage analysis of code
coverage analysis level test cases

(See “Error Prevention  Review of the code coverage

and Detection report for uncovered code
Measures” in the elements and their impact
Simulink Verification  Justification of and corrective
and Validation action on uncovered elements
Reference Workflow)
4 Additional Considerations
 Checklist 4: Additional Considerations
Technique / Measure
8 Configuration management
and revision control
(See “Configuration
Management and Revision
Control” in the Simulink®
Verification and
Validation™ Reference
Workflow)
9 Competency of the project
team
(See “Competency of the
Project Team” in the
Simulink Verification and
Validation Reference
Workflow)
10 Installation integrity and
release compatibility
(See “Installation
Integrity and Release
Compatibility” in the
Simulink Verification and
Validation Reference
Workflow)
11 Bug Reporting
(See “Bug Reporting” in the
Simulink Verification and
Validation Reference
Workflow)
Associated Requirements Used / Used Interpretation in
to a limited this application,
degree / Not Evidence
used
 Revision control for model
used for compliance checking
and coverage analysis
 Configuration management for
control of model used for
compliance checking and
coverage analysis (if
applicable)
 Evidence for competence of
project team members
 Validation of modification and
additions to shipping tools (if
applicable)
 Compatibility of product
versions for model creation,
model compliance checking,
and model coverage analysis
 Assessment of bug report
information provided by tool
vendors and compliance with
recommendations and
workarounds (during
development and after
deployment)
 Reporting of issues with
MathWorks® products
 Technique / Measure
12 Deviation from the
reference workflow
(See “Deviation from
Reference Workflow” in the
Simulink Verification and
Validation Reference
Workflow)
13 Integration with the
software safety lifecycle
(See “Integration with
Software Safety Lifecycle”
in the Simulink Verification
and Validation Reference
Workflow)
Associated Requirements Used / Used Interpretation in
to a limited this application,
degree / Not Evidence
used
 Documentation and
justification for deviations
from the reference workflow
by using a deviation procedure
(if applicable)
 Documented software safety
lifecycle, including activities
for verification and validation
as part of a model-based
design process