Software Engineering

20.3 
 Software implementation organization (software 
acceptance testing stage)
1. 
Monitor software acceptance testing.
 Representatives of the software 
implementation organization should witness the conduct of acceptance testing 
to provide insight into software behaviors and responses to test scenarios and 
conditions.
2. 
Evaluate software problem reports.
 The software implementation organization 
must determine the corrective action to be taken to resolve problems that arise 
during acceptance testing. Software problem reports generated as a result of 
acceptance testing should be evaluated to determine if they stem from software 
implementation defects. If necessary, a problem may be elevated to the SWE-
IPT to be resolved by modifying the software architecture or pursuing a devia-
tion or waiver.
3. 
Deliver the final software executables.
 The final software executables should be 
generated and delivered to the project configuration management organization 
to support the software replication process and software configuration audits.
4. 
Deliver the final software source files.
 The final set of source code files should 
be prepared to provide a basis for software problem isolation and resolution. 
The source code files also provide a basis for implementing future extensions 
and enhancement to the software product baseline.
5. 
Deliver the software build procedures.
 The final software build procedures should 
be prepared and delivered to the project configuration management organization 
to facilitate the software replication process. The software build procedures will 
be utilized by the software replication team to generate distribution media and 
accommodate patching and releasing future versions of the software product.
6. 
Support the software configuration audits.
 Representatives of the software 
implementation organization should participate in the conduct of software FCAs 
and PCAs.

---