International (civil aviation; FAA, EASA and other authorities)

DO-178C / ED-12C

77 controls. 5 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

77 controls 5 frameworks share controls with it International (civil aviation; FAA, EASA and other authorities) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
10Overview of certification process0
11Software life cycle data0
12Additional considerations0
2System aspects relating to software development0
3Software life cycle0
A-1.1Activities of every life cycle process set out in the plans3
A-1.2Life cycle model fixed: process interactions, order, feedback and transition criteria3
A-1.3Development and verification environment chosen and documented2
A-1.4Section 12 topics and other special considerations dealt with in planning2
A-1.5Requirements, design and code standards established4
A-1.6Plans shown to conform to DO-178C for the assigned level1
A-1.7Plans produced and changed in a coordinated way1
A-10.1Applicant and certification authority communicate and understand each other0
A-10.2Means of compliance proposed and PSAC agreed with the authority2
A-10.3Evidence of compliance supplied to the authority2
A-2.1High-level software requirements produced from the allocated system requirements3
A-2.2Derived high-level requirements identified and passed to the system and safety processes3
A-2.3Software architecture produced2
A-2.4Low-level requirements produced1
A-2.5Derived low-level requirements identified and passed to the system and safety processes1
A-2.6Source code written from the low-level requirements and architecture2
A-2.7Executable object code and any parameter data item files built and loaded on the target2
A-3.1High-level requirements satisfy the system requirements allocated to software2
A-3.2High-level requirements precise and free of conflict2
A-3.3High-level requirements fit the target hardware0
A-3.4High-level requirements testable or otherwise verifiable2
A-3.5High-level requirements follow the requirements standards0
A-3.6High-level requirements traced to system requirements2
A-3.7Algorithms in the high-level requirements are correct0
A-4.1Low-level requirements satisfy the high-level requirements1
A-4.10Architecture fits the target hardware0
A-4.11Architecture verifiable0
A-4.12Architecture follows the design standards0
A-4.13Partition breaches shown to be prevented2
A-4.2Low-level requirements precise and free of conflict0
A-4.3Low-level requirements fit the target hardware0
A-4.4Low-level requirements verifiable0
A-4.5Low-level requirements follow the design standards0
A-4.6Low-level requirements traced to high-level requirements0
A-4.7Algorithms in the low-level requirements are correct0
A-4.8Architecture does not conflict with the high-level requirements1
A-4.9Architecture internally coherent0
A-5.1Source code implements the low-level requirements1
A-5.2Source code matches the architecture0
A-5.3Source code verifiable0
A-5.4Source code follows the code standards1
A-5.5Source code traced to low-level requirements1
A-5.6Source code free of accuracy and consistency defects1
A-5.7Integration outputs checked as complete and correct1
A-5.8Parameter data item file content correct and complete1
A-5.9Parameter data item file verification demonstrated1
A-6.1Executable object code meets the high-level requirements2
A-6.2Executable object code robust against the high-level requirements2
A-6.3Executable object code meets the low-level requirements0
A-6.4Executable object code robust against the low-level requirements0
A-6.5Executable object code works on the target computer1
A-7.1Test procedures checked as correct2
A-7.2Test results checked and every discrepancy explained2
A-7.3Tests cover every high-level requirement3
A-7.4Tests cover every low-level requirement0
A-7.5Structural coverage by modified condition/decision coverage (level A)0
A-7.6Structural coverage by decision coverage (levels A and B)1
A-7.7Structural coverage by statement coverage (levels A to C)2
A-7.8Data coupling and control coupling exercised by the tests0
A-7.9Compiler-generated code not traceable to source verified (level A)0
A-8.1Configuration items identified2
A-8.2Baselines set and traceability kept1
A-8.3Problem reporting, change control, change review and status accounting in place4
A-8.4Archiving, retrieval and release in place2
A-8.5Software load control in place1
A-8.6Life cycle environment under control1
A-9.1Quality assurance confirms plans and standards were produced and reviewed for conformity and consistency1
A-9.2Quality assurance confirms the processes follow the approved plans3
A-9.3Quality assurance confirms the processes follow the approved standards0
A-9.4Quality assurance confirms transition criteria are met0
A-9.5Quality assurance confirms the software conformity review is held1
REGRecognition, supporting documents and regulator material around DO-178C0

Tell me when DO-178C / ED-12C files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for DO-178C / ED-12C, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition