scope:

Software tools are widely used in multiple domains, to assist in developing, verifying, and controlling other software. In the context of this document a tool is a computer program or a functional part thereof, used to help develop, transform, test, analyze, produce, or modify another program, its data, or its documentation. Examples are automated code generators, compilers, test tools, and modification management tools. This document explains the process and objectives for qualifying tools.

This document was developed for the following reasons:

a. Tools are different from the software using the tools and form a unique domain; therefore, tool-specific guidance for both tool developers and tool users is needed.

b. Tools are often developed by teams other than those who use the tools to develop software. These tool development teams frequently do not have software guidance background (examples of guidance include ED-12C or ED- 109A). This tool-specific document benefits tool development teams and helps them avoid confusion and misinterpretation.

c. This document provides guidance for airborne and ground-based software. It may also be used by other domains, such as automotive, space, systems, electronic hardware, aeronautical databases, and safety assessment processes.

PURPOSE

The purpose of this document is to provide tool qualification guidance. Additionally, clarification material is provided in the form of Frequently Asked Questions (FAQs).