DO-178C Compliance: Key Requirements for Airborne Software Development

Learn the key DO-178C compliance requirements for airborne software, including design assurance levels, verification, traceability, structural coverage, and certification planning.
TL;DR
- DO-178C guides the development of software for airborne systems.
- Five Design Assurance Levels (DAL A to DAL E) define applicable assurance objectives.
- Compliance involves planning, development, verification, and quality assurance.
- Traceability and structural coverage help demonstrate compliance.
- Mugen.Codes helps organisations explore relevant software engineering expertise.
Software plays a critical role in modern aircraft, supporting flight controls, navigation, communication, and monitoring systems.
Failures in these systems can compromise aircraft safety, making rigorous engineering processes and documented evidence essential to demonstrate that the software meets its specified requirements.
DO-178C provides guidance for developing airborne software and demonstrating that applicable software lifecycle objectives have been satisfied.
Understanding its requirements helps engineering teams plan development activities, establish verification processes, maintain traceability, and prepare the evidence needed to support airworthiness approval.
Mugen.Codes is a platform that connects organisations with software engineering expertise for complex technical projects. For teams working on safety-critical airborne systems, it provides a way to explore relevant engineering capabilities and identify expertise that aligns with their development requirements.
Table of Contents
- TL;DR
- What Is DO-178C Compliance?
- Understanding DO-178C Design Assurance Levels
- Key DO-178C Compliance Requirements
- Requirements Traceability and Compliance Documentation
- DO-178C Software Testing and Structural Coverage
- Common Challenges in Achieving DO-178C Compliance
- Best Practices for DO-178C Compliance
- How Mugen.Codes Supports Airborne Software Development
- FAQs
- Final Thoughts on DO-178C Compliance
What Is DO-178C Compliance?
DO-178C, formally titled Software Considerations in Airborne Systems and Equipment Certification, is a standard developed by RTCA with its European counterpart, EUROCAE.
It defines objectives and activities for developing airborne software and providing evidence that the software meets its requirements.
DO-178C compliance involves satisfying the objectives applicable to a software project’s assigned assurance level. This includes planning, requirements development, implementation, verification, configuration management, and quality assurance. The goal is to establish confidence in the software through a controlled and documented development process.
Purpose and Scope of DO-178C
DO-178C helps development teams demonstrate that airborne software has been developed and verified systematically. It supports the certification process by establishing expectations for software lifecycle activities and the evidence used to assess them.
The standard is relevant to software used in systems such as:
- Flight control and guidance systems
- Aircraft navigation and communication equipment
- Engine control systems
- Flight management and monitoring systems
Its applicable objectives depend on the software’s assigned Design Assurance Level (DAL) and the project’s certification context.
DO-178C and Airborne Software Certification
DO-178C supports the broader aircraft and equipment certification process, but following the standard does not automatically certify a software product or aircraft. Certification authorities assess the relevant evidence within the applicable approval framework.
Development teams must plan and document their activities, verify that software meets its requirements, manage identified problems, and demonstrate that applicable objectives have been satisfied. This evidence helps support certification reviews and provides a structured basis for assessing software assurance.
Understanding DO-178C Design Assurance Levels
DO-178C uses five software levels, from DAL A to DAL E, to determine the objectives applicable to airborne software. The assigned level is based on the potential consequences of a software failure, as established through the system safety assessment process.
These levels help determine the rigor of development and verification activities required for a particular software component.
The Five Software Levels: DAL A to DAL E
The five Design Assurance Levels are:
- DAL A: Software whose failure could contribute to a catastrophic aircraft condition.
- DAL B: Software whose failure could contribute to a hazardous or severe-major aircraft condition.
- DAL C: Software whose failure could contribute to a major aircraft condition.
- DAL D: Software whose failure could contribute to a minor aircraft condition.
- DAL E: Software whose failure has no effect on aircraft operational capability or pilot workload under the applicable classification.
DAL A generally has the most demanding assurance objectives, while DAL E has no DO-178C software objectives assigned to it. The applicable level is determined by the safety assessment, not simply by the software’s complexity or size.
How Design Assurance Levels Affect Software Development and Verification
The assigned DAL influences the planning, development, and verification objectives a project must satisfy. Higher assurance levels generally require more extensive evidence and additional verification rigor.
Key differences include:
- Verification objectives: The applicable reviews, analyses, and testing activities vary by level.
- Structural coverage: Higher levels require more demanding coverage analysis. DAL A requires Modified Condition/Decision Coverage (MC/DC), while DAL B requires decision coverage.
- Verification independence: Certain objectives require verification activities to be performed independently of the development activities they assess.
- Documentation and traceability: Teams must maintain lifecycle data and evidence appropriate to the applicable objectives.
Understanding these differences early helps teams allocate engineering resources, establish appropriate verification plans, and avoid gaps that could delay certification activities.
Key DO-178C Compliance Requirements

