Introduction
Modern aircraft rely on software to manage critical functions such as flight controls, navigation, communication, cockpit displays, and monitoring systems. Since software failures in aviation can have serious consequences, ensuring software safety, reliability, and regulatory compliance is essential.
This is where DO-178C certification becomes important. DO-178C is a widely recognized guidance document used to demonstrate that airborne software has been developed and verified according to rigorous safety and assurance objectives.
For aerospace manufacturers, avionics developers, and engineering organizations, understanding DO-178C is essential when developing software for commercial, business, and other aircraft systems. In this guide, we explore the standard, its software levels, the verification process, and the role of specialized engineering partners in achieving compliance.
What Is DO-178C Certification?
DO-178C, formally titled Software Considerations in Airborne Systems and Equipment Certification, is a standard published by RTCA. It provides guidance for demonstrating the safety and assurance of software used in airborne systems and equipment.
Although commonly called DO-178C certification, the document itself is not a standalone certification issued to a software product. Instead, it establishes objectives and activities that help applicants demonstrate software compliance as part of an aircraft or equipment certification process.
The standard emphasizes a structured development lifecycle, requirements traceability, verification, configuration management, quality assurance, and comprehensive documentation.
Following these practices helps development teams identify errors early, maintain consistency throughout the software lifecycle, and provide evidence that the software meets its intended requirements.
Why Is DO-178C Important for Aviation Software?
Aircraft software must operate reliably under demanding conditions. An undetected defect in a safety-critical system could affect aircraft operations, making systematic development and verification essential.
Key benefits of following DO-178C include:
- Improved software safety: Defined development and verification objectives help teams identify and address potential defects.
- Better requirements traceability: Requirements can be linked to design, source code, and verification evidence.
- Consistent development practices: Documented processes establish clear responsibilities and review procedures.
- Stronger verification evidence: Structured reviews and testing provide evidence that software meets its requirements.
- Support for certification activities: Compliance data helps applicants demonstrate that applicable objectives have been satisfied.
Effective avionics software testing is a central part of this process because it helps verify that software behaves as expected under defined conditions.
Understanding DO-178C Software Levels
DO-178C defines five software levels, designated Level A through Level E. The applicable level is determined by the potential consequences of a software failure, based on the system safety assessment.
Level A: Catastrophic
Level A applies when a software failure could contribute to a catastrophic failure condition. It has the most extensive set of software assurance objectives and verification expectations.
Level B: Hazardous or Severe-Major
Level B applies when software failure could contribute to a hazardous or severe-major failure condition. It requires substantial verification and development evidence.
Level C: Major
Level C applies when a failure could contribute to a major failure condition. The required objectives are less extensive than those for Levels A and B.
Level D: Minor
Level D applies when a failure could contribute to a minor failure condition. The associated assurance objectives are less demanding than those for higher software levels.
Level E: No Safety Effect
Level E applies when software failure has no effect on aircraft safety. DO-178C does not prescribe software assurance objectives for Level E.
Selecting the correct software level is essential because it determines the applicable objectives, verification activities, and evidence required throughout the development lifecycle.
Key Activities in the DO-178C Compliance Process
Achieving compliance involves coordinated activities across planning, development, verification, and certification support.
1. Planning and Standards Definition
The team establishes the software development and verification plans, defines applicable standards, identifies responsibilities, and determines how compliance evidence will be produced.
2. Requirements Development
High-level requirements describe the intended software functions. These are refined into low-level requirements that provide sufficient detail for implementation and verification.
Requirements must be reviewed for correctness, completeness, consistency, and verifiability.
3. Software Design and Implementation
Engineers develop the software architecture, detailed design, and source code in accordance with the applicable plans and standards. Reviews help identify defects before they progress to later stages.
4. Verification and Testing
Verification includes reviews, analyses, and testing activities appropriate to the assigned software level.
Depending on the applicable objectives, activities may include requirements-based testing, structural coverage analysis, and checks for unintended functionality. For Level A, Modified Condition/Decision Coverage (MC/DC) is an important structural coverage objective.
Robust avionics software testing also involves maintaining traceability between requirements, test cases, test results, and identified defects.
5. Configuration Management and Quality Assurance
Configuration management ensures that software versions, development artifacts, and changes remain controlled and traceable. Quality assurance activities help establish confidence that the planned processes and standards are followed.
6. Compliance Documentation
The team prepares the required plans, standards, records, verification results, and compliance summaries. These artifacts support the certification review and help demonstrate that applicable objectives have been satisfied.
The Role of Avionics Engineering Services
Developing compliant airborne software requires specialized technical expertise, disciplined processes, and careful coordination across engineering teams.
Professional avionics engineering services can support organizations with software development, requirements analysis, verification planning, testing, documentation, and certification-related activities.
An experienced engineering partner can also help identify process gaps, improve traceability, and coordinate verification activities across complex projects. The precise scope of support depends on the project, applicable regulatory requirements, and the capabilities of the engineering provider.
Organizations should evaluate potential partners based on their relevant aerospace experience, technical competence, quality processes, documentation practices, and ability to work within established development and certification plans.
Sign in to leave a comment.