In this webinar series, we provide an introduction to a Software Development process for DO-178C/DO-331 using MathWorks tools. The example starts from textual requirements and follows the development process all the way through verification of the object code on the target processor. This process can be divided into two categories:
For more information on this process and the tools in use, please visit our webpage on DO-178C. More detailed information on how these tasks relate to specific objectives in DO-178C/D)-331 is available in MathWork’s DO Qualification Kit. We also provide solutions for other standards related to DO-178C, such as DO-254 and ARP-4754A.
Part 1 Introduction to Model-Based Design for High Integrity Software Development In this first webinar in the series, we introduce Model-Based Design and discuss why it can provide value over traditional software development processes in certification workflows.
Part 2 Requirements-Based Modeling and Traceability In part 2 of this webinar series, we discuss how to build a Simulink model from a requirements document, and how to create bi-directional links for traceability between the detailed design model and the textual high-level requirements.
Part 3 Conformance to Modeling Standards In part 3 of this webinar series, we discuss the importance of developing and enforcing a modeling standard.
Part 4 Verification of the Model Against High-Level Requirements In part 4 of this webinar series, we discuss verification of the model against the textual requirements.
Part 6 Automatic Code Generation and Traceability In part 6 of this webinar series, we discuss automatic flight code generation.
Part 7 Proving Code Correctness In part 7 of this webinar series, we discuss the use of Polyspace for formal verification of the embedded software.
Part 8 Automatic Test Vector Generation and Software-In-the-Loop Testing In part 8 of this webinar series, we discuss the use of Simulink Code Inspector to automate source code reviews.