unit 4-configuration management

8/13/2019 Unit 4-Configuration Management

1/30

Unit 4

Configuration Management


2/30

Configuration Managemnet

Change is continuous proces in softwaredevelopment

Many artifacts are created ,used and modified

One needs to manage the changes in a controlledway

Configuration means patterns, designs which affect

the characteristics or attributes of the final product

Controlling a change and managing the effect of one

change on the other artifacts through impact analysis

to produce desired patterns is termed Configuration

Management


3/30


4/30

Configurable Artifacts

Some artifacts needs to be changed during the

SDLC. Such artifacts are called configurable

artifacts.

Ex:SRS, design documents, test cases

Changes in one may start a chain reaction and

one may need to control it


5/30

Nonconfigurable Arifacts

There are few artifacts may change or may not

change

If there is any change nobody needs to

track /control the results

Ex: test results, minutes of meeting


6/30

Controlled Artifacts

There are few artifacts may change , but do

not need any review

Though change may not require any approval,

the changes must happen in a controlled

manner

Ex:changes in structure of the organisation,

contact people, changes in team members.


7/30

Managed and controlled Artifacts

Changes are controlled and tracked. Any such

change needs someone to review and

approve.

Ex: SDLC Plans, requirement specification,

design documents


8/30

Cycle of Configuration Management

Creation of Draft

Review of Draft

Baselining - Once the Final decision is reached on thereview comments, actions are initiated accordingly to

update the artifacts Versioning Methods

xx.yy.zz--- xx represents a major change

yy represents minor change

zz represents a draft versionxx.yy--- xx for all changes

zz represents a draft version


9/30

Configuration Management Process

Draft-> Review->Rework->Baseline

And further updations as and when essential

Steps:

-Establishing Configuration library

-PM is the owner of CL-CL stores all configurable items and work products for the givenproject.

-Structure of a configuration library

-Planning artifacts

-Source related artifacts-Requirements related artifacts

-Design related artifacts

-Testing artifacts


10/30

continued- Establishing definition of versions and processes for updation

- Definition of access privileges for users of configuration library

-Administrative Access

- Add/Delete Access

-Check out/Check in access

-Read Access

-Drafting a configurable item-Review of Draft

-Approval of Draft

-Further Updation

-Creation of documents

-Check in/ Check Out-Get latest version

-Working folder

-Deleting Cofiguration artifacts

-Recovery of deleted artifacts

-Destroy/Purge for artifacts


11/30

Auditing Configuration Library

Status Accounting

Configuration Management Audit


12/30

Typical configurable item

Requirements, Technology-.Jaya

Complexity .Anupam

Process.Upasana

Complete services H/S---Bharat

CompatibilityAbhijit Billing/Type of project, Testing----Girish

Change in the process---Divya

Constraints----Nileshwari

Integration of different modules---Sonali

Planning----Manoj Documenting---Ami

Reliable and Accurate---Aman


13/30

Few more concepts about

configuration Library-Storage of configurable items in the library

-Branching

-Merging

-Finding history

-Comparison-Rollback

-Labeling

-Pinning

-Sharing-Conflict Handling

-Multiple checkout


14/30


15/30

Advantages of using a tool

Automated

Accuracy

Ambiguity free

Cost efficiency

Performance

User friendly GUI

Abstract

Regular backups

Security

Regular updation


16/30

Disadvantages of Using Tools

Experts required

Errors

Small projects

Time consumed to learn the concept

Cost for small projects

Frequent usability?

Platform issues

Availability

Complexity


17/30

Configuration management PlanningIs required to set up and use configuration

Library.

Basic areas of configuration management:

1.Introduction

2.Scope

3.Configuration management activities and responsibilities

4.Access privileges5.Configuration management procedure

6.Configurable items with naming conventions

7.Change Control

8.Working folder definition

9.Commenting standards

10.Labeling standards

11.Tools and usage

12.Assumptions and risks

13.Configuration status reporting

14.Traceability matrix

15.Integration and build procedure16.Configuration management audits


18/30

Starts during the early phases of the project

All products of the software process may haveto be managed Specifications Designs

Programs

Test data

User manuals

Thousands of separate documents may begenerated for a large software system


19/30

Defines the types of documents to be managedand a document naming scheme

Defines who takes responsibility for the CMprocedures and creation of baselines

Defines policies for change control and versionmanagement

Defines the CM records which must bemaintained

Describes the tools which should be used toassist the CM process and any limitations on theiruse


20/30

Software systems are subject to continualchange requests From users

From developers From market forces

Change management is concerned withkeeping

track of these changes and ensuring that theyare implemented in the most cost-effectiveway

Change management


21/30

Request change by completing a change request formAnalyze change request

ifchange is valid then

Assess how change might be implementedAssess change costSubmit request to change control board

ifchange is accepted then

repeatmake changes to sof tw are

submit changed softw are for quality approval

untilsof tware quality is adequate

create new system versionelse

reject change request

elsereject change request

The change management process


22/30

Maintenance activities and configuration

Management

Applying a patch

Updating source code


23/30

Configuration Management

Measurements


24/30

Quality Tips

Understand the limitations of tools and

database used in automated tools for

configuration management. Every tool may

have some limitations and database size alsomatters to the maintain the integrity of

software


25/30

Create a configuration library only after

understanding the customer specific and

project specific requirements. Future

requirements for the project must beconsidered while selecting a tool and setting

up a library.


26/30

Conduct baseline audits and configuration

management audits as per the frequency

defined. This can ensure that deliverables

going to the customer are correct and the

configuration management process is

followed correctly


27/30

Be careful while dealing with conflicts. As far

as possible, conflicting situations must be

avoided
http://localhost/var/www/apps/conversion/tmp/scratch_8//upload.wikimedia.org/wikipedia/commons/7/7f/ConfiurationActivityModel.png


28/30
http://localhost/var/www/apps/conversion/tmp/scratch_8//upload.wikimedia.org/wikipedia/commons/7/7f/ConfiurationActivityModel.png


29/30

Key Points

Configuration management is the managementof system change to software products

A formal document naming scheme should be

established and documents should be managedin a database

The configuration database should recordinformation about changes and change requests

A consistent scheme of version identificationshould be established using version numbers,attributes or change sets


30/30

unit 4-configuration management

Documents