Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Configuration and Change Management Discipline

Purpose Track and maintain the integrity of evolving project assets. The project team members must be able to:  identify and locate artifacts,  to select the appropriate version of an artifact,  to look at its history to understand its current state and  the reasons it has changed, and  to ascertain who is currently responsible for it. 2

3 The CCM Cube

4 The CCM Cube- Configuration Management

 Important artifacts are placed under version control.  As an artifact evolves,  multiple versions exist, and  you must identify  the artifact,  its versions, and  its change history. 5 The CCM Cube- Configuration Management

 Artifacts depend on one another.  As a result, each change causes a ripple effect.  Build management  making sure that components that would constitute a build are  available and are  assembled in the right order  based on their dependency hierarchies.  Must trust to components  have been developed and  tested adequately to be included in a build.  An artifact is OK only if its ancestors are OK. 6 The CCM Cube- Configuration Management

The CCM Cube- Change Request Management 7

 Changes to artifacts  tracked and  associated with the corresponding change request.  Change requests are closed when  the change has been completed,  tested, and  included in a release 8

The CCM Cube- Status and Measurement 9