WebSphere Issues


IBM Rational Clear Case (UCM) basic concepts

Filed under: Java, programming, Rational — Tags: , , , — Ishtiaque @ 12:53 pm
  • SCM : Software Configuration Management is about managing change to software
  • UCM Unified Change Management is IBM’s solution for managing change across the development lifecycle using Rational brand tools. UCM integrates a project’s activities with the software artifacts being changed through a defined, repeatable process.
  • ClearCase : It’s a robust software artifact management tool that provides automated parallel development.
  • ClearQuest : It’s is a flexible, customizable defect and change-tracking application.
  • Activity : An activity represents a unit of work in your UCM project, for example: Defect Fix, New Feature or Enhancement Request.
  • Element : An element is an artifact under source control; it can be a file, or a directory element. For example html, xml, .java, .sql etc
  • Version: Each revision of an element is called a version. An element encompasses the entire set of versions of the artifact.
  • Component: UCM manages the large number of artifacts by collecting related files and directories into a component, an entity that can be managed as a whole.
  • Baseline: A baseline is a stable configuration of one or more components. At the beginning of a project, a configuration manager creates an initial baseline. It identifies one version of each element to be used by developers as a starting point for their development.
  • Project: An object that contains configurations and policies relating to a development effort to create a Product, Group of products, Subset of a product’s functionality
  • VOB: ClearCase stores element versions and components in a repository called a Versioned Object Base (VOB).
  • PVOB: ClearCase stores objects associated with the project in a repository called a Project VOB (PVOB)
  • Development Stream: The development stream contains activities and a baseline that configure which versions of elements appear in the development view. The stream does not necessarily select versions of all elements. Development streams isolate a developer’s changes until the changes are ready to be integrated. Development streams enable parallel development to occur.
  • Development View: Contains the versions appropriate for implementing your activities. Selects zero or one version of each element. Is configured to look at a single stream.
  • Integration Stream:  The main shared stream of a UCM project, typically created and maintained by the project manager. Its primary functions are to: Enable access to versions of the project’s shared elements, Share the results of each developer’s completed activities, Maintain baselines created at various points in time during the development effort.
  • Integration View: Each developer has an integration view that is associated with the project’s integration stream. The developer uses this view to build and test the latest versions of a project’s shared elements.
  • Activity: Changes to artifacts stored in ClearCase are linked to UCM activities. The activity keeps track of: Which artifacts are created or modified as you work on the activity, The stream in which the activity is located, Whether the activity is currently set in any view.
  • Rebase: It brings changes in a baseline from the integration stream to your development stream. Deliver brings activities from your development stream to the integration stream. Before you start a rebase operation, check in all files and directories in your development view. You cannot start a rebase operation from a view that contains checkouts.
  • Deliver: Deliver brings activities from your development stream to the integration stream.
  • Hijacked File: A hijacked file is a file loaded in your view that has been modified without first being checked out. You can hijack a file by disabling the read-only attribute in File Properties or by a explicit command in ClearCase Remote Client.




Blog at WordPress.com.

%d bloggers like this: