Software Engineering

336
CHAPTER 20 
Software Acceptance Testing 
the post-development processes. The DRR is intended to ensure that the processes 
for software replication, distribution, training, and sustainment are operationally 
prepared to bolster customer and stakeholder demands to software product training 
and problem resolution. 
Figure 20.1
 depicts the products of the acceptance testing 
stage of software development.
20.1 
Products of software acceptance testing
1. 
Acceptance test report.
 This report summarizes the results of software accept-
ance testing. It should provide the traceability to software problem reports 
generated to the software components and units of which the behavior did not 
satisfy the test procedure. Acceptance testing confirms that the software product 
(software configuration items and computing environment) satisfies the software 
specifications.
2. 
Software problem reports.
 Software problem reports should be generated for 
every discrepancy found during acceptance testing. The priority level, risks, 
workarounds, and resolution alternatives should be identified so the proper reso-
lution alternative can be identified that will permit software deployment at the 
soonest opportunity. If dry-run testing was conducted, then there should not be 
any new software problem reports generated during acceptance testing.
3. 
Software deviations and waivers.
 Deviations and waivers should be generated 
for deficiencies in the software product that conflict with the software specifica-
tions. Deviations represent nonconformity of the software product with software 
specifications. Deviations represent acknowledgment of these situations, and 
request authorization to proceed to deploy the software product in its current