Tool Mentor:
Setting Up the Implementation Model Using Rational ClearCase
Purpose
This tool mentor describes how to create a framework in the development environment for organizing and
storing configuration item artifacts related to the implementation and delivery
of the software product. The physical representation of subsystems in the
development environment defines the "product directory structure" and is, in
effect, the software Implementation Model. This tool mentor explains how to set
up the Implementation Model directory.
Related Rational Unified Process (RUP) information:
Overview
Before beginning to use ClearCase, it's important to know whether you'll
use ClearCase UCM, an out-of-the-box usage model, or base ClearCase,
which provides a set of tools that can be used to construct other usage
models.
This tool mentor is applicable to both ClearCase UCM and base ClearCase
tasks, whereas all of the other ClearCase tool mentors presented in the RUP use the UCM model.
This tool mentor is applicable when running Microsoft Windows.
Terminology
There are some differences between RUP terminology and that used by
ClearCase. The following definitions of tool-specific terminology should help
clarify the differences.
- Activity: A ClearCase activity maps closely to a RUP Work
Order. It is not to be confused with the RUP concept of an Activity.
- Configuration Management: In the context of ClearCase, use of the term Configuration
Management refers to Version Control and Build Management. RUP uses the IEEE
and ISO definitions of Configuration
Management (CM), which also includes Change Management as part of CM.
- Configuration and Change Management: Both ClearCase and Rational
ClearQuest refer to Configuration and Change Management, which is synonymous
with the RUP definition of Configuration
Management. RUP uses these terms synonymously.
- Project: A ClearCase project maps to the RUP Project
Repository.
Tool Steps
To set up the implementation model with Rational ClearCase:
-
Create the Configuration
Management (CM) repositories (ClearCase VOBs) that represent the subsystems defined by your architecture
-
Import existing
files and directories into the repositories to create an initial set of
development configuration items (ClearCase elements)
-
(Optional)
Create an administrative VOB to contain definitions of global type objects used in defining baselines in your
subsystems
Versioned Object Bases (VOBs) store versions of files, directories, and other
objects. They serve as repositories for configuration management information.
To start the VOB Creation Wizard:
- On the Windows task bar, click Start > Programs > Rational
ClearCase Administration > Create VOB.
- The VOB Creation Wizard starts. Follow the steps that are
presented to create a ClearCase VOB. Before beginning, it is helpful to know
VOB naming conventions used by your site or project, and where to place the
VOB storage.
Context-sensitive help is available at each step of the wizard.
- In the remaining steps in the Wizard, do the following:
- Name the VOB and indicate whether it should be a UCM component or
Project VOB (PVOB).
- Specify a VOB storage location.
- Choose Options.
For details
about creating VOBs, see the online help for the ClearCase VOB Creation
Wizard.
For an overview
of setting up VOBs, see the chapter "Setting Up ClearCase VOBs" in the
ClearCase manual Administrator's Guide.
2. Import
existing files and directories into the repositories to create an initial
set of development configuration items (Rational ClearCase elements)
Working within a ClearCase view produced for your project, create the desired
directories within your VOBs and copy existing files into them.
- From
ClearCase Explorer, select the directories and files you want to import.
- Right-click to display a menu of commands and select Add to Source Control.
This creates a ClearCase element for each of the highlighted objects.
For
information on importing large volumes of files, see the clearimport command in the
ClearCase manual Command Reference.
3. (Optional) Create
an administrative VOB to contain definitions of global type objects used in
defining baselines in your subsystems
Optionally, you may want to create an Administrative VOB to contain definitions
of global type objects.
To create an administrative VOB, start the VOB Creation Wizard previously
described in procedure
1 and follow the prompts.
For more
information about working with administrative VOBs, see "Using Administrative VOBs and Global Types" in the
ClearCase manual titled Administrator's Guide.
Copyright
© 1987 - 2001 Rational Software Corporation
|