Cart 0 Product Products (empty)
No products
To be determined Shipping
$0.00 Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart. There is 1 item in your cart.
Total products
Total shipping To be determined
Total
New Sale! 
View larger
View larger RTCA DO-330
New product
RTCA DO-330 2011 Edition, December 13, 2011 Software Tool Qualification Considerations
More info
Description / Abstract: 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 provides software tool qualification guidance. Additionally, clarification material is provided in the form of Frequently Asked Questions (FAQs). The document was developed for the following reasons:
• 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.
• 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 DO-178C or DO-278A). This tool-specific document benefits tool development teams and helps them avoid confusion and misinterpretation.
• It 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.
This document provides software tool qualification guidance. Additionally, clarification material is provided in the form of Frequently Asked Questions (FAQs). The document was developed for the following reasons:
• 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.
• 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 DO-178C or DO-278A). This tool-specific document benefits tool development teams and helps them avoid confusion and misinterpretation.
• It 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.