Model-Based Design for DO-178C/DO-331 Compliance

Day 1 of 3

Model-Based Design for DO-178C/DO-331 Overview

Objective: Understand how MathWorks workflows can satisfy and support DO-178C and DO-331 objectives.

• Overview of system, software, and hardware life cycles
• DO-178C/DO-331 workflow with Model-Based Design
• Satisfying DO-178C/DO-331 objectives using Model-Based Design

Requirements Traceability

Objective: Trace a model to requirements according to DO-178/DO-331 compliance.

• Requirements overview in the DO-178C process
• Using Requirements Toolbox for requirement traceability
• Generating a System Design Description (SDD)
• Understanding compatibility with external requirement tools

Modeling Standards for DO-178C/DO-331

Objective: Understand conformance to modeling standards for DO-178C/DO-331.

• Modeling standards for DO-178C/DO-331 applications
• Modeling standards in the Model-Based Design (MBD) process
• Using Simulink Check pre-packaged rules for high-integrity systems

Day 2 of 3

Model Verification

Objective: Learn to verify software requirements through simulation.

• Test cases authoring in Simulink Test
• Test case inputs and data collection options
• Tracing test cases to requirements
• Requirements-based testing with Simulink Test

Model Coverage

Objective: Utilize Simulink Coverage to collect model coverage data.

• Model coverage metrics
• Capturing model coverage with Simulink Coverage
• Missing model coverage resolution

Derived Requirements and Design Verification

Objective: Learn how to utilize Simulink Design Verifier for low level requirement verification.

• Simulink Design Verifier (SLDV) to identify unreachable elements
• Developing low-level tests for missing Model coverage
• Model coverage reporting

Day 3 of 3

Model-Code Verification and Traceability

Objective: Use Simulink Code Inspector to demonstrate structural and algorithmic equivalence between a model and its generated code.

• Code inspection overview
• Checking model compatibility for Simulink Code Inspector
• Verifying model-to-code traceability

Static Code Analysis and Formal Code Verification

Objective: Show that generated code is compliant with coding standards and prove that it is robust against various run-time errors.

• Polyspace tools overview
• Running Polyspace analyses from Simulink
• Enforcing coding standards with Polyspace Bug Finder
• Proving code robustness with Polyspace Code Prover
• Demonstrating control and data coupling coverage with Polyspace Code Prover

Code Verification Against Software Requirements

Objective: Use Simulink Test to demonstrate complete code coverage via software requirements test cases, and verify software requirements on the target hardware.

• Software-in-the-loop (SIL) and processor-in-the-loop (PIL) overview
• Testing executable object code against high-level requirements
• Collecting code coverage

Tool Qualification

Objective: Use DO Qualification Kit to qualify MathWorks products and features for DO-178C certification.

• Tool qualification requirements
• DO Qualification Kit overview
• Tool qualification example
• Qualifiable tools and credits taken
• DO Qualification Kit customization