Software Engineering

8.5.3 
Assess proposed changes
Changes to software requirements must be assessed to determine the impact of 
the change on the project framework against the necessity for the change. If a pro-
posed change is determined to be essential for the software product to satisfy stake-
holder needs, then the change may be necessary. However, the project resources 
may not accommodate the additional work effort necessary to incorporate the pro-
posed change into the software architecture. The approach for performing a change 
impact assessment involves the following five steps:
1. 
Define the scope of the change proposed by identifying the work packages that 
would be affected by authorizing the change.
2. 
Determine the key differences in the proposed project state to determine the 
impact on the project’s critical path toward achieving milestones and objectives.
3. 
Determine the ability of the project framework to accommodate the proposed 
change by adjusting work estimates, as appropriate.
4. 
Assess the project sensitivity or probability of success assuming the change is 
authorized.
5. 
Present the findings and recommendations to the appropriate change control 
board.
Change proposals should address changes to the requirements baseline once it is 
established and should involve one or more stakeholders to champion the proposed