The Full Wiki

More info on IBM Rational ClearCase UCM

IBM Rational ClearCase UCM: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

Unified Change Management (UCM) is the object-oriented realization of ClearCase, a set of software tools typically supporting the process area software configuration management. UCM is activity based. The activity object is the basis for sharing information between ClearCase and ClearQuest. In ClearQuest, the activity presents itself as a task on the developers “to do list” query. In ClearCase, the activity connects the task with the actual files that need changing to accomplish the task (the change set.) A new baseline consists of the old baseline plus all checked-in activities to date. By looking at the change sets of those activities, it is possible to know every file that was touched in order to arrive at a new baseline.

UCM is also component-based, meaning that units of code that are developed and built together can be kept isolated until time to integrate with the full codeline. Each UCM component can each have its own recommended baseline and a set of component baselines can be used to define the fully integrated main product baseline.

UCM is also project-based, meaning that each codeline can have its own custom set of development policies and can spawn new projects by using its final baseline as a jumping off point for future development. UCM is a layer built on Rational ClearCase to provide additional software configuration management features. These changes include integration with ClearQuest to enforce defect and change tracking with code development through the use of activities. This is part of the Rational Unified Process which describes the lifecycle of change management for IBM Rational's software development process. It also gives integrators ownership of projects and streams to allow policy and feature management by project leaders and release engineers. UCM removes the ability/requirement that users manage a configuration specification for a view. UCM is used and configured via either CLIs or GUIs.



Project Versioned Object Bases store UCM metadata. All UCM structures reside in PVOBs.


Projects group similar components into a code base used to build software. Project policies can be applied to enforce a process for users working within the project.


One or more components can be configured per base ClearCase VOB. A component can be a part of multiple projects and streams, allowing for code reuse.


Streams are created within a project to allow users to work on content simultaneously in isolated environments within views. Code changes are integrated from one stream to another analogously to branches in base ClearCase. A stream also allows for development of several simultaneous releases of a product to take place.


A baseline is applied to a set of components within a stream and serves analogously to base ClearCase labels.


Element versions can be grouped into an activity change set. An activity can be enforced with ClearQuest checking criteria to allow tight integration of defect tracking with code development.

External links



Got something to say? Make a comment.
Your name
Your email address