Configuration Management(CM) is a key component of software
development. The CM keeps tracks of all the changes made to
the project artifacts. Generally we place all the base lined
documents in CM tool. For large projects, even some
companies employ Configuration Manager who is responsible of
tracking the base line documents and even prepares
configuration test plan.
The list below illustrates the types of project artifacts
that must be managed and controlled in the CM environment:
·	Source code
·	Requirements
·	Analysis models
·	Design models
·	Test cases and procedures
·	Automated test scripts
·	User documentation, including manuals and online Help
·	Hardware and software configuration settings
·	Other artifacts as needed


Change Management:
Managing change is a process. The process is the primary
responsibility of the software
development staff. They must assure that the change requests
are documented, that they are tracked through approval or
rejection, and then incorporated into the developmental process.
Many software development project teams group changes to be
implemented into a new version of the system. This grouping
normally reduces the costs associated with incorporating
changes into the software requirements during development.
The testers need to know two aspects of change:
1.	The characteristics of the change so that modification to
the test plan and test data can be made to assure the right
functionality and structure are tested.
2.	The version in which that changes will be implemented.