Scribd
Upload
22 views13 pages

Uint 5 Topic 5 Software Configuration Management Activities

Uploaded by

Rayush Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
22 views13 pages

Uint 5 Topic 5 Software Configuration Management Activities

Uploaded by

Rayush Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Software Configuration

Management Activities
Dr. Rohit Rastogi
Associate Professor,
Computer Science & Engineering Department,
ABES EC, Ghaziabad
Affiliated to Dr. A.P.J. Abdul Kalam Technical University, Uttar
Pradesh, Lucknow
Basic
Configuration Management (CM) is a technic of
identifying, organizing, and controlling modification to
software being built by a programming team.
Identification
 Basic Object: Unit of Text created by a software engineer during
analysis, design, code, or test.

 Aggregate Object: A collection of essential objects and other


aggregate objects. Design Specification is an aggregate object.

 Each object has a set of distinct characteristics that identify it


uniquely: a name, a description, a list of resources, and a
"realization.“

 Interrelationships
between configuration objects can be described
with a Module Interconnection Language (MIL).
Version Control
Version Control combines procedures and tools to
handle different version of configuration objects that are
generated during the software process.

Creating versions/specifications of the existing product


to build new products with the help of the SCM system.
Conti…
Clemm defines version control in context of SCM
Configuration management allows a user to specify
alternative configuration of software system through
selection of appropriate versions.

This is supported by associating attributes with each


software version, and then allowing a configuration to
be specified [and constructed] by describing set of
desired attributes.
Change Control
James Bach describes change control in context of SCM is:
Change Control is Vital. But forces that make it essential
also make it annoying.

A burdensome change control process could effectively


discourage it from doing creative work.

A change request is submitted and calculated to assess


technical merit; potential side effects, overall impact on
other configuration objects and system functions, and
Conti…
Access Control governs which software engineers have
authority to access and modify a particular
configuration object.

Synchronization Control helps to ensure that parallel


changes, performed by two different people, don't
overwrite one another.
Conti…
Configuration Audit
SCM audits to verify that software product satisfies
baselines requirements and ensures that what is built
and what is delivered.

SCM audits also ensure that traceability is maintained


between all CIs and that all work requests are associated
with one or more CI modification.

SCM audits are "watchdogs" that ensures that integrity


of project's scope is preserved.
Status Reporting
Configuration Status reporting providing accurate status
and current configuration data to developers, testers,
end users, customers and stakeholders through admin
guides, user guides, FAQs, Release Notes, Installation
Guide, Configuration Guide, etc.
Advantages of SCM
Improved productivity and efficiency by reducing time
and effort required to manage software changes.
Reduced risk of errors and defects by ensuring that all
changes were properly tested and validated.
Increased collaboration and communication among
team members by providing a central repository for
software artifacts.
Improved quality and stability of software systems by
ensuring that all changes are properly controlled and
managed.
Disadvantages of SCM
Increased complexity and overhead, particularly in
large software systems.

Difficultyin managing dependencies and ensuring that


all changes are properly integrated.

Potential
for conflicts and delays, particularly in large
development teams with multiple contributors.

You might also like