Aviation software must pass a demanding standard, DO-178C, before it can fly

Aviation software must pass a demanding standard, DO-178C, before it can fly
Image: Intellect (generated)

In short: Commercial aircraft depend on software, so that software must be approved before it is trusted in the air. Authorities such as the FAA, EASA and Transport Canada rely on one principal reference for this approval, known as DO-178C. It ties the amount of scrutiny to how serious a failure could be.

DO-178C is the main reference that aviation authorities use to approve commercial aerospace systems built on software. Its formal title refers to considerations for software in airborne systems and equipment certification. It is published by RTCA together with EUROCAE and succeeds the earlier DO-178B. The revision was completed in November 2011, approved a month later, and became available for sale and use in January 2012. In 2017 the FAA accepted it as one acceptable way, though not the only way, to show compliance with its software rules.

The central idea is that scrutiny follows consequence. Safety assessment and hazard analysis examine what a failure would do to the aircraft, its crew and its passengers. Failures range from catastrophic, which may cause deaths and usually the loss of the aircraft, down to those with no effect at all. The result sets a software level, also called a development assurance level, graded from A to E. Software that commands, controls or monitors safety-critical functions should receive the highest level, A, and the level decides how many objectives must be met.

Some of those objectives require independence, meaning the person verifying an item may not be the person who wrote it, and this separation must be clearly documented. The standard is objective-based rather than prescriptive. It says what must be shown, and each project plans the activities that will show it. This flexibility is useful, yet it makes a first project under the standard hard to set up. Traceability links requirements, code and tests so that reviewers can check that every requirement is implemented and verified.

The 2011 revision was an update rather than a rewrite, and much of the earlier wording was kept. Some ambiguity about low-level requirements may remain. Tool qualification moved into DO-330, a domain-independent document also usable beyond aviation. Supplements cover model-based development, object-oriented techniques and formal methods, the last intended to complement testing rather than replace it. The standard itself notes that following it does not alone guarantee software safety, which must be shown through separate system-level work.

Opens the Intellect+ feed with this card first. Swipe up for the next one.

Sources

  • Summary by Intellect · source: DO-178C

To cite this card, link to https://intellectplus.co.uk/app/technology-do-178c.

How we source, check and correct cards: Editorial standards.

General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.

Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?

Related

Finding something worth knowing…