Rational Unified Change Management with ClearQuest

Posted on Jan 31 2008 - 3:16am by Raj

Rational Software offers Unified Change Management (UCM) as the best approach for managing change during software system development from requirements to release.

Rational Unified Change Management with ClearQuest

What Is Unified Change Management?

Rational Software offers Unified Change Management (UCM) as the best approach for managing change during software system development from requirements to release.

  • UCM helps software teams manage change in software development, from requirements to release.
  • ClearCase LT and ClearQuest are the foundations for UCM. ClearCase LT manages the artifacts associated with a software development project. ClearQuest manages the project activities. It offers charting and reporting features to track and communicate project progress to all stakeholders.
  • Under UCM, team members use ClearCase LT to manage artifacts under source control, they work on activities in their personal development workspaces, and deliver modified artifacts to the integration stream after they complete an activity.

UCM focuses on these guiding concepts:

  • A UCM activity represents the work required to complete a development task.UCM activities can be derived from a variety of sources, including a defect or an enhancement request.
  • An artifact is an item that is produced, modified, or used in the software development lifecycle as the result of performing an activity. In the Rational Unified Process (RUP), the artifacts produced in one activity are often used as input into other activities. Conceptually, artifacts can be requirements,visual models, test cases, source code, documentation, or project plans. Artifacts are items that are critical to the success of your project and should be placed under configuration management, or version control. Usually, an artifact is represented by
    a file or a set of files.The key strength of UCM is that it unifies the activities used to plan and track software development progress with the artifacts used to create, design, and build software applications. Figure 11 shows a typical way to manage change using UCM.

UCM Tools

A key aspect of the UCM model is that it unifies the activities used to plan and track project progress and the artifacts undergoing change. The UCM model is realized by both process and tools. Rational ClearQuest and Rational ClearCase LT provide tool support for UCM. For example, ClearQuest manages the project’s tasks, defects, and requests for enhancements (referred to generically as activities), and ClearCase LT manages the artifacts produced by a software project. When used together, these tools
help your software team better manage changing requirements and development complexity throughout the software development lifecycle.
Rational ClearQuest. Manages change activity associated with software development, including enhancement requests, defect reports, and documentation modifications.
ClearQuest also offers charting and reporting features to track and communicate project progress to all stakeholders.
Rational ClearCase LT. Uses the built-in UCM development process to track and manage changes to all software project files, including requirements, visual models, and source code.

Using the Tools with UCM – ClearQuest and ClearCase LT
We typically use UCM with ClearQuest and ClearCase LT
as follows:

1 [one time] A project manager or administrator installs Rational software. This individual sets up the ClearQuest and ClearCase LT environments, and creates a Rational project. (A Rational project associates the data created and maintained by Rational tools and enables integrations among them.) A project manager also creates a UCM project to associate with the Rational project.
2 [one time] You identify yourself to the project by joining the project. As a result, a private workspace (consisting of a development stream and a development view) is created for you. You also gain access to a workspace available to your entire team.
This public workspace includes an integration stream; you can create a companion integration view for your own use.
You use a view to select one version of each element in your workspace. In UCM,your stream provides these configuration instructions to the view and tracks your activities. When you join a project, UCM automatically configures your stream so that you see the right version for your workspace.
3 Your project manager uses ClearQuest to assign activities to you.
4 You run a ClearQuest query to find the activities assigned to you. This is your to-do list. From this list, you decide which activity to work on.
5 You work with artifacts as usual. You use ClearCase LT in your private workspace to:
❑ Check out artifacts. When you check out an artifact, ClearCase LT asks which
activity you want to work on. In the background, ClearCase LT keeps track of
the change set (the list of changed artifacts) associated with the activity.
❑ Edit and verify the changes.
❑ Check in the artifacts. When you check in an artifact, it is still part of your
private workspace. Your change does not become publicly available until you
deliver it, as described in Step 6.
6 After you finish work on the activity, you deliver changes for the entire activity . Because ClearCase LT keeps track of the change set, you don’t have to specify the list of artifacts to deliver. Delivering the changes makes the changes publicly available through the integration stream. It can also close the activity, depending on the policies the project manager has established.
7 After developers deliver a set of activities, the project manager makes a baseline, a new common starting place for all developers that includes the new activities or modified artifacts. On your project, a new baseline can be created regularly, perhaps even daily.
8 If the changes in the baseline are approved (through testing or through 
review process), the project manager promotes it, making it the recommended baseline.
9 You rebase your development stream (work area) so that when you work on your next activity, you start from the most recent recommended baseline. Restart with Step 4 to select the next activity to work on.Depending on the structure of your organization, your team may identify these roles
using different names, assign the responsibility of different roles to be performed by one individual rather than several, or share the responsibility of a single role among several team members, as defined by the Unified Process for UCM. No matter how your team is structured, you can use UCM successfully because the model follows a basic process for configuration and change management, and ClearCase LT helps to automate much of the artifact and activity auditing.

For More Information

To learn how to use ClearCase LT, start with the ClearCase LT tutorial. Go to
Start > Programs > Rational Software > Rational ClearCase > Tutorial. In the Help Topics window, double click Tutorial and then double click
Rational ClearCase Tutorial.
For more information about using Rational ClearCase LT and UCM with Rational Suite, read Using Unified Change Management with Rational Suite.
For general information about Rational ClearCase LT with or without UCM, read the Rational ClearCase LT Introduction.

About the Author

Leave A Response