Software Configuration Management of Version Control Study Based

8/18/2019 Software Configuration Management of Version Control Study Based

1/16


2/16

Presented By

sama !halid "##$%

&a'as (hmed "#)*%

+aniaal (,mat "-#)%


3/16

Configuration Management

Software de.elo/ment /rocess is a continuous /rocessof change0

Software configuration management is the disci/line ofmanaging the e.olution of com/le1 software systems0

2t is the /rocess of controlling and monitoring changesto wor3 /roducts0

2t controls the costs in.ol.ed in ma3ing changes to a

system0This /a/er deals with only 4.ariant management5 in

SCM0


4/16

Baseline

2n order to easily manage the change in the software6SCM introduces the conce/t of 4Baseline50

Baseline is defined as the .erification and a//ro.al

of the /roduct through formal change control/rocess 7efore further de.elo/ment0

Baseline is created for each /hase of softwarede.elo/ment life cycle0

Baseline may 7e documentation or a sourcecode0


5/16

Baseline "cont0%

Baseline of a sta7le .ersion is a 7asis for furtherde.elo/ment and to release ne1t .ersion0

Baseline contain all the necessary data6

documentation and source codes needed to de.elo/ne1t .ersion after accommodating change0


6/16

Versioning

Software .ersioning is a way to categori,e the uni'uestates of com/uter software as it is de.elo/edand released0

Versioning is /art of software configurationmanagement0

Change can 7e accommodate 7y releasing new .ersion of a software with desired functionality0


7/16


8/16

Version Control

The current .ersion control is usually su//orted 7y aC(S: tool0

Tools use for managing the storage of each system

.ersion6 and control access to the systemcom/onents0

Com/onents of a system is ta3en out6 edit and /laceit again in the system6 after this change they

constitute a new .ersion0


9/16

Version Control "cont0%

There are three ty/es of .ersion controls discussed inthe /a/er Chec3 in;chec3 out Control Branching and Merging


10/16

2t is a Centralised Version Control system0

( single ser.er holds the code 7ase

Clients access the ser.er 7y means of chec3;

in=chec3;outs:1am/les9 CVS6 Su7.ersion6 Visual Source Safe0

(d.antage is6 it is easier to maintain a single ser.er0

Chec3;in is the /rocess of store the softwareconfiguration items from the user>s wor3en.ironment to the software configuration li7rary

Chec3 in;chec3 out Control


11/16

Chec3 in;chec3 out Control

chec3;out is the /rocess of remo.ing the softwareconfiguration items from software configurationli7rary0

Synchronous control can 7e used to ensure thatconcurrent e1ecution modification 7y different/eo/le does not ma3e chaos0


12/16

Branching and Merging

?irst we get a co/y from main .ersion0 Co/ied .ersion is mar3ed and termed it as 47ranch5 Changes is made in that co/ied 7ranch0 Version control is a//lied

Changed 7ranch is merged 7ac3 into co/ied .ersion0


13/16

Branching and Merging

To re/resent an inde/endent de.elo/ment /ath ofde.elo/ment /rocess and maintenance /rocess

Tin merging we merge the modification of

inde/endent occurred in the two .ersion 7ranchesinto one 7ranch0


14/16


15/16

Conclusion

Baseline /lays an im/ortant role in .ersionmanagement and .ersion control

By using 7aseline change can 7e easily managed in

.ersion control /rocess0 &e can de.elo/ software in terms of 7etter 'uality 7y

using 7aselines0

Baseline somehow wor3s according to conce/ts of

4testing5Before going to ne1t /hase we .erified the current

/hase and than mo.e towards further de.elo/ment0


16/16

Than3 You

Documents

Software Configuration Management of Version Control Study Based