Standard Details
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.
Standards Committee | |
Status |
Superseded
|
Board Approval |
2008-03-27
|
History |
Published Date:2008-07-18
|
Additional Resources Details
PAR |
Working Group Details
Working Group |
829_WG - Std for Software Test Documentation Working Group
|
Working Group Chair |
Claire Lohr
|
Standards Committee | |
Society | |
IEEE Program Manager | |
Existing Standards |
A set of basic test documents that are associated with the dynamic aspects of software testing (that is, the execution of procedures and code) is described. The purpose, outline, and content of each basic document are defined. Although the documents described in the standard focus on dynamic testing, several of them may be applicable to other testing activities. Documentation on electronic media as well as paper is covered. The standard does not call for specific testing methodologies, approaches, techniques, facilities, or tools, and does not specify the documentation of their use. It also does not imply or impose specific methodologies for documentation control, configuration management, or quality assurance.
|
Superseded by IEEE Std 829-2008. A set of basic software test documents is described. This standard speci?es the form and content of individual test documents. It does not specify the required set of test documents.
|