Transcript Document

Computing and SE II
Chapter 17: Software Configuration
Management
Er-Yu Ding
Software Institute, NJU
Main Contents
1. What is SCM?
2. Terminologies of SCM
3. The SCM Process
1. What is SCM ?
---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
1. What is SCM ?
--- Software Configuration
SCM
• IdentifyManagement,
change
• Control change
• Ensure that change is being properly
implemented
• Report changes to others who may
have an interest
1. What is SCM ?
--- What Are These
changes in
Changes?
business requirements
changes in
technical requirements
changes in
user requirements
other
documents
software models
Project
Plan
data
Test
code
1. What is SCM ?
--- The Software
Configuration
programs
The pieces
documents
data
Also include software tools, such as editor, compiler, browser
and so on.
2. Terminologies of SCM
--- Baselines
• The IEEE (IEEE Std. No. 610.12-1990)
defines a baseline as:
• 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.
• a baseline 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 Software Configuration Items (SCIs)
2. Terminologies of SCM
--- Baselines
modif ied
SCIs
Project database
Sof tware
engineering
tasks
SCIs
Formal
technical
rev iews
approv ed
SCIs
stored
SCIs
ext ract ed
SCM
controls
SCIs
BASELINES:
Sy st em Specif ication
Sof tware Requirements
Design Specif icat ion
Source Code
Test Plans/Procedures/Dat a
Operat ional Sy stem
Figure 27.1
2. Terminologies of SCM
--- SCM Repository
• The SCM repository is the set of
mechanisms and data structures that allow
a software team to manage change in an
effective manner
• The repository performs or precipitates the
following functions [FOR89]:
–
–
–
–
–
–
Data integrity
Information sharing
Tool integration
Data integration
Methodology enforcement
Document standardization
2. Terminologies of SCM
--- Repository Content
business rules
business funct ions
organizat ion st ruct ure
inform at ion archit ect ure
Business
Cont ent
use-cases
analy sis m odel
scenario-based diagram s
flow-orient ed diagram s
class-based diagram s
behav ioral diagram s
design m odel
archit ect ural diagram s
source code
object code
sy st em build inst ruct ions
Const ruct ion
Cont ent
int erface diagram s
com ponent -lev el diagram s
t echnical m et rics
t est cases
t est script s
t est result s
qualit y m et rics
Model
Cont ent
V&V
Cont ent
proj ect est im at es
proj ect schedule
SCM requirem ent s
change request s
change report s
Project
Management
Cont ent
SQA requirem ent s
proj ect report s/ audit report s
proj ect m et rics
Document s
Project Plan
SCM/ SQA Plan
Sy st em Spec
Requirem ent s Spec
Design Docum ent
Test Plan and Procedure
Support docum ent s
User m anual
Figure 27.3
• Versioning.
2. Terminologies of SCM
--- Repository Features
– saves all of these versions to enable effective management of product releases
and to permit developers to go back to previous versions
• Dependency tracking and change management.
– The repository manages a wide variety of relationships among the data
elements stored in it.
• Requirements tracing.
– Provides the ability to track all the design and construction components and
deliverables that result from a specific requirement specification
• Configuration management.
– Keeps track of a series of configurations representing specific project
milestones or production releases. Version management provides the needed
versions, and link management keeps track of interdependencies.
• Audit trails.
– establishes additional information about when, why, and by whom changes
are made.
3. The SCM Process
Sof tware
Vm.n
reporting
conf igurat ion auditing
v ersion control
change cont rol
ident if ication
SCIs
•
3. The SCM Process
--- Software Configuration
Developing Identification
a system requires a definition of
the baseline components
– One label identifies the baseline itself
– The second label identifies any updates the that
baseline
• Changes to these baseline components
specify the system evolution
• The software baseline consists as an
aggregate of system components called SCI
(Software Configuration Items)
3. The SCM Process
--- Change Control
STOP
3. The SCM Process
--- Change Control
Process—I
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 process—II
3. The SCM Process
--- 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 process—III
3. The SCM Process
--- 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
•
3. The SCM Process
--Version
Control
Version control combines procedures and tools to manage
different versions of configuration objects that are created
during the software process
• A version control system implements or is directly integrated
with four major capabilities:
– a project database (repository) that stores all relevant
configuration objects
– a version management capability that stores all versions of a
configuration object (or enables any version to be constructed
using differences from past versions);
– a make facility that enables the software engineer to collect all
relevant configuration objects and construct a specific version of
the software.
– an issues tracking (also called bug tracking) capability that
enables the team to record and track the status of all
outstanding issues associated with each configuration object.
3. The SCM Process
--- Auditing
Change
Requests
SCIs
SQA
Plan
SCM Audit
3. The SCM Process
--- Status Accounting
Change
Change
Reports
Requests
ECOs
SCIs
Status Accounting
Reporting
END
• Next Lecture
– Software tools and environment