Purpose

Subsystems, when they reach a specified level of maturity, are baselined, and then available for reuse in subsequent project iterations and/or other projects. Deliverable files are placed under version control (staged) in a separate location (staging VOB). This Tool Mentor describes how to baseline a subsystem, stage deliverable files, and make the subsystem available for reuse.

Related Rational Unified Process activity:

Activity:  Release Subsystem(s)

Overview

This Tool Mentor is applicable when running Windows NT 4.0.

To use ClearCase to set up a staging process:

  1. Create a VOB to store project deliverables.
  2. Edit your build scripts to copy the deliverable files from the source VOBs to the staging VOB and check them in.

To use ClearCase to baseline a subsystem and make the subsystem available for reuse:

  1. Create the label type for the baseline, then apply the label to the stable set of versions in the source VOBs and to the deliverables in the staging VOB.
  2. Notify the users that the subsystem is available and tell them which label to use when reconfiguring their views to use the new version of the subsystem.

Tool Steps

  1. Create a VOB to store project deliverables.
  2. For details about creating VOBs, see Setting Up ClearCase VOBs in the ClearCase Administrator's Manual.

  3. Edit your build scripts to copy the deliverable files from the source VOBs to the staging VOB and check them in.
  4. Create the label type for the baseline, then apply the label to the stable set of versions in the source VOBs and to the deliverables in the staging VOB.
  5. See Tool Steps in Using ClearCase to Baseline the Product for instructions on creating and applying labels.

  6. Notify the users that the subsystem is available and tell them which label to use when reconfiguring their views to use the new version of the subsystem.
 

Display Rational Unified Process using frames

 

© Rational Software Corporation 1998 Rational Unified Process 5.1 (build 43)