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

PDF page 1

PDF page 1 of 15

Enlarge original ↗

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

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

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

            AdvisoryU.S. Department
of TransportationFederal Aviation        Circular
Administration

Subject: Airborne Software Development       Date: 07/21/2017     AC No: 20-115D
Assurance Using EUROCAE ED-12( ) and       Initiated by: AIR-134   Change:
RTCA DO-178( )

1.  Purpose of this Advisory Circular (AC).

    a.  This AC describes an acceptable means, but not the only means, for showing compliance
with the applicable airworthiness regulations for the software aspects of airborne systems and
equipment in type certification or TSO authorization. This AC is not mandatory and does not
constitute a regulation. However, if you use the means described in the AC, you must follow it
in all applicable respects.

    b.  This AC recognizes the following current EUROCAE and RTCA, Inc. documents:

        (1) EUROCAE ED-12C, Software Considerations in Airborne Systems and Equipment
Certification, dated January 2012, and RTCA DO-178C, Software Considerations in Airborne
Systems and Equipment Certification, dated December 13, 2011.

        (2) EUROCAE ED-215, Software Tool Qualification Considerations, dated January
2012, and RTCA DO-330, Software Tool Qualification Considerations, dated December 13,
2011.

        (3) EUROCAE ED-218, Model-Based Development and Verification Supplement to ED-
12C and ED-109A, dated January 2012, and RTCA DO-331, Model-Based Development and
Verification Supplement to DO-178C and DO-278A, dated December 13, 2011.

        (4) EUROCAE ED-217, Object-Oriented Technology and Related Techniques
Supplement to ED-12C and ED-109A, dated January 2012, and RTCA DO-332, Object-Oriented
Technology and Related Techniques Supplement to DO-178C and DO-278A, dated December
13, 2011.

        (5) EUROCAE ED-216, Formal Methods Supplement to ED-12C and ED-109A, dated
January 2012 and RTCA DO-333, Formal Methods Supplement to DO-178C and DO-278A,
dated December 13, 2011.
          Note: EUROCAE ED is hereafter referred to as ED; RTCA DO is hereafter referred
to as DO. Where the notation ED-XXX/DO-XXX appears in this document, the referenced
documents are recognized as being equivalent.




                                   1

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 →