Software Engineering

324
CHAPTER 19 
Software Implementation
their correctness. This assembly, integration, and testing series of events continues 
to generate larger, more complex software components. Software integration pro-
gresses until a completely integrated and tested software configuration item is real-
ized and available for acceptance testing. The software implementation stage is 
shown in 
Figure 19.1
.
Software implementation includes the dry-run of the software acceptance test-
ing. This dry-run exercise is intended to ensure that the acceptance test procedures 
are effective and the software product performs according to software specifica-
tions. A dry-run provides a demonstration of the software product’s readiness for 
acceptance testing. Acceptance testing represents a formal demonstration to stake-
holders that the software development effort has achieved its objectives. If the tests 
are successful, the software product is deemed to be ready for distribution and post-
development sustainment. The act of declaring the acceptance testing successful is 
the first step in transitioning from the software development project to deployment 
and post-development operations. Additional projects may be initiated to provide 
software post-development process operations and provide preplanned product 
improvement through an incremental or spiral approach. Alternatively, the software 
development project may simply transition into the post-development stage of the 
software life cycle.
Software deficiencies identified within the software implementation stage must 
be resolved. Those deficiencies that are determined to be the result of architectural 
flaws must be documented in architectural problem reports. The software engineer-
ing integrated product team (SWE-IPT) must be responsible for resolving architec-
tural deficiencies and repairing the architectural artifacts. Other deficiencies may 
be discovered that stem from programmatic design or coding mistakes. However, 
those software problem reports are the responsibility of the software implemen-
tation organization to resolve. The software implementation team should not be 
allowed to deviate from the software TDP. Software architectural deficiencies must 
be resolved by the SWE-IPT. Architectural problem reports should be generated by 
software implementation personnel to document perceived software deficiencies 
that stem from the software TDP.
An acceptance testing dry-run is conducted to ensure that the software product 
can successfully pass acceptance testing while running on the specified computing