Software Engineering

16.5.2 
Maintain change history repository
The software change history repository is intended to capture the history of every 
change request and proposal entertained by the software engineering team. It 
should capture the change request or proposal content, change evaluation material, 
CCB determination results, change notification package, and change assimilation 
audits.
16.5.3 
Maintain technical risk repository
The technical risk repository is intended to capture every risk acknowledged by the 
software engineering team. This includes risks associated with the software archi-
tecture definition, computing environment definition, software implementation, 
software test and evaluation, and post-development processes. The risk repository 
should capture the initial risk identification memoranda, assessment reports, abate-
ment strategy, and risk monitoring reports.

---

This page intentionally left blank

---

SECTION
3
Stages of Software  
Engineering  
Application
This section addresses the software engineering and related organizational tasks 
that should be accomplished for each stage of the software life cycle. These tasks 
are arranged by the functional organizations involved in the software development 
effort, including software engineering, computing environment preparation, soft-
ware implementation, post-development process preparation, and software test and 
evaluation.
A representation of the software life cycle is shown in 
Figure 1
. This set of life-
cycle stages is used to describe how a software product should be developed, dis-
tributed, and supported. The software life cycle begins with the identification of 
requirements for the software product and the computing environment. The prod-
uct then is designed during architectural definition, which develops the specifica-
tions for each of the functional and physical units and components. Once all of the 
physical units and components have been specified the product and computing envi-
ronment implementation can commence. Once the software units and components 
have been integrated into the complete product configuration the product acceptance 

---