Object-Oriented Software Engineering

Using UML, Patterns, and Java

Configuration Management

Outline of the Lecture

♦ Purpose of Software Configuration Management (SCM)
w Motivation: Why software configuration management?
w Definition: What is software configuration management?
w Activities and roles in software configuration management
♦ Some Terminology
w Configuration Item, Baseline, SCM Directory, Version, Revision
Release.
♦ Software Configuration Management Activities
w Promotion Management, Release Management, Change Management
♦ Outline of a Software Configuration Management Plans
w Standards (Example: IEEE 828-2005
w Basic elements of IEEE 828-2005
♦ Configuration Management Tools

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2

Page 1
Why Software Configuration Management ?

♦ The problem:
w Multiple people have to work on software that is changing
w More than one version of the software has to be supported:
t Released systems
t Custom configured systems (different functionality)
t System(s) under development
w Software must run on different machines and operating systems

➭ Need for coordination

♦ Software Configuration Management
w manages evolving software systems
w controls the costs involved in making changes to a system

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3

What is Software Configuration Management?

♦ Definition:
w A set of management disciplines within the software engineering process
to develop a baseline.

♦ Description:
w Software Configuration Management encompasses the disciplines and
techniques of initiating, evaluating and controlling change to software
products during and after the software engineering process.

♦ Standards (approved by ANSI)

w IEEE 828-2005: Software Configuration Management Plans
w IEEE 1042-1987: Guide to Software Configuration Management
(Archived)

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4

Page 2
Managing Software Configurations

♦ Software Configuration Management is a project function (as defined

in the software project management plan) with the goal to make
technical and managerial activities more effective.
♦ Software Configuration Management can be staffed in several ways:
w A single team performs all software configuration management activities
for the whole organization
w A separate configuration management team is set up for each project
w All the software configuration management activities are performed by
the developers themselves
w Mixture of all of the above

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5

Configuration Management Activities

♦ Configuration item identification

w modeling of the system as a set of evolving components
♦ Promotion management
w the creation of versions for other developers
♦ Release management
w the creation of versions for the clients and users
♦ Change management
w the handling, approval and tracking of change requests
♦ Branch management
w the management of concurrent development efforts
♦ Variant management
w the management of versions intended to coexist

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6

Page 3
♦ No fixed rules:
w SCM activities are usually performed in different ways (formally,
informally)
w depending on the project type and life-cycle phase (research,
development, maintenance).

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7

Terminology

♦ We will define the following terms

w Configuration Item
w Baseline
w SCM Directories
w Version
w Revision
w Release

➭ The definition of the terms follows the IEEE standard.

➭ Different configuration management systems may use different
terms.
➭ Example: CVS configuration management system and ADAMS (that is
used in our projects) use terms differing from the IEEE standard.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8

Page 4
Terminology: Configuration Item

“An aggregation of hardware, software, or both, that is designated

for configuration management and treated as a single entity in the
configuration management process.”

v Software configuration items are not only program code segments but all type of
documents according to development, e.g
➭ all type of code files
➭ drivers for tests
➭ analysis or design documents
➭ user or developer manuals
➭ system configurations (e.g. version of compiler used)

v In some systems, not only software but also hardware configuration items (CPUs,
bus speed frequencies) exist!
v Even a commercial product used in the system can be a configuration item

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9

Finding Configuration Items

♦ Large projects typically produce thousands of entities (files,

documents, data ...) which must be uniquely identified.
♦ Any entity managed in the software engineering process can
potentially be brought under configuration management control
♦ But not every entity needs to be under configuration management
control all the time.
♦ Two Issues:
w What: Selection of Configuration Items
t What should be under configuration control?
w When: When do you start to place entities under configuration control?
♦ Conflict for the Project Manager:
w Starting with CIs too early introduces too much bureaucracy
w Starting with CIs too late introduces chaos

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10

Page 5
Finding Configuration Items (continued)

♦ Some items must be maintained for the lifetime of the software. This
includes also the phase, when the software is no longer developed
but still in use;
♦ An entity naming scheme should be defined 
so that related documents have related names.

♦ Selecting the right configuration items is a skill that takes practice

w Very similar to object modeling
w Use techniques similar to object modeling for finding CIs!
t Find the CIs
t Find relationships between CIs

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11

Which of these Entities should be Configuration Items?

♦ Problem Statement ♦ Source code

♦ Software Project Management Plan ♦ API Specification
(SPMP)
♦ Input data and data bases
♦ Requirements Analysis Document
(RAD) ♦ Test plan
♦ System Design Document (SDD) ♦ Test data
♦ Project Agreement ♦ Support software that is part of the
♦ Object Design Document (ODD) final system
♦ Dynamic model ♦ Support software that is not part of the
♦ Object model product
♦ Functional model ♦ User manual
♦ Unit tests ♦ Administrator manual
♦ Integration test strategy

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12

Page 6
 Possible Selection of Configuration Items

♦ Problem Statement ✔ Source code

♦ Software Project Management Plan ♦ API Specification
(SPMP)
✔ Input data and data bases
✔ Requirements Analysis Document
(RAD) ♦ Test plan
✔ System Design Document (SDD) ✔ Test data
♦ Project Agreement ✔ Support software (part of the product)
✔ Object Design Document (ODD) ♦ Support software (not part of the
♦ Dynamic Model product)
♦ Object model ♦ User manual
♦ Functional Model ♦ Administrator manual
✔ Unit tests
♦ Integration test strategy

Once the Configuration Items are selected, they are usually organized in a tree
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13

Configuration Item Tree (Example)

“The project” CI

Models Subsystems Documents

Object Model Dynamic Model RAD ODD ....

Database User Interface ....

.... Code Data Unit Test ....

“The project”
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14

Page 7
Terminology: Version

♦ The initial release or re-release of a configuration item associated

with a complete compilation or recompilation of the item. Different
versions have different functionality.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15

Terminology: Baseline

“A specification or product that has been formally reviewed and

agreed to by responsible management, that thereafter serves as the
basis for further development, and can be changed only through
formal change control procedures.”

Examples:
Baseline A: All the APIs have completely been defined; the bodies of the
methods are empty.
Baseline B: All data access methods are implemented and tested.
Baseline C: The GUI is implemented.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16

Page 8
More on Baselines
♦ As systems are developed, a series of baselines is developed, usually
after a review (analysis review, design review, code review, system
testing, client acceptance, ...)
w Developmental baseline (CIs: RAD, SDD, Integration Test, ...)
t Goal: Coordinate engineering activities
w Functional baseline (CIs: first prototype, alpha release, beta release)
t Goal: Get first customer experiences with functional system
w Product baseline (product)
t Goal: Coordinate sales and customer support
♦ Many naming scheme for baselines exist (1.0, 3.14159, 6.01a,, ...)
♦ A 3 digit scheme is quite common:
MacOS X 10.3.6

Release Version Revision

(Customer) (Developer) (Developer)
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 17

Managing Baselines in SCM

Baseline A (developmental)

Baseline B (functional, first prototype)

Baseline C (functional, beta test)

Release

How do we manage changes in the baselines?

Time
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 18

Page 9
 Change management

♦ Change management is the handling of change requests

w A change request leads to the creation of a new release
♦ General change process
w The change is requested (this can be done by anyone including users and
developers)
w The change request is assessed against project goals
w Following the assessment, the change is accepted or rejected
w If it is accepted, the change is assigned to a developer and implemented
w The implemented change is audited.
♦ The complexity of the change management process varies with the project. Small
projects can perform change requests informally and fast while complex projects
require detailed change request forms and the official approval by one more
managers.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 19

Controlling Changes

♦ Two types of controlling change:

w Promotion: The internal development state of a software is changed.
w Release: A changed software system is made visible outside the development
organization.

Promotion Release
Policy Policy

Master Software User

Developer Working Repository
Area Promotion Directory Release

♦ Approaches for controlling change (Change Policy)

w Informal (good for research type environments and promotions)
w Formal approach (good for externally developed CIs and for releases)

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 20

Page 10
 Terminology: SCM Directories

♦ Programmer’s Directory (IEEE: Dynamic Library)

w Library for holding newly created or modified software entities
w The programmer’s workspace is controlled by the programmer only
♦ Master Directory (IEEE: Controlled Library)
w Central directory for all promotions
w Manages the current baseline(s) and for controlling changes made to them
w Entry is controlled, usually after verification
w Changes must be authorized
♦ Software Repository (IEEE: Static Library)
w Archive for the various baselines (externally) released for general use
w Copies of these baselines may be made available to requesting
organizations

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 21

Promotion and Release are Operations on CIs

“The project” CI
“The project” CI

promote()
release()

Models Subsystems Documents

Object Model Dynamic Model RAD ODD ....

Database User Interface ....

.... Code Data Unit Test ....

“The project”
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 22

Page 11
Let‘s Create a Model for Configuration Management

We just learned that promotions are stored in the master directory

and releases are stored in the repository

Problem: There can be many promotions and many releases

Solution: Use Multiplicity

* Promotion Release
*
Master
Repository
Directory

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 23

Let‘s Create a Model for Configuration Management

Insight: Promotions and Releases are both versions

Solution: Use Inheritance

Version

* Promotion Release
*
Master Repository
Directory

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 24

Page 12
Let‘s Create a Model for Configuration Management

Problem: A configuration item has many versions

Solution: Create a 1-many association between Configuration Item

and Version
Configuration Item

*
Version

* Promotion Release
*
Master Repository
Directory

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 25

Let‘s Create a Model for Configuration Management

Problem: Configuration items can themselves be grouped

Solution: Use the composite design pattern

Controlled item
Configuration Item
*
*
CM Aggregate Configuration item Version

* Promotion Release
*
Master Repository
Directory

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 26

Page 13
Configuration Item Model (UML Class Diagram)

* Controlled
item
*
Configuration Version
CM Aggregate item

* Promotion Release
*
Master Repository
Directory

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 27

Change Policies

♦ Whenever a promotion or a release is performed, one or more policies apply. The

purpose of change policies is to guarantee that each version, revision or release
conforms to commonly accepted criteria.

♦ Examples for change policies:

“No developer is allowed to promote source code which cannot be
compiled without errors and warnings.”

“No baseline can be released without having been beta-tested by at least

500 external persons.”

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 28

Page 14
Terminology: Version vs Revision vs Release

Version:
w The state of a configuration item or configuration aggregate at a well-
defined point in time.
w It is usually associated with a complete compilation or recompilation of the
item.
w Different versions usually have different functionality.

Revision:
w Change to a version that corrects only errors in the design/code, but does
not affect functionality.

Release:
w A version that has been made available externally.
w The formal distribution of an approved version.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 29

Branch Management

♦ While software is released in a sequential way, the development of

different features can be done by different teams concurrently and
later merged into a single version
♦ A branch identifies a concurrent development path requiring
independent configuration management
♦ The sequence of versions created by each team is a branch, which is
independent from the versions created by the other teams

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 30

Page 15
Example: CVS version identification scheme
Main trunk CVS version identification scheme
<version> ::= <configuration item name>.<version identifier>
<version identifier> ::= <branch>.<revision>
MUE.1.1:Release <branch> ::= <version identifier>.<branch number> |
<branch number>
<branch number> ::= <nonnegative integer>
revised by
<revision> ::= <nonnegative integer>
MUE.1.2:Release derived from

Branch 1.2.1
revised by Branches are
MUE.1.3:Release
identified with
1.2.1.1:Release
the version
they were
merged with revised by
derived from
1.2.1.2:Release followed by a
released as
unique
MUE.2.0:Release
number

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 31

Variant Management
♦ Variants are version that are intended to coexist
w Examples: variants for different platforms, variants released with
multiple levels of functionality

♦ Two approaches to deal with variants

♦ Redundant teams.
w A team is assigned to each variant.
w Each team is given the same requirements and is responsible for the
complete design, implementation, and testing of the variants
w A small number of configuration items are shared across variants
♦ Single project.
w Design a subsystem decomposition that maximizes the amount of code
shared across variants (core subsystems)
w For multiple platforms, core subsystems are lower level subsystems
w For multiple levels of functionality, confine increments of functionality in
mostly independent subsystems
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 32

Page 16
Software Configuration Management Planning

♦ Software configuration management planning starts during the early

phases of a project.

♦ The outcome of the SCM planning phase is the Software

Configuration Management Plan (SCMP) which might be extended
or revised during the rest of the project.

♦ The SCMP can either follow a public standard like the IEEE 828, or
an internal (e.g. company specific) standard.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 33

The Software Configuration Management Plan

♦ Defines the types of documents to be managed and a document

naming scheme.
♦ Defines who takes responsibility for the CM procedures and creation
of baselines.
♦ Defines policies for change control and version management.
♦ Describes the tools which should be used to assist the CM process
and any limitations on their use.
♦ Defines the configuration management database used to record
configuration information.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 34

Page 17
Outline of a Software Configuration Management Plan
(SCMP, IEEE 828-2005)
1. Introduction 4. Schedule (WHEN?)
w Describes purpose, scope of w Establishes the sequence and
application, key terms and coordination of the SCM activities
references with project mile stones.
2. Management (WHO?) 5. Resources (HOW?)
w Identifies the responsibilities and w Identifies tools and techniques
authorities for accomplishing the required for the implementation of
planned configuration management the SCMP
activities 6. Maintenance
3. Activities (WHAT?) w Identifies activities and
w Identifies the activities to be responsibilities on how the SCMP
performed in applying to the will be kept current during the life-
project. cycle of the project.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 35

SCMP Section 1: Introduction

1.1 Simplified overview of the configuration management activities.
1.2 Scope:
w Overview description of the project
w Identification of the CI(s) to which software configuration management
will be applied.
1.3 Identification of other software to be included as part of the SCMP
(support software and test software)
1.4 Relationship of SCM to hardware of system configuration
management activities
1.5 Degree of formality and depth of control for applying SCM to
project.
1.6 Limitations and time constraints for applying SCM to this project
1.7 Assumptions that might have an impact on the cost, schedule and
ability to perform defined SCM activities.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 36

Page 18
SCMP Section 2: Management
2.1 Organization
w Organizational context (technical and managerial) within which the SCM
activities are implemented. Identifies
t All organizational units (client, developers, managers) that participate in an SCM
activity
t Functional roles of these people within the project
t Relationship between organizational units
2.2. Responsibilities
w For each SCM activity list the name or job title to perform this activity
w For each board performing SCM activities, list
t purpose and objectives
t membership and affiliations
t period of effectivity, scope of authority
t operational procedures
3. Applicable Policies
w External constraints placed on the SCMP

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 37

Typical Configuration Management Roles

♦ Configuration Manager
w Responsible for identifying configuration items. The configuration
manager can also be responsible for defining the procedures for creating
promotions and releases
♦ Change control board member
w Responsible for approving or rejecting change requests
♦ Developer
w Creates promotions triggered by change requests or the normal activities
of development. The developer checks in changes and resolves conflicts
♦ Auditor
w Responsible for the selection and evaluation of promotions for release and
for ensuring the consistency and completeness of this release

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 38

Page 19
SCMP Section 3: Activities

3.1 Configuration Identification

3.2 Configuration Control
3.3 Configuration Status Accounting
3.4 Configuration Audits and Reviews
3.5 Interface Control
3.6 Subcontractor/Vendor control
3.7 Release management and delivery

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 39

3.2 Configuration Control

Defines the following steps

3.2.1 How to identify the need for a change (layout of change request form)
3.2.2 Analysis and evaluation of a change request
3.2.3 Approval or disapproval of a request
3.2.4 Verification, implementation and release of a change

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 40

Page 20
3.2.1 Change Request

♦ Specifies the procedures for requesting a change to a baselined CI

and the information to be documented:
w Name(s) and version(s) of the CI(s) where the problem appears
w Originator’s name and address
w Date of request
w Indication of urgency
w The need for the change
w Description of the requested change

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 41

3.2.2 Evaluation of a Change

♦ Specifies the analysis required to determine the impact of proposed

changes and the procedure for reviewing the results of the analysis.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 42

Page 21
3.2.3 Change Approval or Disapproval

♦ This section of the SCMP describes the organiztion of the

configuration control board (CCB).
♦ Configuration Control Board (CCB)
w Can be an individual or a group.
w Multiple levels of CCBs are also possible, depending on the complexity of
the project
♦ Multiple levels of CCBs may be specified.
w In small development efforts one CCB level is sufficient.
♦ This section of the SCMP also indicates the level of authority of the
CCB and its responsibility.
w In particular, the SCMP must specify when the CCB is invoked.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 43

3.2.4 Implementing Change

♦ This section of the SCMP specifies the activities for verifying and
implementing an approved change.
♦ A completed change request must contain the following information:
w The original change request(s)
w The names and versions of the affected configuration items
w Verification date and responsible party
w Identifier of the new version
w Release or installation date and responsible party
♦ This section must also specify activities for
w Archiving completed change requests
w Planning and control of releases
w How to coordinate multiple changes
w How to add new CIs to the configuration
w How to deliver a new baseline

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 44

Page 22
3.3 Configuration Status Accounting

♦ This section of the SCMP must contain the following sections

w What elements are to be tracked and reported for baselines and
changes?
w What types of status accounting reports are to be generated? What
is their frequency?
w How is information to be collected, stored and reported?
w How is access to the configuration management status data
controlled?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 45

3.4 Configuration Audits and Reviews

♦ This section of the SCMP identifies audits and reviews for the
project.
w An audit determines for each Configuration Item if it has the required
physical and functional characteristics.
w A review is a management tool for establishing a baseline.
♦ For each audit or review the plan has to define:
w Objective
w The Configuration Items under review
w The schedule for the review
w Procedures for conducting the review
w Participants by job title
w Required documentation
w Procedure for recording deficiencies and how to correct them
w Approval criteria

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 46

Page 23
Tailoring the SCMP

♦ The IEEE standard allows quite a bit flexibility for preparing an

SCMP.
♦ A SCMP may be
w tailored upward:
t to add information
t to use a specific format
w tailored downward
t Some SCMP components might not apply to a particular project.
t Instead of omitting the associated section, mention its applicability.
t Information that has not been decided on at the time the SCMP is approved
should be marked as “to be determined”.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 47

Conformance to the IEEE Standard 828-2005

♦ Presentation format & Minimum information
w A separate document or a section embedded in another document titled
“Software Configuration Management Plan”.
w 6 Sections: Introduction, Management, Activities, Schedules, Resources
and Plan Maintenance
♦ Consistency Criteria:
w All activities defined in the SCMP (Section 3.1 to 3.6) are assigned to an
organizational unit or person and they are associated with resources to
accomplish the activities.
w All Configuration items identified in Section 2.1 have defined processes for
baseline establishment and change control (Section 3.2) .
♦ If the above criteria are met, the SCMP can include the following
sentence:
“This SCMP conforms with the requirements of IEEE Std 828-2005.”
♦ Note: The consistency criteria can also be used at a SCMP review
meeting

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 48

Page 24
 Example SCM Plans (from the Guide IEEE 1042.1990)

Life-cycle Phase Project Type Size SCM Tools Life Span Writing Character of
Project

A
Complex system
Development Critical Medium Advanced Short Highly contracted to
Structured another company

B Small software
development
Concept Prototype Small Basic Short Informal project
C SCMP used by
Maintenance Support Large On-line Full Structured organization using
Software Life-Cycle contracted SW
D
Development of
All Commercial Small Integrated Full Informal embedded
Life-Cycle applicatåions

ARENA: Concept. Prototype, Small, On-line, Full Life-Cycle, Informal

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 49

Tools for Software Configuration Management

♦ Software configuration management is normally supported by tools
with different functionality.
♦ Examples:
w RCS
t very old but still in use; only version control system
w CVS (Concurrent Version Control)
t based on RCS, allows concurrent working without locking
t http://www.cvshome.org/
t CVSWeb: Web Frontend to CVS
w Perforce
t Repository server; keeps track of developer’s activities
t http://www.perforce.com
w ClearCase
t Multiple servers, process modeling, policy check mechanisms
t http://www.rational.com/products/clearcase/

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 50

Page 25
Tasks for the Configuration Manager (Summary)
SCMP following the IEEE 828-2005 standard

Define configuration items

Define promote /release policy

Define activities and responsibilities

Set up configuration management system

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 51

References

♦ Readings used for this lecture

w [Bruegge-Dutoit] Chapter 13 Configuration Management
w [IEEE Std 828] Software Configuration Management
w [IEEE Std 1042] Guide to Configuration Management Plan (SCMP)
♦ Additional References
w CVS
t Homepage: http://www.cvshome.org/
t Online Documentation: http://www.cvshome.org/docs/manual/cvs.html
w Jikes: Open Source Java Compiler maintained with CVS
t Source tree (read only): http://sourcery.org/jikes/anoncvs.html
t Jikes project portal http://sourcery.org/jikes
w CVSWEB example
t http://stud.fh-heilbronn.de/~zeller/cgi/cvsweb.cgi/

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 52

Page 26
 Summary
♦ Software Configuration Management: Important part of project
management to manage evolving software systems and coordinate
changes to them.
♦ Software Configuration Management consists of several activities:
w Promotion and Release management
w Branch, Variant and Change Management
♦ Public standard for SCM plans: IEEE 828.
♦ The standard can be tailored to a particular project:
w Large projects need detailed plans to be successful
w Small projects should not be burdened with the bureaucracy of detailed
SCM plans
♦ SCM should be supported by tools. These range from
w Simple version storage tools
w Sophisticated systems with automated procedures for policy checks and
support for the creation of SCM documents.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 53

Page 27