Glossary

Glossary

access control

Access control regulates which user groups are permitted to perform tasks (methods) with CA Harvest SCM objects. Each securable object in CA Harvest SCM has a list of methods associated with it; each user group can be assigned access to any of the method-object combinations.

administrator

An administrator is a CA Harvest SCM user belonging to the Administrator group. Administrators can perform all actions in CA Harvest SCM without access checks. An administrator typically initializes, activates, set ups, and assigns users to CA Harvest SCM. The administrator also defines life cycles, sets up access control, and performs repository recovery operations when necessary.

baselining

Baselining is the beginning of a life cycle from a point in an existing life cycle. Baselining lets groups begin development for a new release from the end of the previous release, or from a significant point in a continuing development cycle.

change

A change is a modification to an application that requires traceability and review.

concurrent update

Concurrent update is a mode of the check-out process that creates reserved versions of branches for the specified package. Branching can be used to support concurrent development, letting more than one package check out an item for update at the same time or more than one view to update an item.

context

A context is a collection of CA Harvest SCM settings, including, state, package, check-in process, check-out process, and view path. A context is used by CA Harvest SCM to determine necessary properties such as view path, and which change package to check in to.

get

A get from repository is a procedure used when performing an incoming synchronization. Performing a get from repository on a resource creates it in the local workspace if it does not exist, updates it if has changed, or deletes it if it was removed from the server. If the resource is a folder, the get from repository is performed on every resource under the folder as well.

item

An item is a component of a repository containing the actual information that makes up a software application. Items are the units of information modified by developers, analogous to operating system files. A versioned item represents many versions of a file. It has an initial version and it can have many versions on the trunk or on branches.

item path

An item path is a conventional way of referring to the equivalent of directories in the CA Harvest SCM repository, to distinguish them from directories in the external file system.

life cycle

A life cycle is the set of all the stages a change or release goes through from identification to completion. A life cycle is made up of states and processes.

package

A package is a CA Harvest SCM object that groups a set of changes together. A package is the fundamental unit of work in the CA Harvest SCM life cycle.

process

A process is a unit of work in CA Harvest SCM. Processes can be added to states or linked to other processes. Linked processes execute automatically; processes in states are optional. CA Harvest SCM provides a number of processes like concurrent merge, promote, and demote.

project

A project refers to the entire management framework in CA Harvest SCM that supports a particular development or maintenance activity. You can have many different projects, depending on the applications being controlled and the kind of development activity. A project includes information about how changes progress through the development life cycle, the activities that can occur, what data to access, and user responsibilities.

recursive

Recursive describes a function that starts at one level and continues down until no more levels exist. CA Harvest SCM provides a recursive option for check-in and check-out. When this option is selected, all files and directories below a specified directory can be included in a check-in operation, or all items and paths below a specified view path can be included in a check-out operation.

repository

A repository is a hierarchical collection of versioned items. It could include all the code for an application or only a module.

state

A state is part of the life cycle where a series of activities take place to correct a problem.

tag

A tag is an informative attribute associated with a version and displays in Repositories view and Lists view. Reserved, removed, and merged versions are tagged.

version

A version is a variation or edition of a CA Harvest SCM item. Versions are created when changes are made to an item, primarily through the check-out and check-in processes. A version represents the initial item and all changes associated with previous versions in its line of descent.

view path

A view path is a conventional way of referring to the equivalent of directories in the CA Harvest SCM repository, to distinguish them from directories in the external file system. When a view path is set, only resources below that path are visible. For this reason, a set view path is known as a view path anchor. All folders directly under the view path anchor are considered to be projects.