Unified Change Management (UCM) associates your development
work with activities in a project. This topic outlines the UCM development
cycle.
About UCM
Unified Change Management (UCM) is a process that supports software
project teams in managing their work. UCM uses Rational ClearCase and
(optionally) Rational ClearQuest to
automate the tasks of software configuration management and defect and change
tracking.
Setting Up UCM Work Areas
To use UCM, you must set up one or more work areas. The number
of work areas that you need depends on whether the UCM project you join has
one or more streams.
Managing Visual Studio Projects with ClearCase Views
The Rational ClearCase Client
for Microsoft Visual
Studio .NET provides operations for managing Visual Studio projects and their
associated ClearCase views.
Setting UCM Activities
Before you can check out and modify source files in a UCM view,
you must associate the view with an activity. Setting your view to an activity
assigns any versions of source files you create to the activity change set.
Working on Activities
To work on activities, you modify source files and test your modifications.
If your project is enabled for Rational ClearQuest,
you might have to enter information in your change request management
system to communicate your progress.
Delivering Activities
When you are ready to make one or more activities available to
the project team, prepare your work areas. Then, deliver your activities.
Creating a New Baseline
At regular intervals during a development project, the UCM administrator
creates and recommends new baselines from the integration stream.
Rebasing Work Areas
At appropriate times, the project manager creates baselines in
the project integration stream, incorporating development changes that have
been delivered. After the baseline has been tested and recommended by the
administrator, rebase your development stream to keep your development work
area current with new baselines.