Chapter 9
Software Configuration Management
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
What Are These Changes?
changes in
business requirements
changes in
technical requirements
changes in
user requirements
other
documents
software models
Project
Plan
data
Test
code
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
The Software
Configuration
programs
The pieces
documents
data
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Change & SCM
Software Engineering
tools
methods
procedures
a TQM foundation
SCM
identification
version control
change control
auditing
reporting
construction
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Change Control
STOP
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Change Control ProcessI
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
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Auditing
Change
Requests
SCIs
SQA
Plan
SCM Audit
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
10
Status Accounting
Change Change
Requests Reports
ECOs
SCIs
Status Accounting
Reporting
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
11