Model-Based Design for DO-178C Software Development with MathWorks Tools, 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 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.

Note: Simulink Verification and Validation transitioned to Simulink Check, Simulink Coverage, and Simulink Requirements in R2017b.