Software Engineering

328
CHAPTER 19 
Software Implementation
 
and adheres to software design and coding standards. In addition, each unit 
design should be evaluated to determine if it provides a noncomplex and well-
documented solution that will facilitate post-development sustainment. These 
design walk-throughs or peer reviews can be performed for individuals or 
groups of related software units.
 3. 
Prepare software unit source code files
. The software implementation team 
edits the source code according to the unit programmatic design documenta-
tion. A source-coded editor should be used to facilitate code generation due to 
its ability to dynamically check the syntactic validity of instructions; it may 
provide interpretive execution and debugging.
 4. 
Prepare software problem reports
. Software problem reports should be gen-
erated whenever a software unit test procedure uncovers a defect. Software 
problem reports must be evaluated to determine the proper resolution, and 
tracked to ensure they are resolved. Software defects that can only be rectified 
by making adjustments to the software architecture should be submitted to the 
SWE-IPT as an ECR.
 5. 
Prepare software unit test scenarios
. The software unit test scenarios and pro-
cedures should be developed and documented in the software development 
folder.
 6. 
Code software units
. The software implementation team generates the code for 
each software unit according to the unit programmatic design documentation.
 7. 
Test software units
. The software implementation team tests each software unit 
to ensure that it performs as expected, and achieves the software unit speci-
fications. The results should be documented in the software unit test report. 
Deficiencies identified during unit testing may be resolved, if possible, by 
modifying the programmatic design and fixing the source code appropriately. 
Software problem reports must be generated to document identified deficien-
cies that stem from the structural unit specifications.
 8. 
Prepare software unit test report
. The results of the software unit testing 
should be documented in the software unit test report and captured in the 
software unit SDF. The software unit test report should identify every error 
encountered during testing, and identify the software problem reports that were 
generated to document the deficiencies.
 9. 
Resolve identified deficiencies
. As software unit testing identifies deficiencies, 
the software unit must be redesigned and its code updated to reflect the correc-
tive action. The software development folder should be updated to preserve test 
results and properly reflect the “as-implemented” software unit design. The 
modified software unit is retested to ensure that the modifications did resolve 
the problem reports and did not introduce any additional problems.
10. 
Place software units under configuration control
. Once a software unit has 
satisfied its unit test procedures the code should be captured in the software 
library and placed under configuration control.
11. 
Prepare software component integration and test procedures
. The software 
component integration and test procedures should be prepared and captured 
in the component SDF. Software component test procedures should not repeat 

---