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 7

PDF page 7 of 15

Enlarge original ↗

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

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

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

7/21/17                                                AC 20-115D


                    Figure 1 - Legacy Software Process Flow Chart



       Intent to use software
        previously shown to
     satisfy DO-178, DO-178A,                                                            Conduct
            or DO-178B                                                      Change Impact Analysis
                                                                            See 9.b(4)


     Evaluate software usage
     history, SDs, ADs, OPRs,
                  etc.
                                                                                                                   Will                        Determine tool         See 9.b.(1)
                                                                                             there be new software     Yes          qualification
                                                                                                  tools or changes to tools?                requirements.
                                                                           See 9.b.(5)                 See paragraph 10.

                                           Correct process
                 Is the                         deficiencies and
      software usage history   No      document plan for                            No
           acceptable?                     resolving related
         See 9.b.(1)                  software deficiencies.
                                   See 9.b.(1)                                       Did you
                                                                                     upgrade the         Yes        Yes
                                                                                           software baseline to
                                                                     DO-178C IAW paragraph
                                                                                                          9.b.(2)(a),(b),or(c)?
                                                                           See 9.b.(6)
                 Is the
       software developed    No                                              No
         using DO-178B?
         See 9.b.(2)

                                                                                                                                                                    If MBD,
                                                                        OOT, or FM will       No        Yes
                                                                            be used, do processes
                                                                                       support the technique IAW
                                                                                              applicable guidance?
                                                                          See 9.b.(7)(a)
                 Is the                                        Is the
          DO-178B                        DO-178 or       Yes                         Yes
          software level                DO-178A software level                                                                              Yes
           acceptable?                          acceptable?
         See 9.b.(2)                      See 9.b.(2)

                                                                               Have
         No                           No                                       the software plans       No
                                                                            and environment been
                                                                                              properly maintained?    Upgrade software baseline
                                     Upgrade software baseline                     See 9.b.(7)(b)     including all processes &
                                               including all processes &
    procedures using DO-178B
                                        procedures using DO-178C
       or use DO-178C and                                          and DO-330.                            Yes
           DO-330.
                                    See 9.b.(2)(a) or (b)
        See 9.b.(2)(c)


                                                                      Do you want
                                                                                                    to declare equivalence to    Yes
                                                                           DO-178C?
                                                                           See 9.b.(7)(c)


                                                                       No                    Upgrade software baseline
                   Is                                                                                                                  including all processes &
        the legacy system                          Yes                                                                                 procedures using DO-178C
          software to be                                                                                         and DO-330.
            modified?                                                                                      See 9.b.(9)
         See 9.b.(3)
                                                                         Change software and
                                              Acronyms                      associated life cycle data using
         No                    ADs – Airworthiness Directives               the same DO-178( ) version as
                           FM – Formal Methods                          the original approval. For
                               IAW – In Accordance With                      configuration data / PDI, use
                                                                                                     Change                                                                                                                                    software                                                                                                                        and                                                                              approved                                                                                          process                                                                                                              or                                                                                                                  establish                                        –                                           Model-Based                                                      Development     Original            approval                     basis                            or        MBD                                                                                                                       associated                                                                                                                                                                                                 life                                                                                                                                           cycle                                                                                                                                       data                                                                                                                                              using                                                                   new process                                                                                                 using                                                                                        DO-178C.                           OOT                                        –                                                Object                                                      Oriented                                                          Technology   baseline          upgrade                      to                 DO-178C                                                                                                      DO-178C,                                                                                                                                  Section                                                                                                                                                    12.1,                                                                                                                           and                                                                        See 9.b.(8)(a)                                                                          &                                                                                                                            (b)                              OPRs                                         –                                      Open                                                 Problem                                                            Reports   acceptable            as approval                           basis.                                                                                                                                 applicable                                                                                                                               supplements.                                   PDI                                       –                                           Parameter                                                    Data                                                             Item      See             9.b.(3)(a)                      or                           (b)                                                                                                     See                                                                                                                                                      9.b.(6)                                                                                                  &                                                                                                                                                                  (9)                               SDs                                       –                                                Service                                                                     Difficulties


     Note: References to EUROCAE documents are intentionally omitted for formatting purposes.





                                   7

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 →