Aerospace and Defense

Industry Standards


The DO-178B standard specifies objectives across the development cycle to achieve flight software certification. Activities to satisfy DO-178B objectives can be time-consuming and expensive, including several associated with design, coding, and integration processes:

  • Traceability to requirements
  • Compliance with requirements
  • Robustness of requirements
  • Conformance to standards

Using Model-Based Design, engineers can satisfy DO-178B objectives while realizing cost and time-to-market benefits associated with early verification of requirements, automated linking to requirements, model and code standards checking, code generation, report artifact generation, and test case reuse.

MATLAB, Simulink, and Embedded Coder support key development activities involving Model-Based Design for DO-178B. Additional products support important verification tasks:

The latest update to the DO-178 standard is DO-178C, which contains Model-Based Development and Verification (DO-331) and the Formal Methods supplements (DO-333) that map more closely to current industry development and verification practices.

Technical Article: Model-Based Design for DO-178B

Software systems deployed in safety-critical applications in aerospace and other industries must satisfy rigorous development and verification standards. One of the most widely used of these standards is DO-178B "Software Considerations in Airborne Systems and Equipment Certification." This article compares three approaches to using Simulink system models and Model-Based Design to develop safety-critical systems that must satisfy the DO-178B standard:

  • Using the model to capture only low-level software requirements
  • Using the model to capture both high- and low-level software requirements
  • Using separate models to capture the high-level and low-level software requirements

Read full Model-Based Design for DO-178B article

Key products for developing DO-178B applications:

More about MathWorks support for DO-178B: