FAA / Advisory circular

AC 20-152A

Development Assurance for Airborne Electronic Hardware

Development assurance for custom airborne hardware, COTS devices, COTS IP and circuit board assemblies.

Start with the scope.

This AC recognises DO-254/ED-80 and adds objectives for distinct hardware categories. Its stated applicability covers hardware contributing to DAL A, B and C functions; the relevant objective restrictions still apply.

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 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

         Objective CD-10
       When the applicant intends to independently assess a tool output, the applicant should
        propose an independent assessment that verifies the tool output is correct. The
        independent assessment should justify that there is sufficient coverage of the tool
         output. The completeness of the tool assessment should be based on the
         design/implementation and/or verification objectives that the tool is used to satisfy.

       ED-80/DO-254 - Figure 11-1, Item 4. - Is the Tool a Level A, B or C Design Tool or
        a Level A or B Verification Tool?
        ED-80/DO-254, Figure 11-1, Item 4 of the tool assessment/qualification flow excludes
         the need for activities for tools “used to assess the completion of verification testing,
        such as in an elemental analysis.”
       The last statement is misleading regarding the intent of code coverage tools used for
         elemental analysis. As stated in Section 5.7 of this document: when a code coverage
          tool is used for elemental analysis, it does not represent an assessment of the
        completeness of the requirements-based testing activities or the effectiveness of the
         requirement coverage.
            It is therefore necessary to provide some further clarifications.
        •  This document recognizes the Figure 11-1, Item 4 exclusion of tool
             assessment/qualification activities for code coverage tools only when they are used
             to assess whether the code has been exercised by requirements-based
             testing/simulations (elemental analysis).
        •   If test cases or procedures are automatically generated by a tool and this tool uses
            coverage to determine the completion of the requirements verification, then the tool
            should be considered to be a verification tool to answer the question raised in
            Figure 11-1, Item 4.
       ED-80/DO-254 - Figure 11-1, Item 5. - Does the Tool have Relevant History?
         In ED-80/DO-254, the supporting text for Figure 11-1, Item 5 can be misinterpreted to
         suggest that when the tool has been previously used, no further tool assessment is
         necessary. Item 5 should be understood to mean that the applicant will provide
          sufficient data and justification to substantiate the relevance and credibility of the tool
          history.

         Objective CD-11
       When the applicant intends to claim credit for the relevant history of a tool, sufficient
        data should be provided as a part of the tool assessment to demonstrate that there is a
         relevant and credible tool history to justify that the tool will produce correct results for
            its proposed use.

       ED-80/DO-254 - Figure 11-1, Item 9. – Design Tool Qualification
        For design tools, contrary to the note in the supporting text for Figure 11-1, Item 9, the
          tool history should not be used as a stand-alone means of tool assessment and
          qualification. A relevant tool history may be used to compensate for some particular

                                         10

Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.

Aerospace Consulting / Engineering perspective

Define the hardware assurance approach by function and device.

Use the PHAC to identify intended functions, assurance levels, custom and COTS boundaries, and the evidence needed for each applicable objective. Keep supplier information, integration verification and system-level assumptions connected.

Discuss the system and hardware assurance approach →
Source edition and reading coverage

31 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: 06b17bec98562261063d87e518df3fe581412a5dce64b39ef4769c57433b6bc6

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 →