Accelerating the pace of engineering and science

Model-Based Design for DO-178C Software Development with MathWorks Tools, Part 2: Requirements-Based Modeling and Traceability

From the series: Model-Based Design for DO-178C Software Development with MathWorks Tools

Register to watch video

Mike Anthony, MathWorks

In part 2 of this webinar series, we discuss how to build a Simulink model from a requirements document, and how to then create bi-directional links for traceability between the detailed design model and the textual high-level requirements. 

In a high-integrity software development process, one of the most fundamental ideas is that the software development must be requirements-based. The idea of traceability helps ensure completeness in the design. Traceability of the model to the textual requirements (or bottom-to-top traceability) helps ensure that the design satisfies all of its high-level requirements. Traceability of the requirements to the model (top-to-bottom traceability) helps ensure that everything in the model satisfies a requirement. In other words, no capability exists that is not explicitly required. 

This webinar will walk through a simple example of how to use Simulink and Simulink Verification and Validation to accomplish this task.

Product Focus

  • DO Qualification Kit
  • Simulink
  • Stateflow
  • Simulink Verification and Validation

Recorded: 31 Mar 2013

Series: Model-Based Design for DO-178C Software Development with MathWorks Tools

Introduction

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.

Development and Verification of the Model

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 5: Proving Algorithmic Correctness
In part 5 of this webinar series, we discuss the idea of using formal methods to further verify the model and assess robustness.

Development and Verification of the Code

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.

Part 9: Verification of the Object Code Against the Model
In part 9 of this webinar series, we discuss requirements-based testing of the cross-compiled executable object code.