Purpose
  • The Promotion Method refers to how artifacts from an individual engineer’s development area are made available for subsystem and system integration, build, testing, and release.

    Concepts: Promotion Method describe some of the benefits and disadvantages associated with the 'Check-In' and 'Private Branch' methods that could be used in the development environment.
Topics
Tool Mentor: Using ClearCase to Check Out and Check In Configuration Items

Assess Promotion Method Suitability To top of page

Purpose
  • To determine the protocol that needs to be followed as components are reviewed, re-worked, ‘promoted’ for sub-system and system level integration. The method also covers how components would be ‘sent-down’ for re-work and subsequent re-integration.

As described in the Concepts: Promotion Method , each promotion method has its relative merits, and could be applied at different times during the course of the project’s lifecycle.

The Promotion on ‘Check-In’ Method could be appropriate in the Inception, Elaboration and Transition phases of the project when the team size is relatively small.

The Private Branch Promotion Method is probably best applied during the Construction Phase as work is developed, tested and integrated in discrete chunks

Select and Enforce the Adopted Promotion Method To top of page

Purpose
  • To communicate the decision of the selected promotion method to all project staff to ensure that work products and practices are synchronized.

The method may need to be enforced through tool support. In this case, tools and scripts could be set up such that a developer cannot access artifacts unless the correct ‘check-ins’ have been made.

Display Rational Unified Process using frames

 

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