|


]
 
] 


 

 
 

]
 |

ƥ The justified villain
ƥ Its inevitable and a fact of life in SE
ƥ Confusions may arise if changes are not
analyzed before they are made,
recorded before implementing, reported
to those with a need to know
ƥ It should be controlled in a manner for
approving quality and error reduction





  


O
ew business or market conditions dictate

changes in product requirements or
business rules
2
ew customer needs demand modification
of data produced by information systems,
functionality delivered by products or
services delivered by a computer system
Four fundamental origins of change
(contƍd)

° e organization or business
(growth/downsizing ) causes changes
in project priorities
 udgetary or scheduling constraints
causes a change in system or product
 þlternate view
ƥ Customers want to change
requirements
ƥ Developers needs to change technical
approach
ƥ Managers want to change project
strategy
As time passes knowledge also increases and
this is the driving force behind change
 4ero enters

Software configuration
management (SCM)
 hefinition of S C M
ƥ An umbrella activity that is applied
throughout the software process
ƥ S c m activities
ƥ O)identify change
ƥ 2)control change
ƥ °)ensure change is done properly
ƥ )report changes to others
hiff between Software support & SCM

Software support SCM

ƥ Set of engineering ƥ Itƞs a set of tracking
activities that occur and controlling
after the software activities that begin
has been delivered when a software
to customer and put engineering project
into operation begins and
terminates with
death of software
 Terms in use

ƥ Software configuration
ƥ ase lines
ƥ Software configuration item
 Software configuration
ƥ Output of software process is
information which is divided into
ƥ O)computer programs
ƥ 2)documents describing computer projects
ƥ °)data(inside the program & external to it)
The items that comprise all the information
produced as a part of the software process
are collectively called software
configuration
 ¢aseline
ƥ A SCM concept that helps us to control
change without seriously impeding
justifiable change
ƥ A specification or product that has been
formally reviewed and agreed upon
,that thereafter serves as the basis for
further development, and that can be
changed only through formal change
control procedures (IEEE)
 aseline (contƞd)
ƥ aseline is a milestone in the development of
software that is marked by the delivery of
one or more software configuration items and
the approval of these SCIƞs that is obtained
through formal technical reviews
ƥ efore a software configuration item becomes
a baseline, change may be made quickly and
informally However, once a baseline is
established, we figuratively pass through a
swinging one way door
 



¢


    

 Software configuration item
ƥ Info created as part of software
engineering process
ƥ Itƞs a single section of large
specification or one test case in a large
suite of tests (extreme way of saying )
ƥ ealistically itƞs a document, a entire
suite of test cases or a named program
component
 SCI = Configuration Object
ƥ In reality SCIƞs are organized to form
configuration objects that may be
catalogued in project database with
single name
ƥ Configuration object has name ,
attribute and is connected to other
objects by relationships
 

 



  

  
    

      
 
 The S C M process
ƥ Other than change control SCM is
responsible for identification of
individual SCIƞs and various versions of
the software
ƥ Also the auditing of software
configuration to ensure its properly
developed
ƥ eporting of all changes applied to the
configuration
 ãuestions facing S C M
O 
      
  
 

   
    !
" 
    

  
 

!
# $ 


    
 
!
% 
 
 !
& $  


 

  !
 `  |


O
dentification
2 ersion control
3 Change control
ð 
     

 ep 

 


 

ƥ To control and manage SCIƞs each must be

separately named and organized using object
oriented approach
ƥ Two types of objects are : basic (unit of text
created during software engineering) and
aggregate (collection of basic or other
aggregate objects)
ƥ Each object has a set of distinct features:
name, description, list of resources ,
ơrealizationơ



  

ƥ Configuration object identification must also consider
the relationships that exist between named objects
An object can be identified as a <part of> an
aggregate object The relationship <part of> defines
a hierarchy of objects
E g E diagram <part of> data model
data model <part of> specification
module interconnection language (M
):
representation of inter-relationships between
configuration objects A MIL describes the
interdependencies among configuration objects and
enables any version of a system to be constructed
automatically
 


  

ƥ Evolution graph : describes change history of
an object
ƥ Lot of tools are there for identification
sometimes a tool is designed to keep info
about the latest version est are achieved
by subtracting from the most recent version
this makes current configuration immediately
available and others are derived easily

`hanks mates!
]
 
] 


 

 
 

]