Purpose
  • Projects usually maintain ‘controlled’ versions of a file or subsystem in a central, restricted access, repository. Check-In and Check-Out are the operations that enable development staff to obtain a particular version of an element, make changes to it, and re-submit it to become the latest controlled version. The purpose of this step is to ensure that the 'check-in and check-out' procedure is established and followed.
Input Artifacts:
  • Any Artifact.
 Resulting Artifacts:

  • Any Artifact
Frequency: On-Going
Worker: Any Worker

The primary CM operations performed by any member of the development staff are:

  • Check Out – Grants permission to change an element
  • Check In – Stores a new version of the changed element
  • Add to Source Control – Places a new file or directory under version control, creating the initial version
  • Promote – Submits changes to the integrator.
  • Update – Makes changes made by other developers available to your view.

An implementer will typically work in the following manner:

  1. Checks out the files that need to be changed.
  2. Makes the changes.
  3. Performs unit tests to verify the changes.
  4. Gets the changes approved.
  5. Checks in the changes.
  6. Promote the changes.
 

Display Rational Unified Process using frames

 

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