IEC Certification Kit

Embedded Coder™
Conformance Demonstration Template

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

v
vi
1 Introduction
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

Embedded Coder™ 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 Embedded
Coder > r2015a.
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>

1-3
1-4
2 Design Verification
 Checklist 1: Design Verification

Technique / Measure Associated Requirements Used / Used to Interpretation in

a limited degree this application,
/ Not used Evidence
1 Model review  Inclusion of all model
components
(See “Reviews and Static
Analyses at the Model
Level” in the Embedded
Coder™ Reference
Workflow)
2 Adherence to modeling  Designation of a modeling
standard standard

(See “Reviews and Static  Review the modeling standard

Analyses at the Model as suitable for use
Level” in the Embedded  Restriction to modeling
Coder Reference constructs suited for production
Workflow) code generation
 Evidence for using the
modeling standard
3 Static analysis at the  Evidence for using static
model level (if analyzers
applicable)

(See “Reviews and Static

Analyses at the Model
Level” in the Embedded
Coder Reference
Workflow)
4 Supporting activities  Documentation of the results of
reviews and analyses
(See “Reviews and Static
Analyses at the Model  Corrective action on failure of
Level” in the Embedded reviews and analyses
Coder Reference
Workflow)

2-2
 Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
5 Module and integration  Inclusion of all model
testing at the model level components

(See “Module and  Consideration of intended and

Integration Testing at the possible unintended functions
Model Level” in the  Systematic design of test
Embedded Coder vectors
Reference Workflow)
 Inclusion of test vectors being
derived from the specification
according to established criteria
 Consideration of model
integration stages
 Consideration of module
interaction
6 Supporting activities  Documentation of the results of
module and integration tests,
(See “Module and including test results and
Integration Testing at the achievement of test objectives
Model Level” in the and criteria
Embedded Coder
Reference Workflow)  Corrective action on failure of
module and integration tests
 Impact analysis

2-3
2-4
3 Code Verification
 Checklist 2: Code Verification

Technique / Measure Associated Requirements Used / Used to Interpretation in

a limited degree this application,
/ Not used Evidence
7 Equivalence test vector  Structural coverage with respect
generation to applicable model coverage
metrics (SIL 2 and above); see
(See “Equivalence Test table “Model Coverage
Vector Generation” in Analysis”
the Embedded Coder™
Reference Workflow)  Creation of additional test
vectors (if applicable)
 Assessment of or justification
for uncovered model parts
8 Equivalence test  Stimulation of the model used
execution for production code generation

(See “Equivalence  Stimulation of the executable

Test Vector Generation” derived from the generated
in the Embedded Coder code
Reference Workflow)  Test execution in a target-like
environment or analysis of the
differences between testing and
the target environment
 Assessment of model parts used
for simulation but not for code
generation
9 Signal comparison  Designation of a suitable
comparison algorithm and
(See “Signal acceptance threshold
Comparison” in the
Embedded Coder  Comparison of simulation
Reference Workflow) results and execution results
10 Supporting activities  Documentation of the results of
equivalence tests
(See “Equivalence
Testing Model Versus  Corrective action on failure of
Code” in the Embedded equivalence tests
Coder Reference  Evidence for using automated
Workflow) equivalence testing tools
 Evidence for validation of
equivalence testing tools

3-2
 Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
11 Prevention of  Model and code coverage
unintended functionality comparison or traceability
(SIL 2 and above) review, see table “Prevention of
Unintended Functionality”
(See “Prevention of
Unintended  Assessment of or justification
Functionality” in the for issues revealed
Embedded Coder
Reference Workflow)
12 Supporting activities  Documentation of the results of
demonstrating the absence of
(See “Prevention of unintended functionality
Unintended
Functionality” in the  Corrective action on failure to
Embedded Coder demonstrate the absence of
Reference Workflow) unintended functionality

3-3
3-4
4 Additional Considerations
 Checklist 3: Additional Considerations
Technique / Measure
13 Verification and validation
of hand code (if applicable)
(See “Hand Coded Portions
within the Generated Code”
in the Embedded Coder™
Reference Workflow)
14 Supporting activities
(See “Hand Coded Portions
within the Generated Code”
in the Embedded Coder
Reference Workflow)
15 Verification and validation
of generated AUTOSAR
files (if applicable)
(See “Generated
AUTOSAR Files” in the
Embedded Coder Reference
Workflow)
16 Supporting activities
(See “Generated
AUTOSAR Files” in the
Embedded Coder Reference
Workflow)
17 Deviation from the
reference workflow
(See “Deviation from the
Reference Workflow” in the
Embedded Coder Reference
Workflow)
Associated Requirements Used / Used Interpretation in
to a limited this application,
degree / Not Evidence
used
 Designation of measures to
verify and validate hand code
 Consideration of the interfaces
between hand code and
generated code
 Traceability to the software
requirements specification
 Documentation of the results
of verifying and validating the
hand code
 Corrective action in case of
the detection of errors in the
hand code
 Designation of measures to
verify and validate generated
AUTOSAR files
 Documentation of the results
of verifying and validating
generated AUTOSAR files
 Corrective action in case of
the detection of errors in the
generated AUTOSAR files
 Documentation and
justification for deviations
from the reference workflow
by using a deviation
procedure, if applicable
4-2
 Technique / Measure
18 Integration with the
software safety lifecycle
(See “Integration with the
Software Safety Lifecycle”
in the Embedded Coder
Reference Workflow)
19 Configuration management
and revision control
(See “Configuration
Management and Revision
Control” in the Embedded
Coder Reference Workflow)
20 Installation integrity and
release compatibility
(See “Installation Integrity
and Release Compatibility”
in the Embedded Coder
Reference Workflow)
21 Bug reporting
(See “Bug Reporting” in the
Embedded Coder Reference
Workflow)
22 Competency of the project
team
(See “Competency of the
Project Team” in the
Embedded Coder Reference
Workflow)
Associated Requirements Used / Used Interpretation in
to a limited this application,
degree / Not Evidence
used
 Documented software safety
lifecycle, including
application-specific
verification and validation
activities
 Revision control for artifacts
to be validated or verified
 Configuration management for
artifacts to be validated or
verified (SIL 2 and above)
 Validation of modification and
additions to shipping tools (if
applicable)
 Compatibility of product
versions for model creation,
code generation, and
translation validation
 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
 Evidence for competence of
project team members
4-3
 Technique / Measure Associated Requirements Used / Used Interpretation in
to a limited this application,
degree / Not Evidence
used
23 Workshare  Documentation of workshare
Considerations between OEM and supplier, if
applicable
(See “Workshare
Considerations” in the
Embedded Coder Reference
Workflow)

4-4