16.1 Project Overview

Release 2.0 development of the monet project includes the following kinds of work:

These three development efforts can proceed largely in parallel (Figure 50), but critical dependencies and milestones must be considered:

Figure 50 Project Plan for Release 2.0 Development

The plan uses a baseline-plus-changes approach. Periodically, developers stop writing new code, and spend some time integrating their work, building, and testing. The result is a baseline: a stable, working version of the application. ClearCase makes it easy to integrate product enhancements incrementally and frequently. The more frequent the baselines, the easier the tasks of merging work and testing the results.

After a baseline is produced, active development resumes; any new efforts begin with the set of source versions that went into the baseline build.

You define a baseline by assigning the same version label (for example, R2_BL1 for Release 2.0, Baseline 1) to all the versions that go into, or are produced by, the baseline build.

The project team is divided into three smaller teams, each working on a different development effort: the MAJ team (new features), the MIN team (minor enhancements), and the FIX team (Release 1.0 bug fixes and patches).

NOTE: Some developers may belong to multiple teams. These developers work in multiple views, each configured for the respective team's tasks.

The development area for the monet project is shown here. At the beginning of Release 2.0 development, the most recent versions on the main branch are labeled R1.0.

\monet

(project top-level directory)

src\

(sources)

include\

(include files)

lib\

(shared libraries)