Software Engineering

16.4 
Change assimilation
Change assimilation addresses the software control tasks responsible for ensuring 
that authorized changes are properly engineered and integrated into the software 
architecture. Change assimilation begins when the change request or proposal is 
approved by the chairperson of the technical or project-level CCB. The change noti-
fication package should be prepared before the CCB convenes to approve the change.
If the business case, technical merits, and consequences corroborate that a pro-
posed change is advantageous and achievable, then the evaluation team should 
advocate for the change to be undertaken. The final authorization of a change 
request or proposal resides with either the technical or project-level CCB. While the 
software architecture is controlled by the technical CCB, the chief software engi-
neer or chairperson of the technical CCB can ratify the change to be undertaken. 
However, if a change proposal involves the provisioning of additional resources for 
the project to accommodate the proposal, then only the chairperson of the project 
CCB or project manager can ratify the proposal.