Module 6 Scm Mba

7/29/2019 Module 6 Scm Mba

1/22

Introduction to Software

Configuration Management (SCM)

Ikram Ahmed KhanChief Executive

Business Beam (Pvt.) Limited

[email protected]
mailto:[email protected]:[email protected]


2/22

Business Beam (Pvt.) Limited 2

Why do Software Configuration

Management?

Some common issues of developers: I want my work back, and I want it back

now.

The problem occurred because client wasrunning wrong version of the software.

Ops! The bug was solved but it suddenlyreappeared.

The developed and tested feature is

suddenly missing. Ops! Some wrong files were complied and

sent to client.


3/22


What is SCM?

Configuration Management is a

umbrella activity similar to SPM &

SQA.

If you dont control the changes, it

controls you.

SCM is essential part of Project

Management and solid software

Engineering Practices.


4/22


Formal Definition

Software Configuration

Management is a set of

engineering procedures for

tracking and documenting software

throughout its life cycle, to ensure

that all changes are recorded and

current state of the software isknown and reproducible.


5/22


SCM answers the following

questions!

What constitutes the software

product at any point in time?

What changes have been made to

the software product?


6/22


Rational for having SCM

Without SCM, we can face

following problems: Simultaneous Update

Redundant work for maintenance

Shared code & work products

Common Code

No Control on Versions


7/22 Business Beam (Pvt.) Limited 7

SCM and Productivity

A project that takes one person 12 months is a

12 man-month project. However, the same

project is not likely to be completed by 2

people in 6 months, or 3 people in 4 months.

The more people get involved, more time is

spent on the communication among the staff.

SCM reduce the time spend in communication,

and more time is available for software

development.



Functional Areas of SCM


Identification

Software Configuration Control

SC Status Accounting & Reporting

Software Configuration Audits




Identification (SCI)

SCI involves:

Identifying the structure of the software

Uniquely identifying individual components

Making them accessible in some form

Goals of SCI:

To create the ability to identify the system

components throughout the SDLC To provide traceability between the

software & related SCIs.




Identification (cont)

Identification Activity includes:

Selecting items to be placed under SCM

control.

Developing the software hierarchy. Creating an identification scheme that

reflects the software hierarchy.

Uniquely identifying the various revisions of

the software product. Defining relationships and interfaces

between the various software products.


11/22




SCI methods primarily address the

following issues:

Baselines

Versions

Naming convention


12/22




What is Software Configuration

Item?

Documents

Programs (Code)

Structures (Model)


13/22


Baseline

Baseline represents the assignment of a name to each

group of SCIs that are related to each other.

A baseline can be defined as a milestone in the

development of the software that is marked by thedelivery after formal technical review.

A baseline is a specification or product that has been

formally reviewed and agreed upon, that thereafter

serves as the basis for further development and that canbe changed only through formal change procedures.


14/22


Version

When item is baselined, it become frozen. The term

frozen means that the item can only be changed by

creating a new version.

Version Control

It ensures repeatability and the ability to produce any

version of the software at any given time.

Version Control Automation

Labels for product

Hierarchical Structure

Version Making

Document Labeling


15/22


Change Controls Board (CCB)

Change

Proposals

Document

Change

Review byCCB

Implement

Verify

Accept

Reject


16/22


SC Status Accounting and

Reporting

Configuration Status Reporting also called

Status Accounting is an SCM task that may be

viewed as an accounting system.

Configuration Status Accounting is defined asan element of configuration management,

consisting of recording and reporting of

information that is needed to manage a

configuration effectively.


17/22



Reporting (cont)

Purpose

The purpose of software

configuration status accounting is to

maintain continuous records of thestatus of all basedline items.

It is also used as:

Management Tool Disaster Insurance


18/22



Reporting (cont)

Needed Information

The time at which baseline were

established.

When each SCI was included in thebaseline.

When each change was added to baseline.

A description of each software change.

Documentation status of each baseline. A description of each SCI.


19/22



Reporting (cont)

Planning: Status accounting

reports need to be addressed in

detail in the SCM plan:

Type of information that is needed to

be reported.

Degree of controls on status

reporting required by the customer. Status reporting standards, both

internal and customer driven.


20/22



Audit should periodically be performed

to ensure that the SCM practices and

procedures are rigorously followed

Ensure the integrity of the softwarebaseline over the product life cycle

Should be performed prior to every

major baseline change


21/22



The phase review process ensures that

proper SCM actions are taken as

follows:

Requirements Functional

Design

Product

Operational


22/22

Thank You

Module 6 Scm Mba

Documents

Transcript of Module 6 Scm Mba