IBM SC34-4499-03 manual Glossary, 313, Compare to, Contrast with, See also

Glossary

This glossary includes terms and de®nitions from the IBM Dictionary of Computing, 10th edition (New York: McGraw-Hill, 1993). If you do not ®nd the term you are looking for, refer to this document's index or to the IBM Dictionary of Computing.

This glossary uses the following cross-references:

Compare to

Indicates a term or terms that have a similar but not identical meaning.

Contrast with

Indicates a term or terms that have an opposed or substantially different meaning.

See also

Refers to a term whose meaning bears a relationship to the current term.

A

absolute path name. A directory or a part expressed as a sequence of directories followed by a part name beginning from the root directory.

access list. A set of objects that controls access to data. Each object consists of a component, a user, and the authority that the user is granted or is restricted from in that component. See also authority, granted authority, and restricted authority.

action. A task performed by the TeamConnection server and requested by a TeamConnection client. A TeamConnection action is the same as issuing one TeamConnection command.

agent. See build agent.

alternate version ID. In collision records, the database ID of the version of a driver, release, or work area where the con¯icting version of a part is visible.

approval record. A status record on which an approver must give an opinion of the proposed part changes required to resolve a defect or implement a feature in a release.

approver. A user who has the authority to mark an approval record with accept, reject, or abstain within a speci®c release.

approver list. A list of user IDs attached to a release, representing the users who must review part changes that are required to resolve a defect or implement a feature in that release.

attribute. Information contained in a ®eld that is accessible to the user. TeamConnection enables family administrators to customize defect, feature, user, and part tables by adding new attributes.

authority. The right to access development objects and perform TeamConnection commands. See also access list, base authority, explicit authority, granted authority, implicit authority, restricted authority, and superuser privilege.

B

base authority. The set of actions granted to a user when a user ID is created within a TeamConnection family. See also authority. Contrast with implicit authority and explicit authority.

base name. The name assigned to the part outside of the TeamConnection server environment, excluding any directory names. See also path name.

base part tree. The base set of parts associated with a release, to which changes are applied over time. Each committed driver or work area for a release updates the base part tree for that release.

build. The process used to create applications within TeamConnection.

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 313