Software Engineering

20.4
  Computing environment implementation organization  
(software acceptance testing stage) ................................................................ 339
20.5
  Post-development process organization (software acceptance  
testing stage) ................................................................................................. 339
20.6
  Software test and evaluation (software acceptance testing stage) ..................... 339
20.7
  Reviews and milestones (software acceptance testing stage) ........................... 340
20.8
  Establish the software product baseline ........................................................... 341
Acceptance testing is the formal testing activity that involves enterprise, customer, 
and stakeholder representatives to witness the readiness of the software product to 
be deployed. If a contract was the genesis for the software development program, 
then this activity represents a significant step in demonstrating that the software 
development program has fulfilled its contractual obligations. If the project was 
funded by internal enterprise resources, then this activity provides proof that the 
program requirements have been satisfied and the product is ready for deployment. 
Such products may be distributed internally in support of business processes or they 
may be marketed as consumer software packages.
Prior to software deployment, the software configuration items must be subjected 
to a final examination to ensure that the software data packages are complete. The 
architecture technical data package (TDP) must be audited to ensure that it accurately 
reflects the “as-built and tested” software configuration. The functional configuration 
audit (FCA) inspects software test results to ensure that the software product satisfies 
its specifications, as augmented by change proposals. The physical configuration audit 
(PCA) inspects the definitive software deployment data package (DDP) to ensure that 
the as-built and tested software configuration is properly reflected in its documenta-
tion set. These configuration audits should be performed to establish the uniformity of 
the software product configuration to the architectural and configuration DDPs.
A deployment readiness review (DRR) should be conducted to present the 
results of acceptance testing, software configuration audits, and the status of each of 

---