UCM

UCM or Unified Change Management is a layer built on top of Rational ClearCase to provide several features to this Configuration Management System for software development. These changes include integration with ClearQuest to enforce defect and change tracking with code development through the use of activities. It also gives integrators ownership of projects and streams, to allow policy management and feature management from a higher level than developers. UCM removes the ability/requirement that users manage a configuration specification for a view. Most configuration and usage of UCM can be done through a command line or graphical user interface.

Project

A project groups similar components together into a code base used to develop a software product. Rules or policies can be set up on the project enforcing a process of users working within the project.

PVOB

Also known as a project versioned object base was introduced to store metadata for UCM. All structures (project, streams, baselines, activities) will refer to a PVOB when referenced.

Component

One or more components can exist in a base ClearCase VOB. A component can be a part of multiple projects and stream allowing for code reuse.

Stream

Streams are created within a project to allow users to work on content simultaniousely in isolated environments within views. A stream is similar to a branch in base ClearCase where code is delivered from one stream to another when integrating code. A stream also allows for development of several releases of a product development to take place.

Baseline

A baseline replaces a label in base ClearCase. A baseline is applied to a set of vobs within a stream which actually labels

Activity

Element changes can be grouped together and associated with reason checking criteria into an activitiy. An activity can be enforced with ClearQuest reason checking criteria allowing bug tracking to be tightly integrated with code development.

External links

• IBM's Unified change management site