Beruflich Dokumente
Kultur Dokumente
www.mathworks.com
www.mathworks.com/sales_and_services
User community:
www.mathworks.com/matlabcentral
Technical support:
www.mathworks.com/support/contact_us
Phone:
508-647-7000
Revision History
September 2015
New for IEC Certification Kit Version 3.6 (Applies to Release 2015b)
Contents
1 Introduction ...................................................................................................................................... 1-1
1.1 Overview ................................................................................................................................. 1-2
2 Integration of Simulink Test into the Model-Based Design Process ................................................ 2-1
2.1 Workflow Overview ................................................................................................................ 2-2
2.2 Tool Use Cases ........................................................................................................................ 2-5
[SLTEST_UC1] Development and execution of tests for Simulink models ................................ 2-5
[SLTEST_UC2] Development and execution of tests for back-to-back testing between model and
code .............................................................................................................................................. 2-5
[SLTEST_UC3] Assessment of test results ................................................................................. 2-5
[SLTEST_UC4] Generation of test reports .................................................................................. 2-5
[SLTEST_UC5] Identification of traceability between requirements and tests cases.................. 2-6
2.3 Error Prevention and Detection Measures ............................................................................... 2-7
[SLTEST_M1] Requirements-based testing ................................................................................ 2-7
[SLTEST_M2] Tool installation integrity checks ........................................................................ 2-7
[SLTEST_M3] Configuration management ................................................................................. 2-7
[SLTEST_M4] Input data integrity checks .................................................................................. 2-7
[SLTEST_M5] Competency of project team ............................................................................... 2-7
[SLTEST_M7] Manual comparison of test results to expected results ........................................ 2-7
[SLTEST_M8] Manual review of test report content .................................................................. 2-8
3 Additional Considerations ................................................................................................................ 3-1
3.1 Configuration Management and Revision Control .................................................................. 3-2
3.2 Competency of the Project Team ............................................................................................ 3-3
3.3 Installation Integrity and Release Compatibility ..................................................................... 3-4
3.4 Bug Reporting ......................................................................................................................... 3-5
3.5 Deviation from the Reference Workflow ................................................................................ 3-6
3.6 Integration with the Software Safety Life Cycle ..................................................................... 3-7
4 Workflow Overview......................................................................................................................... 4-1
5 Conformance Demonstration Template ........................................................................................... 5-3
6 References ........................................................................................................................................ 6-1
vi
1 Introduction
1.1 Overview
Simulink Test provides tools for authoring, managing, and executing systematic, simulationbased tests of the Simulink models. You can create nonintrusive test harnesses to test models
and subsystems. Simulink Test includes a test sequence block that lets you construct complex
test sequences and assessments, and a test manager that lets you manage and execute tests. It
enables functional, baseline, equivalence, and back-to-back testing, including software-in-theloop (SIL) and processor-in-the-loop (PIL). You can generate reports, archive and review test
results, rerun failed tests, and debug the component or system under test.
The test harness in Simulink Test lets you test components without creating a separate test
model. You can apply pass and fail criteria that include absolute and relative tolerances, limits,
logical checks, and temporal conditions. Test execution can be automated or customized with
setup and cleanup scripts. Simulink Test stores test cases and their results, creating a repository
for reviewing and investigating failures. You can link requirements to a test case captured in
Microsoft Word, IBM, Rational, DOORS, and other documents (with Simulink
Verification and Validation).
Key capabilities of Simulink Test include:
This document provides a reference workflow for Simulink Test. In particular, it describes how
to:
Users of the Simulink Test tool seeking to leverage the certification or qualification of the tool
shall carry out this workflow as part of the overall ISO 26262, IEC 61508, or EN 50128
software safety lifecycle.
The document is organized as follows:
1-2
Chapter 2, Integration of Simulink Test into the Model-Based Design Process provides a
reference workflow for the Simulink Test tool. It describes reference use cases and measures
to prevent or detect potential tool errors.
Chapter 3, Additional Considerations describes tool options that impact verification results,
and other considerations such as tailoring and bug reporting.
Chapter 4, Workflow Overview summarizes the workflow in a tabular way.
Chapter 5, Conformance Demonstration Template references a template that can be used to
demonstrate conformance with this reference workflow.
Chapter 6, References lists the standards and guidelines referenced in this document
Disclaimer While adhering to the recommendations in this document will reduce the risk that
an error is introduced in development and not be detected, it is not a guarantee that the system
being developed will be safe. Conversely, if some of the recommendations in this document are
not followed, it does not mean that the system being developed will be unsafe.
1-3
Note: For details about the capabilities and definitions of the terms, see the Simulink Test Users
Guide
During the development of embedded application software, you can use graphical modeling with
Simulink, Fixed-Point Designer, and Stateflow to conceptualize the functionality. Using
this modeling paradigm, the application software is modeled using time-based block diagrams
and event-based state machines. The model of the application software is simulated (executed)
within the Simulink environment. The model serves as the primary representation of the
application software throughout the development process, specifying functionality and design
information, and serving as a source for automated code generation with Embedded Coder. In
practice, this model elaboration is characterized by a step-wise transformation of the application
software model from an early executable specification into a model suitable for production code
generation, and then finally into C or C++ code. To accomplish the transformation, the model is
enhanced by adding design information and implementation details. The development process
becomes the successive refinement of models, followed by automatic code generation and
compilation and linking, as shown in Figure 1.
Note: For details about the parts of the workflow related to other tools and corresponding error
detection and mitigation measures, see the following documents:
2-2
Simulink test features integrated into the Model-Based Design Process are shown on Figure 2.
Note: all types of testing shown on the Figure 2 (module, integration, equivalence and back-toback testing) include the activities described in the use cases (development and execution of
tests, assessment of test results, generation of test reports, traceability identification)
Solid arrows in the figure indicate the succession of software development activities.
2-3
2-4
2-5
2-6
2-7
2-8
3 Additional Considerations
When implementing this reference workflow, consider the following topics:
3-2
3-3
3-4
You can use the bug reports section of the MathWorks web site
Test.
Note You can use the IEC Certification Kit Model Advisor check Display bug reports for
Simulink Test to display bug report information for this product.
The tool user shall validate modifications or additions to shipping product(s), if applicable.
3-5
3-6
3-7
4 Workflow Overview
Objective
Prerequisites
Verification
and testing of
Simulink
models
Back-to-back
testing
between
model and
code
Work Products
Simulink model to
be verified/tested
Software
requirements and
architectural
specifications for the
development model
to be tested
Simulink model to
testing)
4-2
5 Conformance Demonstration
Template
To justify that the requirements outlined in this document have been satisfied, you must provide
evidence for the activities that have been carried out.
The IEC Certification Kit product provides an editable Conformance Demonstration Template that can
be used to demonstrate conformance with the parts of ISO 26262-6, IEC 61508-3, or EN 50128
covered in this document.
To access the conformance demonstration template, on the MATLAB command line, type
certkitiec to open the Artifacts Explorer. The template is in Simulink Test.
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) that satisfies the requirement.
5-3
5-4
6 References
[1] IEC 61508-3:2010. International Standard IEC 61508 Functional safety of electrical / electronic /
programmable electronic safety-related systems Part 3: Software requirements. Second edition,
2010.
[2] ISO 26262-6:2011. Road vehicles Functional safety Part 6: Product development: software
level. International Standard, 2011.
[3] EN 50128:2011. Railway applications - Communication, signaling and processing systems Software for railway control and protection systems. International Standard 2011.
[4] The MathWorks. Software Quality Objectives for Source Code. Version 3.0, 2012.