DO-178C compliance requires structured planning, development, verification, and quality assurance. Each activity helps demonstrate that the software meets its requirements and the objectives associated with its assigned Design Assurance Level.
Software Planning and Development Standards
Planning defines how the project will meet applicable DO-178C objectives throughout the software lifecycle.
Key activities include:
- Establishing development and verification plans.
- Defining coding standards and procedures.
- Assigning responsibilities and identifying required deliverables.
- Planning reviews, testing, and problem reporting.
Effective planning helps teams identify compliance gaps early and avoid costly rework.
Software Requirements Analysis and Design
Software requirements define expected behaviour and provide the foundation for implementation and verification. They must be clear, consistent, verifiable, and traceable to their sources.
Teams develop high-level requirements, refine them into low-level requirements, and establish a software design that supports the specified functionality. Well-defined requirements reduce ambiguity and make verification more effective.
Software Coding and Integration
Developers translate approved requirements and design specifications into source code using established coding standards and procedures. Integration then combines software components and helps identify interface and interaction problems.
Important activities include:
- Reviewing code for errors and deviations.
- Maintaining consistency with approved requirements and design.
- Verifying interfaces between software components.
- Recording and resolving identified problems.
Software Verification and Reviews
Verification provides evidence that software meets its requirements and applicable objectives. Activities include requirements and design reviews, code analysis, testing, and structural coverage analysis where required.
Verification must follow the project’s assigned assurance level. Certain objectives require independence between development and verification activities, and successful testing alone does not establish compliance.
Configuration Management and Quality Assurance
Configuration management controls software versions, changes, and approved releases. Quality assurance checks whether required processes and procedures are followed.
Key activities include:
- Tracking changes to requirements, code, and test artefacts.
- Maintaining version history and release records.
- Monitoring compliance with approved plans.
- Recording findings and corrective actions.
Together, these processes help maintain consistency and reliable compliance evidence.
Requirements Traceability and Compliance Documentation
Requirements traceability connects software requirements to design, implementation, and verification evidence. Supporting documentation helps teams demonstrate that applicable objectives have been satisfied and prepare for certification reviews.
Maintaining Requirements Traceability
Traceability helps teams confirm that requirements are implemented and adequately verified. It also reveals missing verification evidence and software elements without a clear requirements basis.
Effective traceability should connect:
- High-level and low-level requirements.
- Requirements, design, and implementation.
- Verification procedures and test results.
- Changes to affected engineering artefacts.
Software Lifecycle Data and Verification Evidence
DO-178C identifies lifecycle data needed to demonstrate compliance with applicable objectives. Depending on the project, this may include:
- Software development and verification plans.
- Requirements, design records, and source code.
- Verification procedures, results, and analysis records.
- Configuration management and quality assurance records.
- Problem reports and change histories.
These records should accurately reflect engineering activities and remain consistent throughout development.
Managing Software Changes and Defect Records
Changes to requirements, code, or design can affect existing compliance evidence. Teams must assess their impact, update relevant artefacts, and repeat verification activities where necessary.
A controlled process should include:
- Recording and tracking identified defects.
- Assessing the impact of proposed changes.
- Updating affected requirements and tests.
- Performing appropriate regression testing.
- Documenting resolutions and verification results.
Disciplined change management helps preserve traceability, maintain a consistent software baseline, and reduce compliance risks.
DO-178C Software Testing and Structural Coverage

