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.
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.
A focused review, an agreed assessment package or ongoing support alongside your team. We can agree the relevant inputs and scope in the initial conversation.
This opens your email application.
Start a conversation
Tell us about your programme, the system you are developing and the support you need.
We can agree a focused use-case review, a defined evidence package or ongoing programme support.
This opens your email application.
Specialist aerospace expertise
Aerospace Consulting is led by Hussein Khimji, an FAA Designated Engineering Representative in systems and equipment, with a focus on system safety, flight controls and avionics.
We work with aircraft developers and systems suppliers to connect technical decisions, safety assessments and certification evidence.
This is the proposed introduction. The full About page will add your approved biography and associate expertise.
Systems engineering & development assurance
Tell us about the aircraft or system, its intended function, stage of development and the support you need.