IEEE 829:2008

Revision Standard - Superseded.
Test processes determine whether the development products of a given activity conform to the requirements of that activity and whether the system and/or software satisfies its intended use and user needs. Testing process tasks are specified for different integrity levels. These process tasks determine the appropriate breadth and depth of test documentation. The documentation elements for each type of test documentation can then be selected. The scope of testing encompasses software-based systems, computer software, hardware and their interfaces. This standard applies to software-based systems being developed, maintained, or reused (legacy, COTS, Non-Developmental Items). The term software also includes firmware, microcode and documentation. Test processes can include inspection, analysis, demonstration, verification and validation of software and software-based system products. (IEEE 829-2008 is superseded by ISO/IEC/IEEE 29119-1-2013, ISO/IEC/IEEE 29119-2-2013, ISO/IEC/IEEE 29119-3-2013 and ISO/IEC/IEEE 29119-4-2015. )

This standard applies to all software-based systems. It applies to systems and software being developed, acquired, operated, maintained, and/or reused [e.g., legacy, modified, Commercial-Off-the-Shelf (COTS), Government-Off-the-Shelf (GOTS), or Non-Developmental Items (NDIs)]. When conducting the test process, it is important to examine the software in its interactions with the other parts of the system. This standard identifies the system considerations that test processes and tasks address in determining system and software correctness and other attributes (e.g., completeness, accuracy, consistency, and testability), and the applicable resultant test documentation.
The purpose of this standard is to:
- Establish a common framework for test processes, activities, and tasks in support of all software life cycle processes, including acquisition, supply, development, operation, and maintenance processes
- Define the test tasks, required inputs, and required outputs
- Identify the recommended minimum test tasks corresponding to integrity levels for a four-level integrity scheme (see the used example in 4.1)
- Define the use and contents of the Master Test Plan and the Level Test Plan(s) (e.g., for component, integration, system, and acceptance test)
- Define the use and contents of related test documentation (Test Design, Test Case, Test Procedure, Anomaly Report, Test Log, Level Test Report, Interim Test Report, and Master Test Report)