Model-Based Design for DO-178C Software Development with MathWorks Tools, 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. In a requirements-based development process, the idea is to have at least one test case for each requirement. The executable Simulink model allows the developer to verify the model is functionally correct before generating the embedded software. This form of early verification makes use of Simulink and Simulink Report Generator to execute the requirements-based test cases against the model, compare the model’s behavior to the expected behavior to ensure proper functional behavior, and generate a test artifact documenting this testing. This example also makes use of the model coverage analysis feature of Simulink Verification and Validation, as a metric for completion of this requirements-based testing.

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.