Software testing and structural coverage analysis help demonstrate that airborne software behaves as specified and meets applicable verification objectives. Under DO-178C, the required activities depend on the software’s assigned Design Assurance Level.
Requirements-Based Testing
Requirements-based testing verifies that software behaves according to its approved requirements. Test cases should address expected functionality, relevant boundary conditions, and abnormal conditions where specified.
Effective testing involves:
- Designing test cases from software requirements.
- Defining expected results before executing tests.
- Recording test outcomes and investigating discrepancies.
- Retesting software after relevant corrections.
Statement, Decision, and Modified Condition/Decision Coverage (MC/DC)
Structural coverage analysis examines which parts of the source code execute during testing. DO-178C specifies different coverage objectives depending on the assurance level.
- Statement coverage: Determines whether each executable statement has been executed.
- Decision coverage: Determines whether each decision has produced all possible outcomes.
- MC/DC: Demonstrates that each condition in a decision can independently affect its outcome.
DAL C generally requires statement coverage, DAL B requires decision coverage, and DAL A requires MC/DC. These objectives complement requirements-based testing rather than replacing it.
Identifying and Resolving Structural Coverage Gaps
Coverage gaps occur when testing does not exercise all the code required by the applicable coverage objective. Teams must investigate uncovered sections to determine their cause.
Resolution may involve:
- Adding test cases to exercise missing behaviour.
- Correcting implementation or requirements inconsistencies.
- Investigating code that is not traceable to requirements.
- Providing appropriate analysis for identified coverage issues.
The goal is to demonstrate that the software is adequately verified and that unexplained or unintended functionality has been addressed.
Common Challenges in Achieving DO-178C Compliance
DO-178C compliance can be demanding because development teams must coordinate engineering activities, verification, documentation, and evidence management throughout the software lifecycle.
Incomplete or Changing Software Requirements
Ambiguous requirements make implementation and verification more difficult. Changes introduced late in development can also affect code, test cases, and previously established evidence.
Teams can reduce these risks through early requirements reviews, controlled change processes, and consistent stakeholder communication.
Documentation and Traceability Gaps
Missing or inconsistent records can make it difficult to demonstrate that requirements have been implemented and verified. Disconnected documentation also increases the effort required to assess changes and prepare for reviews.
Maintaining traceability throughout development helps identify gaps before they become significant project risks.
Verification Complexity and Coverage Gaps
Higher assurance levels introduce more demanding verification objectives. Complex logic, extensive dependencies, and difficult-to-reproduce conditions can make testing and structural coverage analysis challenging.
Early verification planning, systematic test design, and timely investigation of coverage gaps help manage this complexity.
Tool Qualification and Integration Challenges
Development and verification tools can improve consistency and reduce repetitive work, but their use must be assessed within the DO-178C framework. DO-330 provides guidance on software tool qualification where applicable.
Teams should evaluate tool capabilities, integration requirements, and the potential impact of tool errors when determining whether qualification is necessary.
Best Practices for DO-178C Compliance
A disciplined development process helps teams manage applicable objectives, maintain reliable evidence, and reduce avoidable delays during certification activities.
Establish Compliance Plans Early
Define development and verification activities, responsibilities, deliverables, and applicable objectives before implementation progresses significantly. Align planning with the software’s assigned assurance level.
Integrate Verification Throughout Development
Review requirements, design, and code as development progresses. Early verification helps identify defects before they spread across dependent components and reduces expensive late-stage corrections.
Maintain Traceability and Organise Compliance Evidence
Keep requirements, implementation records, test results, and change histories linked and up to date. Consistent evidence management makes gaps easier to identify and simplifies preparation for certification reviews.
Prepare for Certification Reviews
Review lifecycle data against applicable objectives, resolve outstanding problems, and confirm that verification evidence is complete and consistent. Early preparation gives teams more time to address deficiencies before formal review activities.
How Mugen.Codes Supports Airborne Software Development

Airborne software projects require specialised engineering expertise, disciplined development practices, and careful verification planning. Mugen.Codes helps organisations explore software engineering capabilities relevant to these technical demands.
Finding Relevant Software Engineering Expertise
As a platform for discovering software engineering capabilities, Mugen.Codes helps organisations explore expertise relevant to complex projects, including:
- Embedded Software Development: Expertise relevant to software operating within specialised hardware systems.
- Systems Engineering: Capabilities that support the development and integration of complex technical systems.
- Software Verification: Expertise relevant to testing, analysing, and verifying software behaviour.
Supporting Safety-Critical Development Projects
By helping teams identify relevant engineering capabilities, Mugen.Codes provides a starting point for exploring the expertise needed for airborne software development. Organisations can use the platform to identify capabilities aligned with their technical requirements and project objectives.
DO-178C compliance still depends on satisfying applicable objectives, following appropriate development and verification processes, and maintaining the required evidence throughout the software lifecycle.
FAQs
What Is DO-178C Compliance?
DO-178C compliance means satisfying the applicable objectives for developing and verifying airborne software. These objectives cover planning, requirements, implementation, verification, configuration management, and quality assurance.
Is DO-178C Compliance Mandatory for Airborne Software?
DO-178C is a widely recognised means of demonstrating compliance with applicable airworthiness requirements for airborne software. Whether it is required for a particular project depends on the applicable certification basis and approval process.
What Are the Five DO-178C Design Assurance Levels?
The five levels are DAL A, DAL B, DAL C, DAL D, and DAL E. DAL A corresponds to software whose failure could contribute to a catastrophic condition, while DAL E applies where software failure has no effect on aircraft operational capability or pilot workload under the applicable classification.
What Is the Difference Between DO-178C and DO-330?
DO-178C addresses software considerations in airborne systems and equipment certification. DO-330 provides guidance on software tool qualification, helping determine the qualification considerations for tools used in development or verification when applicable.
Does DO-178C Apply to All Aerospace Software?
No. DO-178C specifically addresses airborne software. Spacecraft software, satellite systems, and other aerospace applications may follow different standards and assurance frameworks depending on their purpose and applicable requirements.
Final Thoughts on DO-178C Compliance
DO-178C compliance requires more than functional software. Teams must establish appropriate development processes, verify requirements, maintain traceability, analyse structural coverage, and preserve reliable evidence throughout the software lifecycle.
Addressing these activities early helps organisations manage technical risks and prepare for certification reviews. Access to relevant engineering expertise can also support teams working through the challenges of safety-critical software development.
Ready to explore software engineering expertise for your next airborne software project?
Explore Mugen.Codes to discover capabilities relevant to your safety-critical development needs.


