A VersionVault UCM 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. When working on a version, developers must associate that version with an activity.
A VersionVault UCM object that typically represents a stable configuration for one or more components. A baseline identifies activities and one version of every element visible in one or more components. Developers can create a development stream or rebase an existing development stream from a baseline.
A VersionVault object that you use to group a set of related directory and file elements within a 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.
A baseline that selects baselines from other components. A composite baseline is created by creating dependency relationships between the component that stores the composite baseline and the components whose baselines are selected by the composite baseline.
A VersionVault operation in which developers merge the work from their own development streams to the project’s integration stream or to a feature-specific development stream. If required, the deliver operation invokes the Merge Manager to merge versions.
A VersionVault UCM object that determines which versions of elements appear in a development view and maintains a list of a developer’s activities. The development stream configures the development view to select the versions associated with the foundation baselines plus any activities and versions that developers create after they join the project or rebase their development stream.
A view associated with a UCM development stream. A development view can be either a dynamic view or a snapshot view.
A property of a stream. Foundation baselines specify the versions and activities that appear in your view. As part of a rebase operation, foundation baselines of the target stream are replaced with the set of recommended baselines from the source stream.
A baseline that is created by recording all versions below the component’s root directory. Generally, full baselines take longer to create than incremental baselines; however, VersionVault can look up the contents of a full baseline faster than it can look up the contents of an incremental baseline.
A version in a snapshot view that is modified but not checked out. By default, a non-checked-out version in a snapshot view is given the file attribute of read-only. If you change this attribute and modify the file, you have hijacked the file by taking it out of direct VersionVault control.
A baseline that is created by recording the last full baseline and those versions that have changed since the last full baseline was created. Generally, incremental baselines can be created much faster than full baselines; however, VersionVault can look up the contents of a full baseline more quickly.
A branch that contains versions available to all members of a team. A developer often works on a private branch. To make private work available to others, the developer merges versions on the private branch with versions on the integration branch.
A VersionVault UCM object that enables access to versions of the project’s shared elements. A project contains only one integration stream, which maintains the project’s baselines. The integration stream configures integration views to select the versions associated with the foundation baselines plus any activities and versions that have been delivered.
A view attached to a UCM project’s integration stream or a feature-specific development stream. An integration view is used to build and test the latest work delivered to the stream. An integration view can be either a dynamic view or a snapshot view.
An instance of a label type object, supplying a user-defined name for a version. See also object, metadata.
A type object that defines a version label for use within a VOB.
To copy a version of an element to a snapshot view and keep track of the checkins, updates, and other VersionVault operations that affect the element.
A statement in the config spec that specifies an element or subtree to load into a snapshot view. Config specs can have more than one load rule.