RTCA DO-178

RTCA DO-178
Name	DO-178
Other names	Software Considerations in Airborne Systems and Equipment Certification
Author	RTCA
First pub	1982
Latest pub	2011 (DO-178C)
Domain	Aviation safety, Avionics

RTCA DO-178

RTCA DO-178 is a guidance document for avionics software certification developed by RTCA, Inc. and used by authorities such as the Federal Aviation Administration and European Union Aviation Safety Agency to achieve compliance with airworthiness standards; it informs certification artifacts required by bodies like Civil Aviation Authority (United Kingdom) and Transport Canada. The guidance interacts with standards and organizations including EUROCAE, RTCA DO-254, ARP4754A, AS9100, and industry stakeholders such as Boeing, Airbus, Lockheed Martin, Northrop Grumman, and GE Aviation.

Overview

DO-178 provides objectives, activities, and evidence expectations for software in airborne systems, aligning with regulatory frameworks like 14 CFR and EASA Certification Specifications. It defines lifecycle processes, verification methods, and data items that certification authorities—such as the FAA and EASA—review during type certification of platforms from manufacturers like Bombardier, Embraer, and Dassault Aviation. The guidance is applied in programs involving suppliers including Honeywell Aerospace, Rockwell Collins, Thales Group, and Safran, and it complements hardware-focused documents such as DO-254 and systems engineering practices from ISO 15288 and ARP4754A.

History and Versions

The original guidance emerged in the early 1980s amid advances in digital avionics used by projects like the Boeing 747-400 and Airbus A320; stakeholders included RTCA, Inc. committees, EUROCAE, and regulators like the FAA. Subsequent revisions responded to technological evolution exemplified by work from Honeywell, Collins Radio, and military programs managed by U.S. Department of Defense contractors; notable updates culminated in DO-178B (1992) influenced by programs such as F-16 upgrades and commercial avionics modernization. The 2011 revision (DO-178C) incorporated supplement material and technical content reflecting advances in model-based development, formal methods, and object-oriented design, harmonizing with standards including ISO 26262 techniques where applicable and interfacing with tool qualification concepts seen in DO-330.

Objectives and Lifecycle Processes

DO-178 prescribes lifecycle processes spanning planning, development, verification, configuration management, quality assurance, and certification liaison used by teams at Boeing, Airbus, Honeywell, and Thales Group. Planning documents such as the Plan for Software Aspects of Certification (PSAC) and Software Development Plan interlink with artifacts from programs like F-35 avionics and civil programs from Bombardier. Verification objectives require traceability linking high-level requirements to low-level requirements and source code, practices mirrored in projects at Lockheed Martin and Northrop Grumman, and they emphasize verification techniques employed by suppliers like GE Aviation and Safran.

Software Levels and Certification Objectives

The guidance defines software assurance levels (A through E) reflecting potential failure conditions, applied in certification of systems on aircraft such as Boeing 737 MAX, Airbus A380, and military platforms like F-35 Lightning II. Level A demands the most stringent objectives, influencing design and verification in flight-critical systems developed by Honeywell Aerospace and UTC Aerospace Systems. Certification objectives map to evidence types—requirements, design, code, test artifacts—that certification authorities including the FAA and EASA assess during validation and qualification of avionics suites in programs from Embraer and Dassault Aviation.

Tool Qualification and Evidence Requirements

DO-178C and supplements such as DO-330 outline qualification of development and verification tools used by vendors including Rockwell Collins and Thales Group; qualification activities involve confirmation of tool outputs via test harnesses, coverage analysis, and assurance cases used on programs like Boeing 787 and Airbus A350. Evidence requirements encompass verification reports, coverage metrics (statement, branch, MC/DC), configuration management records, and anomaly reports reviewed by authorities such as the FAA and Transport Canada for certification artifacts produced by suppliers like Honeywell and Safran.

Implementation and Industry Impact

Adoption of the guidance has shaped avionics engineering practices at major manufacturers—Boeing, Airbus, Lockheed Martin, Northrop Grumman—and Tier 1 suppliers—Honeywell Aerospace, Rockwell Collins, Thales Group—affecting toolchains including model-based design from MathWorks and static analysis tools from vendors like Coverity and GrammaTech. The standardization of software assurance objectives has influenced regulatory interactions among FAA, EASA, Civil Aviation Authority (United Kingdom), and national authorities in Canada and Australia, and has driven research collaborations with institutions such as MIT, Stanford University, Carnegie Mellon University, and NASA into topics like formal methods, model checking, and software verification applied to avionics programs like Space Shuttle upgrades and commercial transport programs.

Category:Avionics