software configuration management

15
Software Configuration Management (SCM) Prepared by:- Virendra Singh Thakur 131060753022

Upload: virendra-thakur

Post on 09-Jun-2015

169 views

Category:

Engineering


3 download

DESCRIPTION

Software Configuration Management (SCM)

TRANSCRIPT

Page 1: Software Configuration Management

Software Configuration Management (SCM)

Prepared by:-Virendra Singh Thakur131060753022

Page 2: Software Configuration Management

What is Software Configuration Management?

Need of SCM Elements of SCM Version Numbering Roles and Accesses in SCM

Outlines

Page 3: Software Configuration Management

It is about managing the project related items (software, code, checklists, artifacts) Organizing in a structured way Securing only to the privileged users Controlling during modification

What is Software Configuration Management?

Page 4: Software Configuration Management

Describes the IEEE Std 828-1990, IEEE standard for software configuration management plans, establishes the minimum required contents of a software configuration management plan and defines the specific activities to be addressed and their requirements for any portion of a software product's life cycle.

Contd..

Page 5: Software Configuration Management

Some of the frustrating problems we face are The latest version of the source code not

found A difficult bug that was fixed at great

expense suddenly re-appears A developed and tested feature is

mysteriously missing A fully tested program suddenly does not

work A wrong version of code was tested

Why do we need SCM?

Page 6: Software Configuration Management

SCM answers who, what, when And Why)Who makes the changes?What changes were made to the system?When were the changes made?Why were the changes made?

Contd..

Page 7: Software Configuration Management

Without configuration ManagementUnorganized project itemsConfused naming conventionsReview / Delivery of wrong version of codeDevelopment based on old version of

specificationsNo proper access / privilege control; Unauthorized access to secure

Contd..

Page 8: Software Configuration Management

Configuration identificationCI – Configuration ItemNCI – Non-Configuration item Configuration control (Elements)Library ControlAccess ControlVersion ControlEstablish Naming conventionsBranching, Merging and Labeling Change Management

Elements of SCM

Page 9: Software Configuration Management

Administratorall access to all folders.can add users to a project’s VSS, and modify their

access levels Configuration Manager greater access than all team-members.responsible for moving files across projects,

establishing baselines, adding requirements files, preparing guidelines,

etc.

Different Roles and Accesses in SCM

Page 10: Software Configuration Management

Team-membervarying access depending on their

responsibilities. For e.g. PM gets add/modify access to Management project

Contd..

Page 11: Software Configuration Management

Selecting the right version and latest version is ver

y important, This can be achieved by assigning attributes to the CI names Version number normally represented as X.Y First digit represents the version number,

Second digit represents revision number. The first formal release document shall bear the

version number 1.0.

Version Numbering

Page 12: Software Configuration Management

Contd..

Page 13: Software Configuration Management

Check –in and Check -Out

• A check-out is the act of creating a local working copy from the repository. A user may specify a specific revision or obtain the latest.

• A check - in is the action of writing or merging the changes made in the working copy back to the repository.

Page 14: Software Configuration Management

Software Configuration Management and Its Contribution to Reliability Program Management

0018-9529/83/0800-0289$O1 .00©( 1983 IEEE)

Published In AUGUST 1983 IEEE

References

Page 15: Software Configuration Management

Thank you