From the series: Using Qualified Tools in a DO-178C Development Process
Bill Potter, MathWorks
Tracing from low-level software requirements to high-level software requirements is an objective in DO-178C. When using Model-Based Design, DO-331 requires tracing from the model to the high-level software requirements when the design is implemented in models. Simulink Requirements™ provides an interface that allows users to trace from model elements to requirements documents or third-party requirements tools. This tracing capability is included for Simulink®, Stateflow®, and MATLAB® block code. DO-178C and DO-331 also require that design data and trace data are produced as part of the development process. The Simulink Report Generator™ can automatically produce a design description document from the model, and that document contains a section that includes the trace links from the model to the requirements. The design description document also includes snapshots of the top level of the model and all subsystems within the model, as well as all of the interface definitions and block settings. Additionally, there is a section with all model-wide settings. This report can be provided in various formats, such as Rich Text, Word, HTML or PDF for long-term archiving. The DO Qualification Kit provides the necessary artifacts to qualify automatic generation of this document by the Simulink Report Generator.
Part 1: Introduction to Model-Based Development for DO-178C Learn how to use of 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.
Part 2: 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.
Part 3: 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.
Part 4: 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.
Part 5: 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.
Part 6: 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.
Part 7: 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.
Part 8: 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.
Part 9: Qualified Test Generation 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.
Part 10: Qualified Software Testing 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.
Choose your country to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .Select
You can also select a location from the following list: