This case study uses a simple helicopter control system to demonstrate a workflow compatible with ARP4754A, DO-178C and DO-331. The case study starts with system level requirements and provides the workflow all the way through executable object code verification. Although the demo uses many MathWorks toolbox licenses, in addition to MATLAB and Simulink, pre-generated artifacts are available for viewing without having to have all of those toolboxes installed on top of MATLAB and Simulink.
Cite As
Bill Potter (2021). DO178_case_study (https://github.com/wfpotter/DO178_Case_Study/releases/tag/1.3), GitHub. Retrieved .
Comments and Ratings (15)
MATLAB Release Compatibility
Platform Compatibility
Windows macOS LinuxCategories
- Code Generation > Embedded Coder > Code Generation from Simulink Models >
- Verification, Validation, and Test > Simulink Test >
- Code Generation > DO Qualification Kit (for DO-178) >
- Simulation Graphics and Reporting > Simulink Report Generator >
- Verification, Validation, and Test > Polyspace Code Prover >
- Verification, Validation, and Test > Simulink Check > Check Model Compliance >
Tags
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!Discover Live Editor
Create scripts with code, output, and formatted text in a single executable document.
DO_03_Design/AHRS_voter/specification
DO_03_Design/ActuatorLoop/specification
DO_03_Design/FCC/specification
DO_03_Design/Heli_inner_loop/specification
DO_03_Design/Heli_outer_loop/specification
tools/checks/mw
tools/compatible_blocks
tools/templates/model_configurations
tools/utilities
tools/utilities/code_generation
tools/utilities/modeling
tools/utilities/project_management
tools/utilities/project_management/shutdown
tools/utilities/project_management/startup
tools/utilities/report_generation
tools/utilities/requirements_management
tools/utilities/verification/dynamic_testing
tools/utilities/verification/static_analysis
work
DO_03_Design/AHRS_voter/specification
DO_03_Design/ActuatorLoop/specification
DO_03_Design/FCC/specification
DO_03_Design/FCC/verification/design_error_detections/dead_logic
DO_03_Design/FCC/verification/design_error_detections/dead_logic/dead_logic
DO_03_Design/FCC/verification/design_error_detections/design_error
DO_03_Design/Heli_inner_loop/specification
DO_03_Design/Heli_outer_loop/specification
DO_03_Design/common/block_libraries/specification
tools/compatible_blocks
tools/templates/model_configurations
tools/templates/model_templates
work
navigation
Select a Web Site
Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .
Select web siteYou can also select a web site from the following list:
Americas
- América Latina (Español)
- Canada (English)
- United States (English)
Europe
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)
I found the solution regarding my previous problem. If you go in the model advisor and run the Simulink Code Inspector checks on the AHRS_voter, some fails will came out.
Solve these fails as suggested in the results and everithing will work fine.
I followed the case study and I see that Simulink Code Inspector verification FAILS on the AHRS_voter.
Looking at the report I see a lot of "Failed to trace" and "Unable to process".
The big question is: How to debug and fix this?
I have downloaded and installed the toolbox file but cannot figure out how to access it
Very Helpful. Thanks.
This is great. Thanks.
Great job putting this all together! Would be great to see more information regarding robustness testing and automatic test generation.