Software Engineering

276
CHAPTER 16 
Software Control Practice
provide a more detailed accounting of the evolving software architecture, trade 
studies, risks, and the adjudication and assimilation of change requests and propos-
als. The evolution of the software architecture continues until the structural configu-
ration is submitted for project-level configuration control. This submission signifies 
that the software architecture has been judged to be relatively stable, durable to 
change, and methodically detailed and specified.
Typical project-level configuration management (CM) practices apply to the 
software product configuration and its associated configuration items. Technical 
configuration control oversees the complete software architecture to manage the 
allocation and traceability of specified software requirements throughout the func-
tional and physical architecture. This includes the identification and specification of 
structural units, components, and internal interfaces.
Change requests and proposals must be distinguished between those that affect 
the project or contract scope and those that only affect the technical effort. Change