Glossary
This glossary provides terms and definitions for HCL VersionVault.
The following cross-references are used in this glossary:
- See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
- See also refers you to a related or contrasting term.
A
- activity
- 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.
- administrative VOB
- 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.
- artifact
- A physical piece of information that is used or produced by a software development process. Examples of artifacts include models, source files, scripts, and binary executable files.
- An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.
B
- baseline
- 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.
- branch
- An object that specifies a linear sequence of versions of an element. Each branch is an instance of a branch type object.
- build
- The process during which a build program produces one or more derived objects. This may involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on.
- build avoidance
- The ability of an HCL VersionVault build program to fulfill a build request by using an existing derived object instead of creating a new one by executing a build script.
C
- change set
- A list of versions of elements that are associated with a Unified Change Management (UCM) activity.
- checked-out version
- A copy of a file that corresponds to a version of an element. See also version.
- checkin
- The action that creates a new version of an element on any branch of its version tree.
- component
- A VersionVault 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.
- config spec
- See configuration specification.
- 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.
D
- delivery operation
- 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.
- derived object (DO)
- A type of output created by a VersionVault build in a dynamic view.
- development stream
- An 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.
- DO
- See derived object.
- dynamic view
- A view that uses a network file system to access versions of elements.
E
- eclipsed
- Pertaining to an object in a versioned object base (VOB) that is not visible because another object with the same name is currently selected by the view.
- element
- An object that encompasses a set of versions, organized into a version tree.
- element type
- A property of an element that specifies how versions of that element are constructed.
- environment
- A specific instance of a configuration of hardware and software.
- extended namespace
- An extension of the standard Windows or Linux file system that allows access to versions of elements.
F
- foundation baseline
- A baseline that configures a stream. Foundation baselines specify the versions and activities that appear in a view.
H
- hijacked file
- A version of an element in a snapshot view or a web view that is modified but not checked out.
- history
- Metadata in a versioned object base (VOB) that consists of event records for objects in that VOB.
I
- installation
- The process of adding a hardware or software component to a computing environment.
L
- label
- An instance of a label type object, which provides a user-defined name for a version. See also object.
- label type
- A type object that defines a version label for use within a versioned object base (VOB).
- load
- To copy a version of an element to a snapshot view or web view.
- load rule
- 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.
M
- main branch
- The starting branch of a version tree of an element. The default name for this branch is main.
- master replica
- In HCL VersionVault MultiSite, the replica at which a mastered object can be modified or instances of the object can be created.
- mastership
- The ability to modify an object or to create instances of an object in a replica.
- metadata
- Data that describes the characteristics of data; descriptive data.
- multiversion file system (MVFS)
- A file system that supports dynamic views.
- MVFS
- See multiversion file system.
N
- nodelocked license
- A type of license that is assigned to a named user or agent. The nodelocked license is installed on the workstation for which it was created.
O
- object
- An item stored in a versioned object base (VOB). An object can be identified by an object-selector string, which includes a prefix that indicates the kind of object, the object's name, and a suffix that indicates the VOB in which the object resides. Examples: lbtype:REL1@/vobs/vega on Linux and lbtype:REL1@\vega on Windows See also label.
- object registry
- A networkwide database that records the storage locations of all versioned object base (VOB) storage directories and all view storage directories.
- orphaned element
- An element that is no longer cataloged in any version of any directory. Such elements are moved to the lost+found directory of the versioned object base (VOB).
P
- platform
- The combination of an operating system and hardware that makes up the operating environment in which a program runs.
- Any base of software technologies on which applications or services can be provided; for example, the Eclipse platform.
- project
- An object that contains configuration information, activities, and policies required to manage a development effort.
- project VOB (PVOB)
- A versioned object base (VOB) that stores Unified Change Management (UCM) objects, such as projects, streams, activities, and change sets.
- PVOB
- See project VOB.
Q
- query
- A request for information from a database that is based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than USD1000.
R
- rebase
- A VersionVault operation that makes a development work area current with the set of versions represented by a more recent baseline in another stream, usually the project's integration stream or a feature-specific development stream.
- replica
- An instance of a versioned object base (VOB) located at a particular site.
S
- scrubbing
- The removal from VOB and view storage directories of files that are no longer needed.
- snapshot view
- A view that uses a local file system to access versions of elements.
- stream
- An object that specifies configuration rules for a UCM view.
T
- trigger
- A monitor that specifies one or more standard programs or built-in actions to be executed whenever a certain VersionVault operation is performed.
- type
- An object that defines a data structure.
U
- UCM
- See Unified Change Management.
- Unified Change Management (UCM)
- A process for organizing software development teams and their work products. Members of a project team use activities and components to organize their work.
V
- version
- An object that implements a particular revision of an element. The versions of an element are organized into a version tree structure. See also checked-out version.
- versioned object base (VOB)
- A repository that stores versions of file elements, directory elements, derived objects, and metadata associated with these objects.
- version tree
- A graphic representation of a versioned object that shows all branches and the versions on each branch.
- VersionVault administrators group
- A Windows domain group whose members have superuser access to VersionVault objects.
- VersionVault registry
- A network service that allows programs to access versioned object bases (VOBs) and views by name instead of network path.
- view
- A VersionVault object that provides a work area for one or more users. For each element in a VOB, a view's configuration specification selects one version from the element's version tree.
- view-private object
- A file or directory that exists only in a particular view and is not under version control.
- VOB
- See versioned object base.
- VOB database
- The part of a versioned object base (VOB) storage directory in which metadata and VOB objects are stored.
- VOB family
- The set of replicas of a particular versioned object base (VOB).
W
- wink in
- To cause a shareable derived object to appear in a view, even though its file system data is actually located in a VOB's derived object storage pool.