Project-level objects are specific to a single project. The following objects are specific to a single CA Harvest SCM project:
state
A state is a distinct phase in the life cycle in which certain activities can take place as packages move from definition to completion. A life cycle can include several states.
process
A process is an action that can be executed on an object in CA Harvest SCM. The processes defined for a state determine what activities can be performed in that state.
package
A package is the basic unit of work that moves through a life cycle. It typically represents a problem or a request that needs to be tracked, the changes made in response to the problem or the request, and any other associated information. The package is the user's link to the actual data accessed during the change process. Each package resides in a particular state of the life cycle.
package group
A package group is one or more packages, which are usually related. A package can belong to one group, several groups, or no groups. Any operation that can be performed on a package can be performed on all packages in a package group.
baseline
A baseline defines the repository items available to a project. A baseline can include items from more than one repository, as in the case of shared code.
view
A view determines what items specific users or user groups can access and view in repositories. A state is usually associated with a view. The view determines which item versions are accessible to users operating in a state using that view. Administrators can define a state without a view, if users do not need access to data items. For example, an initial state named Open, which is simply a holding area for newly created change requests would not need a view.
working view
A working view defines where users can access specific items. Administrators associate working views with one or more states. Several states can share the same working view, but a state cannot use more than one working view. The working view determines which item versions are accessible to users.
snapshot view
A snapshot view is a read-only image of a working view at a specific point in time. Snapshots let you capture a data inventory at significant points in the software's development, such as a release. After you create a snapshot, you can use it to create a baseline.
version
A version is an iteration of an item. Each item in a repository consists of versions of the item. Versions are visible to users only through views. The views for a state in the Workbench display versions in the project baseline view and the state's working view.
|
Copyright © 2013 CA.
All rights reserved.
|
|