To add any change set to a repository workspace, such as a change set attached to a work item.

An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.

A defined quality and values that can be assigned to an artifact. For example, an work item artifact might have an 'priority' or 'severity' attribute.

A permanent copy of a component in a particular repository workspace or stream. A component baseline represents a configuration of a component at a particular point in time.

A group of related changes to files for folders in a workspace or stream.

A change set that can no longer be changed.

A grouping of related artifacts in a stream or repository workspace. A component can contain any number of folders and files.

A discrepancy among change sets in a repository workspace.

A Web user interface component that provides information about the project status at a glance. Users can view project summary information or more detailed information.

To conduct an outgoing flow of change sets and baselines from a repository workspace to a stream.

An arrangement between two workspaces or between a workspace and a stream that enables users to deliver and accept change sets.

A source or destination of incoming and outgoing change sets. In a team setting, most workspaces have flow targets. Streams have flow targets only if they are part of a stream hierarchy.

A change set in a stream or repository workspace that flows to a user repository workspace. An incoming change set is present in a workspace flow target, but not in the workspace itself.

An artifact that shows the work items and additional unstructured information for a team or project area within a development phase.

A relationship between two artifacts.

A change set in the developer workspace that flows to a stream. An outgoing change set is present in a workspace, but not in one or more of the workspace flow targets.

A process by which changes that users make to work items are propagated to the ClearQuest user database.

In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.

The representation of a software project, including the project area defines the project deliverables, team structure, process, and schedule.

An artifact that shows plan items and additional unstructured information for a team or project area and all related child team areas and iterations.

A subset of a baseline that identifies artifacts that have been approved or assigned to a milestone or other meaningful event.

A workspace that holds a developer's private copy of the source file base.

To reconcile discrepancies among change sets in a repository workspace.

To reinstate a previously suspended change set to a repository workspace.

In IBM® Rational Team Concert™, the component that you use to manage source code, documents, and other artifacts that you want to place under version control and share with a team. Rational Team Concert source control is closely integrated with the other application development lifecycle tools included in Rational Team Concert.

An artifact that holds the master copy of a source file base.

To temporarily remove a change set from a repository workspace.

To add, subtract, or change one feature or artifact to match another.

An identifer that groups related artifacts.

A place within a project area for managing team membership, roles, assignments, and team artifacts.

An artifact showing plan items and additional unstructured information for a team or project area and a development iteration and the associated child iteration plans.

A Web user interface widget that is added and displayed in a dashboard page.

An artifact representing a generalized notion of a development task, such as a task, defect report, or enhancement request.

A source or destination of incoming and outgoing change sets.

A record that captures the contents of a repository workspace at a particular time. A workspace snapshot consists of a collection of baselines, one for each component in the repository workspace.