Software Engineering

280
CHAPTER 16 
Software Control Practice
Assembled change evaluation packages should be provided to change evalua-
tion team members for consideration. The change control administrator should con-
firm that each member of the change evaluation team has received the package and 
can accommodate the change evaluation effort within their work assignments and 
budget constraints.
Table 16.1 
Suggested Content for Change Evaluation Package
Content
Description
Change origin and 
tracking
Provide the source information pertaining to the:
●
  Origins of the requested change
●
  Registered identification number
●
  Originating entity or source of the request
●
  Date the request was recorded into the change-tracking 
system
Change description
Provide a vigilant description of the requested architectural 
modification, including:
●
  Architectural element(s) and the partitions to which they are 
incorporated within which will be affected by the requested 
modification
●
  The modification to be employed in place of the current 
architectural element(s)
●
  The anticipated benefits resulting from the architectural 
modification (e.g., operational improvements, customer or 
consumer acceptance, expanded market penetration, ease 
of use, reduced training and education support required for 
software employment)
Architectural  
artifacts pertaining  
to the evaluation
Identification of the architectural drawings, documentation, 
etc. that are provided as an attachment to the package or their 
digital library locations. Instructions for locating and accessing 
the artifacts should also be provided.
Evaluation 
instructions
Provides the instructions for evaluators on how the requested 
modification should be assessed and emphasizes the areas of 
concern with the proposed change adoption. Should focus on 
determining the:
●
  Technical merits of the change
●
  Architectural design consequences imposed by the 
modification (e.g., architectural complexity)
●
  Technical plan and schedule consequences, if any
●
  Technical work package consequences, if any, resulting 
in the need for rework, artifact revisions, software 
implementation, and testing implications
Evaluation  
milestones
Identifies the milestones associated with:
●
  Consolidating individual evaluations into a unified 
determination for the change request
●
  Presenting the determination to the software engineering 
integrated product team (SWE-IPT)
●
  Presenting the determination to the software change control 
board (CCB)

---