Software configuration Management

1. IT 4102
C.I.E.Jayasooriya
ATI - Kurunegala

2.  Functions of a version control system
 Components of a version control system
 Change Control
 Testing
 Developing the configuration management
plan
 Subversion

3.  Pragmatic Version Control using Subversion
by Mike Mason
 Configuration Management Principles &
Practices by Anne Mette Jonassen

4.  Configuration Management is unique
identification , controlled storage , change
control & status reporting of selected
intermediate work products product
components & products during the life of a
system

5.  Configuration management activities may be
viewed as cyclic for each item class placed
under configuration management

6.  Identification
 Storage
 Change control
 Status reporting

8.  The purpose of the identification activity is to
determine the metadata for a configuration
item
 Meta data –
 It describes configuration items
 Metadata for a configuration item may include its
name, the name of the person who produced the
item, the production date, and references to other
related configuration items.

10.  Two incidents may initiate the identification
process:
 In the beginning identification starts with a need
defined in the plans (eg: project plan)
 When you have to change a configuration
item, identification start with a change request

11.  Meta Data

12.  Methods, conventions, and procedures
necessary for the activities in identification
 Procedures for registration of metadata
 Procedures for inheritance of metadata
 Conventions for unique identification
 Conventions for authorization
 Conventions for identification of components in a
delivery

13.  Project and year: SC.91
 Document number: 009
 Author : OA.ect
 Activity identifier: T2.3.1
 Document type: RP (Report)
 Version: 02

14.  The purpose of storage is to ensure that a
configuration item
 will not disappear or be damaged
 it can be found at any time
 delivered in the condition in which you expect to
find it
 that a record is kept to indicate who has been
given the item or a copy of it.

15.  Storage takes place in libraries.
 There are 3 types
 Controlled library/configuration management
library
▪ It is where configuration items are stored.
▪ It may be divided into a number of physical libraries such
as documents, source code,etc
 Dynamic library/development library
▪ It is where items are kept while they are being produced
▪ this will be in the producer's own area

16.  Static Library/user library
▪ It is where items are used
▪ While being used in the static library, items must not be
changed.

17.  Placement in storage from production
 Release from storage for usage
 Release from storage for production

18. The methods, conventions, and procedures
necessary for activities in storage may be
 Procedures for placing items in storage and
related updating of metadata
 Procedures for release for usage
 Procedures for release for production
 Templates for item approval
 Templates for release request

19.  change control is a set of processes and
approval stages required to change a
configuration item's attributes
 The configuration control board (CCB) is
responsible for change control.

21.  Event registration

22.  documented events
 change requests

23.  Creation of the event registration
 Analysis of the event registration
 Rejection or acceptance of the event
registration.
 The change request initiates a new
configuration item.
 A new configuration item is identified and
created, and the change is implemented
 Closing of the change request.
 Closing of the event registration.

24. User Creation of event registration
Developer Analysis of event registration Implementation of change
CCB Evaluation of event Approval or
registration disapproval of change
QA Validation of change

25.  Status reporting makes available, in a useful
and readable way, the information necessary
to effectively manage a product's
development and maintenance

26.  Output – status reports
 Release notes
 Item lists
 Trace matrix

27.  Procedures for the production of available
status reports
 Procedures for ad hoc extraction of
information
 Templates for status reports