By Topic

829-2008  -  IEEE Standard for Software and System Test Documentation - Redline

Revision of IEEE Std 829-1998
StatusInactive  -  Redline

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

This document is only available as part of a bundle
Options Non-Member Member
$149.0 $121.0
IEEE Standard for Software and System Test Documentation - RedlineView Bundle Details

Bundle Details

IEEE Standard for Software and System Test Documentation - Redline

This bundle includes the following items:
  • 829-2008 selected IEEE Standard for Software and System Test Documentation - Redline
  • 829-2008 IEEE Standard for Software and System Test Documentation
Non Member: $149.0 Member: $121.0
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

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, commercial off-the-shelf, 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.

Scope
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.
Purpose
The purpose of this standard is to:- Establish a common framework for test processes, activities, and tasks in support of all softwarelife cycle processes, including acquisition, supply, development, operation, and maintenanceprocesses- Define the test tasks, required inputs, and required outputs- Identify the recommended minimum test tasks corresponding to integrity levels for a four-levelintegrity 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., forcomponent, integration, system, and acceptance test)- Define the use and contents of related test documentation (Test Design, Test Case, TestProcedure, Anomaly Report, Test Log, Level Test Report, Interim Test Report, and Master TestReport)