FAA / Advisory circular

AC 20-115D

Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( )

Software development assurance, recognised standards and the treatment of new development and previously approved software.

Start with the scope.

This AC recognises DO-178C/ED-12C, DO-330/ED-215 and the model-based, object-oriented and formal-methods supplements. Apply the relevant provisions to the software and certification context.

The source, within reach.

Search within this AC, jump to a source page, or download the complete saved publication.

Download saved FAA PDF ↓

Read the source

The document, within reach.

FAA source document

Printed page 4

PDF page 4 of 15

Enlarge original ↗

Original FAA page; extracted words support search. Text reflow has not been reviewed.

Original FAA AC 20-115D, PDF page 4
Extracted text for finding words

This extraction supports search. Read the original page for complete notation and layout.

7/21/17                                                AC 20-115D


    b. You should submit the life cycle data specified in section 9.3 of ED-12C/DO-178C and
section 9.0.a of ED-215/DO-330, as applicable for tool qualification, to the appropriate project
certification office.  It is your responsibility to perform the planned activities and produce the life
cycle data necessary to satisfy all applicable objectives.

    c.  Section 9.4 of ED-12C/DO-178C specifies the software life cycle data related to the type
design of the certified product. However, not all of the specified data applies to all software
levels; specifically Design Description and Source Code are not part of the type design data for
Level D.

    d. You should make available to us, upon request, any of the data described in section 11 of
ED-12C/DO-178C, applicable tool qualification data, data outputs from any applicable
supplements, and any other data needed to substantiate satisfaction of all applicable objectives.

    e.  The FAA may publish an acceptable means of compliance for specific regulations,
stating the required relationship between the criticality of the software-based systems and the
software levels as defined in ED-12C/DO-178C. Such acceptable means of compliance will take
precedence over the application of section 2.3 of ED-12C/DO-178C.

7.  Reserved.

8. Guidance applicable to ED-12B/DO-178B or ED-12C/DO-178C.

    a. Use of Supplements with ED-12C/DO-178C. You should apply the guidance of
supplements ED-218/DO-331, ED-217/DO-332, and ED-216/DO-333 when incorporating the
addressed software development techniques.  If you intend to use multiple software development
techniques together, more than one supplement applies. You cannot use supplements as stand-
alone documents.

        (1) When using one or more supplements, your Plan for Software Aspects of
Certification (PSAC) should describe:

             (a) How you will apply ED-12C/DO-178C and the supplement(s) together.

             (b) How you will address the applicable ED-12C/DO-178C objectives and those
added or modified by the supplement(s), which objectives from which documents apply to which
software components, and how your planned activities will satisfy all the applicable objectives.

        (2)  If you intend to use any techniques addressed by the supplements to develop a
qualified tool, (for tool qualification levels (TQLs) 1, 2, 3, and 4 only), then the Tool
Qualification Plan should describe:

             (a)  Based on supplement analysis, which tool qualification objectives are impacted
by the use of the technique(s).

             (b) How the planned activities will satisfy the added or modified objectives.




                                   4

Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.

Aerospace Consulting / Engineering perspective

Keep software assurance connected to the system.

Make the software level, allocated requirements, interface assumptions and verification responsibilities explicit. Plan the evidence and review points early, and trace changes back to the system safety and certification assumptions.

Explore our development assurance approach →
Source edition and reading coverage

15 original pages. 0 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.

Source SHA-256: 5597a1af49c872a1a843c05601742ddcc8e8a190642f31e3cb9ce8e0dc63d91e

This is a dated source copy. Automatic source acquisition is not yet scheduled.

Original FAA PDF ↗

Working through a certification question?

Bring the aircraft, the basis and the issue your team needs to resolve.

Discuss your programme →