DO Qualification Kit: Simulink Test™ Tool Qualification Plan
DO Qualification Kit: Simulink Test™ Tool Qualification Plan
Simulink® Test™
Tool Qualification Plan
R2020b
This document comprises the Tool Qualification Plan (Reference DO-330 Section 10.1.2) for the following
capabilities of Simulink® Test™. It is intended for use in the DO-178C and DO-330 tool qualification process
for Criteria 3 TQL-5 tools.
• Comparing simulation results or executable object code test results against expected results to
determine pass/fail simulation or test status.
• Generating reports that contain information on pass/fail simulation or test status, and requirements
tracing
With Simulink Test you can create nonintrusive test harnesses to isolate the component under test. You can
define requirements-based assessments using a text-based language, and specify test input, expected
outputs, and tolerances in a variety of formats, including Microsoft® Excel. Simulink Test includes a Test
Sequence block that lets you construct complex test sequences and assessments, and a test manager for
managing and executing tests. Observer blocks let you access any signal or state in the design without
changing the model or the model interface. Large sets of tests can be organized and executed in parallel or
on continuous integration systems.
You can trace tests to requirements (with Simulink Requirements™) and generate reports that include test
coverage information from Simulink Coverage™.
This section provides the certification considerations for the following capabilities of the Simulink Test
verification tool:
• Compare simulation results or executable object code test results against expected results to determine
pass/fail simulation or test status.
• Generate reports that contain information on pass/fail simulation status, and requirements tracing.
Question Answer
Can the tool insert an error into the airborne software or fail to detect an existing error in the Yes1
software within the scope of its intended usage?
Will the output of the tool not be verified as specified in Section 6 of DO-178C, DO-278A, DO- Yes
331, DO-332 or DO-333?
Are processes of DO-178C, DO-278A, DO-331, DO-332 or DO-333 eliminated, reduced, or Yes
automated by the use of the tool? Will you use output from the tool to meet an objective or
replace an objective of DO-178C, DO-278A, DO-331, DO-332 or DO-333, Annex A or Annex C?
Because the answers to the preceding questions are yes, Simulink Test shall be qualified.
To determine the type of qualification (Criteria 1, Criteria 2, or Criteria 3), the following questions based on
guidance of paragraph 12.2.2 of DO-178C about the tool are addressed:
Question Answer
Is the tool output part of the airborne software, such that the output can insert an error into No
the software?
Could the tool fail to detect an error in the airborne software and is the tool also used to No
justify the elimination or reduction of either of the following:
• Verification processes other than that automated by the tool.
• Development processes that could have an impact on the airborne software.
Could the tool fail to detect an error in the airborne software? Yes
Because the answer to the preceding first and second questions are no, Simulink Test can be qualified as a
Criteria 3 tool.
Table 1 Simulink Test with Respect to DO-331, DO-178, and DO-278 Objectives
DO-331 DO-178/278
Objective Table Reference Table Reference Credit Taken
(MB10) Simulation MB.A-3 MB.6.8.3.2.c N/A N/A Partial2 – Simulink Test is used
results are correct MB.C-3 to compare actual simulation
and discrepancies results to expected results;
explained discrepancies have to be
analyzed and explained
manually.
(MB16) Simulation MB.A-4 MB.6.8.3.2.c N/A N/A Partial2 – Simulink Test is used
results are correct MB.C-4 to compare actual simulation
and discrepancies results to expected results;
explained discrepancies have to be
analyzed and explained
manually.
(1) Executable Object N/A N/A A-6 6.4.a Partial3 – Simulink Test is used
Code complies with to compare actual executable
high-level object code test results to
requirements expected results. The expected
results must be provided as
input to this tool.
(2) Executable Object N/A N/A A-6 6.4.b Partial3 – Simulink Test is used
Code is robust with to compare actual executable
high-level object code test results to
requirements expected results. The expected
results must be provided as
input to this tool.
(3) Executable Object N/A N/A A-6 6.4.c Partial3 – Simulink Test is used
Code complies with to compare actual executable
low-level object code test results to
requirements expected results. The expected
results must be provided as
input to this tool.
(4) Executable Object N/A N/A A-6 6.4.d Partial3 – Simulink Test is used
Code is robust with to compare actual executable
low-level object code test results to
requirements expected results. The expected
results must be provided as
input to this tool.
2 This credit is taken only if the Simulink® and Stateflow® models are considered as a Design or Specification Models for the project and
simulation is used as a means of compliance for objectives 1, 2, 4, or 7 of Tables MB.A-3, MB.A-4, MB.C-3 or MB.C-4.
3 This credit is taken only if Simulink Test is used to automatically verify output from execution of executable object code.
(3) Test coverage of N/A N/A A-7 6.4.4.a Partial3 – Simulink Test is used
high-level to generate a report for
requirements is traceability between high-level
achieved requirements and test. The
links between high-level
requirements and test must be
set manually.
(4) Test coverage of N/A N/A A-7 6.4.4.b Partial3 – Simulink Test is used
low-level to generate a report for
requirements is traceability between high-level
achieved requirements and test. The
links between high-level
requirements and test must be
set manually.
Artifact File
Simulink Test Tool Qualification Plan, R2020b (this qualkitdo_sltest_tqp.docx/pdf
document)
4.2 Planning
The Plan for Software Aspects of Certification (PSAC) designates that the Simulink Test will be qualified as a
Criteria 3, TQL-5 tool.
This document provides the Tool Qualification Plan for Simulink Test.
• Review the tool operational requirements for applicability to the project under consideration.
• Configure the tool operational requirements in a configuration management system.
4.5 Verification
Requirements-based test procedures are developed from the tool operational requirements by MathWorks
and provided to the tool user to execute in the installed environment. The test cases and procedures will be
developed in the form of the Simulink Test test file, which exercises the capabilities being qualified in
Simulink Test.
For general information about the testing procedure, see Simulink Test Test Cases and Procedures.
Executing the test procedure generates results that are published in tool qualification reports; see artifact
Execute Qualification Tests and Review Test Results Simulink Test for more information.
• Review the test cases and procedures for applicability to the project under consideration.
• Configure the test cases and procedures in a configuration management system.
• Execute the test cases and procedures in the installed environment.
• Review the test results and confirm they are correct and discrepancies are explained.
• Configure the test results in a configuration management system
The bug report system provides an interface for customers to view and submit bug reports. Users can track
the status of open bugs. Users can choose to receive notifications for new or updated bug reports. The bug
reports on this web site include internally and externally nominated bugs. If applicable, bug reports include
provisions for known workarounds or file replacements. Customers can use the bug report mechanism to
nominate bugs. These nominations are processed and evaluated by The MathWorks, Inc. development
organization.
To open the DO Qualification Kit bug report checks, from the Simulink toolstrip:
The Model Advisor opens. Select and run the check for the bug report you would like to review.
The following table shows the life cycle data for the Simulink Test capability. The table maps the documents
and artifacts to DO-330 life cycle data items. For additional information about the documents and artifacts,
contact MathWorks.
In the following table, the Tool User Action column defines the responsibility of the tool user with regard to
making the data available to certification authorities. For data marked “Submit”, the tool-user must deliver
the data to the certification authorities. When marked “Available”, the data must be available at the tool-
user’s or tool vendor’s site for inspection by the certification authorities.
DO-330, section 10.3.1 <Insert reference to the Simulink Available Authored by MathWorks.
Tool Operational Test Tool Operational Requirement
Requirements artifact and tool user
documentation>
DO-330, section 10.3.3 and Execute Qualification Tests and Available MathWorks provides test cases.
10.2.5 Review Test Results for Simulink Test The tool user can add or remove
Test Cases and Procedures Simulink Test Test Cases and test cases as appropriate for the
Procedures tests used in their project.
Test Cases
qualkitdo_sltest_rs.rpt
DO-330 section 10.1.16 <Insert reference to Software Submit Provided by tool user.
Tool-specific information in Accomplishment Summary artifact>
Software Accomplishment
Summary (SAS)
DO-330 section 10.1.15 <Insert reference to the Tool Submit Provided by tool user.
Tool Accomplishment Qualification Accomplishment
Summary Summary artifact>