INTERNATIONAL INSTITUTE OF PROFESSIONAL STUDIES

DAVV-INDORE (M.P.)

CONFIGURATION MANAGEMENT AND

SOFTWARE CONFIGURATION MANAGEMENT

NAME :- PRAWAL MISHRA

UNDER THE GUIDANCE OF :- COURSE :- M.TECH (8TH-SEM)
DR.KIRTI MATHUR ROLL.NO :- IT-2K16-32
 ● CONFIGURATION
MANAGEMENT

● CONFIGURATION
MANAGEMENT ACTIVITIES

● SOFTWARE CONFIGURATION
MANAGEMENT
Software Engineering
● NECESSITY OF SOFTWARE
CONFIGURATION
MANAGEMENT

● ADVANTAGES OF SOFTWARE
CONFIGURATION
MANAGEMENT
CONFIGURATION MANAGEMENT

Configuration management is a systems engineering process for establishing

and maintaining consistency of a product's, performance, functional and
physical attributes with its requirements, design, and operational information
throughout its life.

The configuration management tool enables the engineers to change the

various components in a controlled manner.
CONFIGURATION MANAGEMENT ACTIVITIES

CONFIGURATION MANAGEMENT ACTIVITIES

CONFIGURATION IDENTIFICATION CONFIGURATION CONTROL

CONFIGURATION IDENTIFICATION

Configuration identification decides the part of the data system which

needs to be kept track of.

Configuration identification is the process of identifying the attributes

that define every aspect of a configuration item

Any Object associated with a software development activity can be

classified into three main categories :-

(1)Controlled

(2)Pre-Controlled

(3)Uncontrolled
CONFIGURATION IDENTIFICATION

Controlled :- Controlled objects are those which are already put under
configuration control

Pre-Controlled :- Pre-controlled objects are not yet under configuration

control, but will eventually be under configuration control.

Uncontrolled :- Uncontrolled objects are not and will not be subjected to

configuration control.

// Controllable objects include both controlled and pre-controlled objects.//

Typical controllable object includes

• Requirements specification document

• Design documents

• Tools used to build the system, such as compilers, linkers, lexical analyzers, parsers,
etc.

• Source code for each module

• Test cases

• Problem reports
Important points

The configuration management plan is written during the project

planning phase and lists all controlled objects.

The managers who develop the plan must strike a balance between
controlling too much, and controlling too little. If too much is
controlled, then configuration management increase to
unreasonably high levels. On the other hand, controlling too little
might lead to confusion when something changes.
Configuration control

Configuration control ensures that changes to a system are implemented

smoothly.

Configuration control is the part of a configuration management system

that most directly affects the day-to-day operations of developers.

The configuration control system prevents unauthorized changes to any

controlled objects.

In order to change a controlled object such as a module, a developer can

get a private copy of the module by a reserve operation.
Configuration control

Configuration management tools allow only one person to reserve a

module at a time.

Once an object is reserved, it does not allow any one else to reserve this
module until the reserved module is restored .
SOFTWARE CONFIGURATION MANAGEMENT

“ Software Configuration Management is a process to systematically

manage, organize, and control the changes in the documents, codes,
and other entities during the Software Development Life Cycle.’’

OR

“ Software Configuration Management is a set of activities that have

been developed to manage change throughout the software life cycle.”
PURPOSE

Systematically control changes to the configuration and maintain the

integrity and traceability of the configuration throughout the systems
life cycles.

SCM Helps organizations to systematically manage, organize and

control changes in documents, codes and other entities during SDLC.

The aims of software configuration management is to control cost and

work effort involved making changes to software system.

The primary goal is to increase productivity with minimal mistakes.

Necessity of software configuration management

There are several problem regarding updatations and storage.

(1)Inconsistency problem when the object is replicated:-
When several engineers work on the same copy of an objects, and change it but
forget to notify other team members than at the time of integration the software
does not work.

(2)Problem associated concurrent access:-

When engineers work on a single copy of object modify it and forget to notify
and overwrite each others work.
(3)Providing a stable development environment:-

Means if we work 3 modules say A,B,C to be integrated but since the developer
of module C keeps changing it, then you cannot make progress in work.

(4)System accounting and maintaining status:-

Existence of variants (version/revision) of a software product cause at least 2 kinds
of problem.

(i) If several variants modules exists, and we find a bug in one of them, then
fixing is required to all.

(ii) Changes made to one modules need to be done in all modules and
programmes may overwrite each other in the event of writing different
functionalities.
Advantages of SCM

Reduced redundant work.

Effective management of simultaneous updates.

Avoids configuration related problems.

Facilities team coordination.

Defect tracking.
THANK YOU