Using Qualified Tools in a DO-178C Development Process
You will learn how to use MathWorks tools in a DO-178C process, starting with the requirements process and ending with the verification of the software. This video series covers DO-331 Model-Based Development and Verification, as well as DO-333 Formal Methods. Additionally, DO-330 Software Tool Qualification Considerations will be addressed by an explanation of the DO Qualification Kit.
Introduction to Model-Based Development for DO-178C
Learn how to use Model-Based Design and formal methods with Simulink, Stateflow, Embedded Coder, and the DO Qualification Kit in a process compliant with DO-178C, DO-331, DO-333, and DO-330.
Qualified Model Verification – Requirements Tracing
Perform tracing from models to requirements, in compliance with DO-178C and DO-331, using Simulink Requirements, and then generate a design description document using Simulink Report Generator.
Qualified Model Verification – Simulation
Perform simulation and model coverage analysis to verify models, in compliance with DO-178C and DO-331, using Simulink Test and Simulink Coverage.
Qualified Model Verification – Model Standards
Perform static analysis to verify model standards, consistency, and accuracy, in compliance with DO-178C and DO-331, using Simulink Check.
Qualified Model Verification – Design Errors
Perform formal methods analysis to verify model consistency and accuracy, in compliance with DO-178C and DO-333, using Simulink Design Verifier.
Qualified Code Verification – Model To Code
Use Embedded Coder and Simulink Code Inspector to generate code from models and verify that translation in compliance with DO-178C and DO-331.
Qualified Code Verification – Code Standards
Use Embedded Coder and Polyspace Bug Finder to generate code from models and verify coding standards in compliance with DO-178C and DO-331.
Qualified Code Verification – Code Errors
Perform formal methods analysis to verify code consistency and accuracy, in compliance with DO-178C and DO-333, using Polyspace Code Prover.
Use Simulink Design Verifier and Simulink Coverage to generate tests from models and verify low-level test coverage, in compliance with DO-178C and DO-331.
Use processor-in-the-loop capability and code coverage analysis to verify executable object code, in compliance with DO-178C and DO-331, with Simulink Test and Simulink Coverage.
Qualify MathWorks tools in compliance with DO-178C and DO-330 using the DO Qualification Kit.
