Software Configuration Management

1
Software Configuration Management
2
The First Law
No matter where you are in the system life cycle,
the system will change, and the desire to change
it will persist throughout the life cycle.
Bersoff, et al, 1980
3
What Are These Changes?
changes in
business requirements
changes in
technical requirements
changes in
other documents
user requirements
software models
Project
Plan
data
Test
code
4
The Software Configuration
programs
documents
The pieces
data
5
Baseline

• Milestone marked by delivery approval of a set
  of software configuration items
• Once baselined only modified if formal
  procedure followed

6
Change SCM
Software Engineering
SCM
identification
tools
version control
methods
change control
procedures
auditing
a TQM foundation
reporting
construction
7
Identification

• Items organized using oo approach
• Each object
• Name
• Description project version
• Resources
• Realization link to object
• Must keep track of interrelationships between
  objects

8
Version Control

• Procedures tools to handle different versions
  of configuration objects
• Automated support

9
Change Control
STOP
10
Change Control Process - 1
need for change is recognized
change request from user
developer evaluates
change report is generated
change control authority decides
request is queued for action
change request is denied
user is informed
change control processII
11
Change Control Process-II
assign people to SCIs
check-out SCIs
make the change
review/audit the change
establish a baseline for testing
change control processIII
12
Change Control Process-III
perform SQA and testing activities
check-in the changed SCIs
promote SCI for inclusion in next release
rebuild appropriate version
review/audit the change
include all changes in release
13
Auditing
Change Requests
SQA Plan
SCIs
SCM Audit
14
Status Accounting
Change Reports
Change Requests
ECOs
SCIs
Status Accounting
Reporting