Tool Mentor: Using ClearCase to Set Up the Implementation Model

Purpose

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 describes how to set up the Implementation Model directory.

Related Rational Unified Process activity:

• Activity: Structure the Implementation Model.

Overview

This Tool Mentor is applicable when running Windows NT 4.0.

To set up the implementation model with ClearCase:

1. Create the CM repositories (ClearCase VOBs) that represent the subsystems defined by your architecture.
2. Import existing files and directories into the repositories to create an initial set of development configuration items (ClearCase elements).
3. (Optional) Create an Admin VOB to contain definitions of global type objects to be used in defining baselines in your subsystems.

For a complete ClearCase-specific overview of this topic, see Establishing the Initial CM Environment in the paper Organizing and Managing Software Projects Using ClearCase on Windows.

Tool Steps

1. Create the ClearCase VOBs that represent the subsystems defined by your architecture.

   For details about creating VOBs, see Setting Up ClearCase VOBs in the ClearCase Administrator’s Manual.

2. Import existing files and directories into the repositories to create an initial set of ClearCase elements.

   Working within a ClearCase view created for your project (see Creating a Workspace for information on creating views), create the desired directories within your VOBs and copy existing files into them. Using the Windows Explorer, select the directories and files you wish to import and use the Add to Source Control ClearCase command (found by right-clicking) to create the corresponding ClearCase elements. If you are importing large volumes of files, see the clearimport command in the ClearCase Reference Manual.

3. (Optional) Create an Admin VOB to contain definitions of global type objects to be used in defining baselines in your subsystems.

   For more information about working with Administrative VOBs, read about Administrative VOBs and Global Types in the ClearCase Administrator’s Manual.