DO-178C (Document for Operational)
What Is DO-178C?
DO-178C, officially titled “Software Considerations in Airborne Systems and Equipment Certification,” is a set of guidelines published by RTCA (U.S.) and EUROCAE (Europe). It provides a rigorous framework to plan, develop, test, and certify software used in aircraft systems, ensuring that the software is both safe and compliant with regulatory requirements.
It is widely accepted by FAA, EASA, and other aviation authorities worldwide.
Why DO-178C Is Important
Airborne software can impact human lives. Whether it’s controlling engine thrust, displaying flight routes, or automating cabin pressure, a software error could have catastrophic consequences. DO-178C ensures:
-
Safety-critical systems behave predictably
-
Software is free from unintended behavior
-
Traceability exists between requirements, code, and tests
Key Principles of DO-178C
1. Software Levels (DAL – Design Assurance Levels)
The stringency of testing and process rigor depends on the criticality of the function:
Level | Effect of Failure | Examples |
---|---|---|
A | Catastrophic – causes crash | Fly-by-wire, flight control software |
B | Hazardous – crew workload/safety | Autopilot, terrain awareness |
C | Major – reduces efficiency | Navigation display, flight plan mgmt |
D | Minor – small impact on operations | Maintenance logging, alerts |
E | No effect on aircraft operation | Passenger Wi-Fi, IFE systems |
2. Development Life Cycle
DO-178C defines stages with strict entry/exit criteria:
-
Planning – Define objectives, plans and compliance strategy
-
Requirements – High-level & low-level functional requirements
-
Design & Coding – Adherence to standards and structure
-
Verification – Testing, reviews, static analysis
-
Configuration & QA – Version control, audits, baseline integrity
-
Certification – Submit artifacts to authority (EASA/FAA)
3. Traceability
Every requirement must be:
-
Linked to its design
-
Implemented in code
-
Verified with a test
This end-to-end traceability ensures no functionality is added without purpose or left untested—also known as bi-directional traceability.
4. Verification & Testing
Testing isn’t just functional. DO-178C also requires:
-
Structural coverage analysis (e.g., statement, branch, and MC/DC)
-
Robustness testing – unexpected inputs or failure modes
-
Reviews of requirements, design, and source code
Higher software levels (A/B) require independent verification—one team codes, another team tests.
Supplements to DO-178C
DO-178C is modular, with extra guidance available for specialized topics:
Supplement | Purpose |
---|---|
DO-330 | Tool qualification |
DO-331 | Model-Based Development (e.g., Simulink) |
DO-332 | Object-Oriented Technology |
DO-333 | Formal Methods (mathematical proofs) |
Real-World Applications
-
Autopilot software in commercial airliners (Level A)
-
Electronic Flight Bag (EFB) apps used by pilots (Level C or D)
Any software update, patch, or bug fix that affects a certified function must go through the DO-178C change process.
Tools Used in DO-178C Projects
-
JAMA/ DOORS – for requirements and traceability
-
JIRA / Polarion – for issue and workflow management
Comments
Post a Comment