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 9

PDF page 9 of 15

Enlarge original ↗

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

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

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

7/21/17                                                AC 20-115D


processes and procedures (including tool qualification processes), using section 12.1.4 of ED-
12C/DO-178C, and ED-215/DO-330.

             (c)   If your legacy software was developed using ED-12B/DO-178B, and the
software level is not acceptable, upgrade the software development baseline, including all
processes and procedures (including tool qualification processes), using section 12.1.4 of ED-
12B/DO-178B or ED-12C/DO-178C and ED-215/DO-330.

        (3)  If the criteria in subparagraphs 9(b)(1) and 9(b)(2) are satisfied and modifications to
the software are not required, then:

             (a)  The original approval may serve as the basis for the software in the installation
approval of the proposed system.

             (b)  If you upgraded the software development baseline using ED-12C/DO-178C
and updated all processes and procedures, including tool qualification processes, to ED-12C/DO-
178C and ED-215/DO-330, then you may declare your software as equivalent to satisfying ED-
12C/DO-178C. 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.

        (4)  If modifications to the software are required, conduct a software change impact
analysis (CIA) to determine the extent of the modifications, the impact of those modifications,
and what verification is required to ensure that the modified software performs its intended
function and continues to satisfy the identified means of compliance.

             (a)  Identify the software changes to be incorporated and perform a CIA consisting
of one or more analyses associated with the software change as identified in section 12.1of ED-
12C/DO-178C;

             (b)  Conduct the verification as indicated by the CIA; and

             (c)  Summarize the results of the CIA in the Plan for Software Aspects of
Certification (PSAC) or in the Software Accomplishment Summary (SAS).

        (5)  If new software tools or modifications to tools are needed, refer to paragraph 10 of
this AC to determine tool qualification requirements.

        (6)  If you upgraded the software baseline to ED-12C/DO-178C in accordance with
subparagraph 9.b.(2), 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
equivalence 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. 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.



                                   9

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 →