0% found this document useful (0 votes)
130 views16 pages

Software Configuration Management of Version Control Study Based

This document discusses software configuration management and version control based on baselines. It defines key concepts like baselines, versioning, and different version control techniques. Baselines represent verified versions approved after formal change control, and help manage changes for subsequent development. Versioning tracks unique software states. Main version control techniques discussed are check-in/check-out control using a central server, branching/merging for independent development, and maintaining version histories for problem tracing. Baselines play an important role in managing versions and enabling higher quality software development by verifying phases before moving to subsequent phases.

Uploaded by

Faisal Latif
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
0% found this document useful (0 votes)
130 views16 pages

Software Configuration Management of Version Control Study Based

This document discusses software configuration management and version control based on baselines. It defines key concepts like baselines, versioning, and different version control techniques. Baselines represent verified versions approved after formal change control, and help manage changes for subsequent development. Versioning tracks unique software states. Main version control techniques discussed are check-in/check-out control using a central server, branching/merging for independent development, and maintaining version histories for problem tracing. Baselines play an important role in managing versions and enabling higher quality software development by verifying phases before moving to subsequent phases.

Uploaded by

Faisal Latif
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/ 16

Software Configuration Management

of Version Control Study Based on


Baseline
AUTHORS:

Yongchang Ren
Tao Xing
Qiang Quan
Ying Zhao

2010 3RD INTERNATIONAL CONFERENCE ON INFORMATION MANAGEMENT,


INNOVATION MANAGEMENT AND INDUSTRIAL ENGINEERING

Presented By
Usama Khalid (005)
Waqas Ahmed (097)
Daniaal Azmat (109)

Configuration Management
Software development process is a continuous process

of change.
Software configuration management is the discipline of
managing the evolution of complex software systems.
It is the process of controlling and monitoring changes
to work products.
It controls the costs involved in making changes to a
system.
This paper deals with only variant management in
SCM.

Baseline
In order to easily manage the change in the software,

SCM introduces the concept of Baseline.


Baseline is defined as the verification and approval
of the product through formal change control
process before further development.
Baseline is created for each phase of software
development life cycle.
Baseline may be documentation or a sourcecode.

Baseline (cont.)
Baseline of a stable version is a basis for further

development and to release next version.


Baseline contain all the necessary data,
documentation and source codes needed to develop
next version after accommodating change.

Versioning
Software versioning is a way to categorize the unique

states of computer software as it is developed


and released.
Versioning is part of software configuration
management.
Change can be accommodate by releasing new
version of a software with desired functionality.

Versioning (cont.)
Version is a configuration item.
In software development, versions are also

constantly evolving entities.


The new version of the system may have different
functions, performance, may modify the system
error.
Version evolution has 2 types :

Serial evolution
Parallel evolution

Version Control
The current version control is usually supported by a

CASE tool.
Tools use for managing the storage of each system
version, and control access to the system
components.
Components of a system is taken out, edit and place
it again in the system, after this change they
constitute a new version.

Version Control (cont.)


There are three types of version controls discussed in

the paper

Check in-check out Control


Branching and Merging
History record

Check in-check out Control


It is a Centralised Version Control system.
A single server holds the code base
Clients access the server by means of check-

in/check-outs
Examples: CVS, Subversion, Visual Source Safe.
Advantage is, it is easier to maintain a single server.
Check-in is the process of store the software
configuration items from the user's work
environment to the software configuration library

Check in-check out Control


check-out is the process of removing the software

configuration items from software configuration


library.
Synchronous control can be used to ensure that
concurrent execution modification by different
people does not make chaos.

Branching and Merging

First we get a copy from main version.


Copied version is marked and termed it as branch
Changes is made in that copied branch.
Version control is applied
Changed branch is merged back into copied version.

Branching and Merging


To represent an independent development path of

development process and maintenance process


Tin merging we merge the modification of
independent occurred in the two version branches
into one branch.

History Record
History record helps in tracing the source of

problem.
It includes the record of version, the time of version
modification, the modifier, the version modification
description.

Conclusion
Baseline plays an important role in version

management and version control


By using baseline change can be easily managed in
version control process.
We can develop software in terms of better quality by
using baselines.
Baseline somehow works according to concepts of
testing
Before going to next phase we verified the current
phase and than move towards further development.

Thank You

You might also like