Activity: Create Baselines

Purpose To ensure that all developed artifacts are captured and archived, at given points in time, as a basis for further product development.
Input Artifacts: Work Order Project Repository Workspace	Resulting Artifacts: Workspace
Frequency: On-going
Role: Integrator
Tool Mentor: Accessing Rational ClearCase from Rational Rose Comparing and Merging Rational Rose Models Using Model Integrator Creating Baselines Using Rational ClearCase

Workflow Details:

Configuration & Change Management

Change and Deliver Configuration Items

Manage Baselines & Releases

Good candidates for a baseline are the sets of files and directories under version control that are developed, integrated and released together. A baseline identifies one and only one version of a element.

Composite baselines are groupings of baselines delivered by teams working on separate subsystems of the overall project. In the event that multiple teams each deliver a baseline.

Part of the iterative development methodology is to constantly build an executable product. A baseline should be seen as the moving front of development which contains the necessary artifacts for subsequent development. So baselines should be created certainly at the end of each iteration.

Project baselining practices are followed in accordance with the configuration identification, baselining and archiving step defined in Activity: Establish CM Policies.