Test Planning - Software Testing: Testing Across the Entire Software Development Life Cycle - page 90

begun, allowing the test team to follow the test plan and execute the test case
for preliminary construction.
Arrow 5 indicates that the development programming activities in fi nal
construction have begun, allowing the test team to follow the test plan and
execute the test case for fi nal construction.
Arrow 6 indicates that the new application has been installed and made
operational that is the starting point of post-implementation, allowing the test
team to follow the test plan and execute the test case for postimplementation.

•

•

5.5 TEST DOCUMENT STANDARDS

Because software testing is a professional branch of software engineering, you
expect to find standard software testing documentation templates. We intro-
duce to two of the industry-recognized standards sources for testing documen-
tation: the IEEE Computing Society and the Tigris Open Source SOFTWARE
Community.
The IEEE Computing Society was founded in 1884 as a merger of the American
Institute of Electrical Engineers (AIEE) and the Institute of Radio Engineers
(IRE). The full name of the current organization is the Institute for Electrical and
Electronics Engineers, Inc. Through its members, the IEEE is a leading authority
in technical areas ranging from computer engineering, biomedical technology, and
telecommunication to electric power, aerospace engineering, and consumer electron-
ics. The IEEE currently has more than 3,65,000 members worldwide, over 68,000
student members, 39 societies, and 1.1 million documents in the IEEE/IEE Elec-
tronic Library. IEEE document templates are available on the IEEE Web site for
subscribers only. [21]
The IEEE documentation standard #829-1998 for testing contains templates for

test plan
test design specifi cation
test case specifi cation
test procedure specifi cation
test log specifi cation
test incident report
test summary report

The test plan contents described in this textbook correspond somewhat to the IEEE
test plan, test design specifi cation, and test case specifi cation. The test case con-
tents described in this textbook cor respond somewhat to the IEEE test design specifi -
cation, test case specifi cation, and test procedure specifi cation. The textbook items
in the test case marked <Placeholder>correspond somewhat to the test log specifi ca-
tions, test incident report, and test summary report.