DO-178C demystified: Strategies for efficient certification

Background

If you're working towards DO-178C certification, you're probably juggling far more than software development. Traceability, testing, structural coverage, tool qualification, multicore processors, and certification evidence all demand time, effort, and expertise. The good news is that DO-178C is not as daunting as it can sometimes appear – and once you understand the process and the objectives behind it, certification becomes far more manageable. This guide explains the key concepts behind DO-178C, explores the technologies and workflows used on successful projects, and shows how modern verification, target analysis, debugging, and trace technologies can help reduce effort and risk.

Before diving into the details, it's worth understanding where DO-178C fits within the broader airborne systems development landscape.

DO-178C in context

DO-178C does not exist in isolation. It forms part of a broader framework of aerospace standards and guidance covering aircraft systems, safety assessment, hardware, and software. Although technically guidance rather than a standard, DO-178C is generally treated as one by the aerospace community - as will we.

At the system level, ARP4754B defines the processes used to develop and certify aircraft systems, while ARP4761A provides guidance on safety assessment and failure analysis. Together, they determine the level of assurance required for the hardware and software that implement those systems.

Within that framework, DO-178C provides guidance for airborne software development and verification, while DO-254 addresses airborne electronic hardware. Other standards and guidance documents address specific technologies and challenges, including integrated modular avionics (IMA), multicore processors, model-based development, object-oriented technologies, and formal methods.

Download Link 1790673526-DO-178C-demystified-strategies-for-efficient-certification.pdf