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 10

PDF page 10 of 15

Enlarge original ↗

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

Original FAA AC 20-115D, PDF page 10
AC 20-115D · 10Open saved PDF here ↗
Extracted text for finding words

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

7/21/17                                                AC 20-115D


        (7)  If you want to use your existing processes to make modifications to your legacy
software using the version of ED-12( )/DO-178( ) (i.e., ED-12/DO-178, ED-12A/DO-178A, or
ED-12B/DO-178B) that was used for the original software approval, you may do so provided all
of the following conditions are met:

             (a)   If model-based development, object-oriented technology, or formal methods
will be used, existing processes incorporating these methods were evaluated and found to be
acceptable by the FAA on a previous certified project. These processes should have been
developed in accordance with the FAA guidance specific to the technique, such as that contained
in associated issue paper or published advisory circular.

             (b) You have maintained, and can still use, the software plans, processes, and life
cycle environment, including improvements to processes or to the life cycle environment as
captured in revised plans.

             (c)  You do not intend to declare the proposed software as having satisfied ED-
12C/DO-178C.

        (8)  If the conditions in subparagraph 9.b.(7) are satisfied:

             (a)  You may accomplish all modifications to the software using the same ED-12()/
DO-178( ) version as the original approval. However, you may not declare your software as
equivalent to satisfying ED-12C/DO-178C.

             (b)  If using configuration data, as defined under “Parameter Data Item” in ED-
12C/DO-178C, you may use existing processes for such data if the processes were evaluated and
found to be acceptable by the FAA on a previous project. In the absence of processes for using
configuration data, you should establish new processes for using parameter data items in
accordance with ED-12C/DO-178C.

        (9)  If any of the conditions in subparagraph 9.b.(7) are not satisfied, update all your
processes and procedures (including tool qualification processes), using ED-12C/DO-178C and
ED-215/DO-330, and make all modifications to the software using section 12.1 of ED-12C/DO-
178C.  If you want to declare your software as equivalent to satisfying ED-12C/DO-178C, your
declaration applies to both modified and unmodified software and is valid even if you use
unmodified tools that have not been qualified using ED-12C/DO-178C and ED-215/DO-330.
However, you cannot declare your unmodified tools as equivalent to having satisfied ED-
12C/DO-178C and ED-215/DO-330. All subsequent modifications to all your software and tools
are to be made using your processes and procedures that satisfy ED-12C/DO-178C and ED-
215/DO-330.

10. Tool Qualification. Section 12.2 of ED-12C/DO-178C, and ED-215/DO-330 provide an
acceptable method for tool qualification. ED-215/DO-330 contains its own complete set of
objectives, activities, and life cycle data for tool qualification.

    a.  If your legacy software was previously approved using ED-12/DO-178 or ED-12A/DO-
178A, and you intend to use a new or modified tool for modifications to the legacy software, use
the criteria of section 12.2 of ED-12C/DO-178C to determine if tool qualification is needed.  If


                                  10

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 →