This ppt is based on configuration management that contains the set of policies and process which we can use to make change in software

1. Configuration Management
• Configuration management is the set of
policies, processes and tools which we use to
manage the change in software
• Why we need a special system to manage the
change in software?
• Because when software is changing with time
it can slip from its track.

2. Configuration Management Activities
• Configuration management is a whole system
which comprise on 4 activities i.e.
a) Change management
b) Version management
c) System building
d) Release management

3. Change Management
• In change management we keep track of
changes requests coming from the customers
or developers.
• Change management also check the cost and
impact of the changes.
• It also decide if the change is really required?
If so, when it is required.

4. Version Management
• It keep track the version number of the
software system it name is already defining it.

5. System Building
• This is the process of assembling and linking all the
program components and libraries to make the
executable system.
• It is complex process, this phase also communicate
with the version control system to check previous build
and to decide what should be the next build.
• Some time developers build a system just for there
testing purpose before giving it to the client, it is
important to keep the track of that system is well.
• It also keep check and balance of the “timestamp”.

6. Release management
• Release management keep track of the release of the
software to the customer.
• It also keep track of the other kind of release.
• There are two kind of release major release and minor
release.
• Like if the release number or let say version number is
8.4.1 it means minor release number is 1 and major
release is 4 and the main software is 8.