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 11

PDF page 11 of 15

Enlarge original ↗

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

Original FAA AC 20-115D, PDF page 11
AC 20-115D · 11Open 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


you need to qualify the tool, use the software level assigned by the system safety assessment for
determining the required Tool Qualification Level (TQL), and use ED-215/DO-330 for the
applicable objectives, activities, and life cycle data. You may declare your qualified tool as
having satisfied ED-215/DO-330 but not the legacy software as equivalent to having satisfied
ED-12C/DO-178C.

    b.  If your legacy software was previously approved using ED-12B/DO-178B, and you do
not intend to declare equivalence to satisfying ED-12C/DO-178C, you can either:

        (1) Use your ED-12B/DO-178B tool qualification processes for qualifying new or
modified tools in support of modifications to ED-12B/DO-178B legacy software, or

        (2) Update your tool qualification processes and qualify the tool using ED 215/DO-330;
use Table 2 of this document for determining the required TQL. You may then declare your
qualified tool as having satisfied ED-215/DO-330.

    c.  If your legacy software was previously approved using ED-12B/DO-178B, you intend to
declare equivalence to satisfying ED-12C/DO-178C, and you have ED-12B/DO-178B legacy
tools that need to be qualified, follow the guidance of this subparagraph.

        (1) ED-12C/DO-178C establishes five levels of tool qualification based on the tool use
and its potential impact in the software life cycle processes (see section 12.2.2 and Table 12-1 of
ED-12C/DO-178C). However, ED-12C/DO-178C does not address the use of tools previously
qualified to the ED-12B/DO-178B criteria. For a tool previously qualified as a ED-12B/DO-
178B development tool or verification tool, use Table 2 (below) to determine the correlation
between the ED-12B/DO-178B tool qualification type and ED-12C/DO-178C tool criteria and
tool qualification levels (TQLs).


      Table 2 - Correlation Between ED-12B/DO-178B Tool Qualification Type and
                   ED-12C/DO-178C Tool Criteria and TQL

                   ED-12B/                    ED-12C/     ED-12C/ED-215
                                  Software
               DO-178B Tool               DO-178C    DO-178C/DO-330
                                     Level
                 Qualification Type              Tool Criteria       TQL
                 Development       A           1            TQL-1

                 Development       B           1            TQL-2

                 Development       C           1            TQL-3

                 Development       D           1            TQL-4

                       Verification          A, B          2            TQL-4

                       Verification         C, D         2            TQL-5

                       Verification              All          3            TQL-5

        (2) Development Tools Previously Qualified Using ED-12B/DO-178B.




                                  11

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 →