Software Engineering

281
16.3 
Change evaluation
16.3 
Change evaluation
The change evaluation team members should assess the proposed architectural 
modification to determine the merits and consequences of adopting the change. The 
evaluation team must substantiate the value proposition inherent with a change, 
involving:
●
  Technical merits of the proposed modification (improvements in functionality, 
performance, usability, supportability, and operational suitability).
●
  Consequences implied with adopting the proposed modification to the software 
architecture (increased complexity, scope (depth and breadth) of the change,  
and the ripple effect to other architectural elements by adopting the 
modification).
●
  Consequences of adopting the modification to the technical plans and schedule.
●
  Consequences to the technical work packages and resource allocations.
●
  Additional resources that accompany a change proposal.
●
  That each technical organization can accommodate the change assimilation 
effort within their workload capacity, budget constraints, and proposed work 
package reallocations.
Change proposals may represent a burden for the software development effort 
to contemplate given the availability of resources within the current structure 
of the project. Additional resources may accompany a proposed change to offset 
the rework and realignment of architectural design characteristics. The additional 
resources needed to assimilate a change must be determined to be sufficient to 
counteract the amplified workload involved with incorporating the change within 
the software development agenda.