This glossary includes terms and definitions for IBM Rational ClearCase.
The following cross-references are used in this glossary:
- See refers the reader from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
- See also refers the reader to a related or contrasting term.
To view glossaries for other IBM products, go to the IBM Terminology Web site
An object that tracks the work required to complete a development task. An activity includes a text headline, which describes the task, and a change set, which identifies all versions that developers create or modify while working on the activity.
A versioned object base (VOB) that contains global type objects. Local copies of global type objects can be created in any VOB that has an AdminVOB hyperlink to the administrative VOB that defines the global type object.
An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.
An object that represents a stable configuration for one or more components. A baseline identifies activities and one version of every element that is visible in one or more components.
An object that specifies a linear sequence of versions of an element. Each branch is an instance of a branch type object. build
The ability of a ClearCase build program to fulfill a build request by using an existing derived object instead of creating a new one by executing a build script.
list of versions of elements that are associated with a Unified Change Management (UCM) activity.
A copy of a file that corresponds to a version of an element. See also Version
The action that creates a new version of an element on any branch of its version tree.
ClearCase administrators group
A Windows domain group whose members have superuser access to ClearCase objects.
A network service that allows programs to access versioned object bases (VOBs) and views by name instead of network path.
A ClearCase object that is used to group a set of related directory and file elements within a Unified Change Management (UCM) project. Typically, the elements that make up a component are developed, integrated, and released together. A project must contain at least one component, and it can contain multiple components. Projects can share components.
Configuration specification (config spec)
A set of rules that specify which versions of VOB elements a view selects. The config spec for a snapshot view also specifies which elements to load into the view.