Filter
Top Products
v The work area or driver’s release
v Another work area
TeamConnection generates a collision record
when a user attempts to replace an older version
of a part with a modified version, another user has
already modified that part, and the first user’s
modification is not based on this latest version of
the part.
command. A request to perform an operation or
run a program from the command line interface. In
TeamConnection, a command consists of the
command name, one action flag, and zero or
more attribute flags.
command line. (1) An area on the Tasks window
or in the TeamConnection Commands window
where a user can type TeamConnection
commands. (2) An area on an operating system
window where you can type TeamConnection
commands.
committed version. The revision of a part that is
visible from the release.
common part. A part that is shared by two or
more releases, and the same version of the part is
the current version for those releases.
comparison operator. An operator used in
comparison expressions. Comparison operators
used in TeamConnection are > (greater than), <
(less than), >= (greater than or equal to), <= (less
than or equal to), = (equal to), and <> (different
from).
component. A TeamConnection object that
organizes project data into structured groups, and
controls configuration management properties.
Component owners can control access to data
and notification of TeamConnection actions.
Components exist in a parent-child hierarchy, with
descendant components inheriting access and
notification information from ancestor components.
See also
access list
and
notification list
.
concurrent development. Several users can
work on the same part at the same time.
TeamConnection requires these users to reconcile
their changes when they commit or integrate their
work areas and drivers with the release. Contrast
with
serial development
. See also
work area
.
configuration management. The process of
identifying, managing, and controlling software
modules as they change over time.
connecting parts. The process of linking parts
so that they are included in a build.
context. The current work area or driver used for
part operations.
corequisite work areas. Two or more work
areas designated as corequisites by a user so that
all work areas in the corequisite group must be
included as members in the same driver, before
that driver can be committed. If the driver process
is not used in the release, then all corequisite
work areas must be integrated by the same
command. See also
prerequisite work areas
.
current version. The last visible modification of
a part in a driver, release, or work area.
current working directory. (1) The directory that
is the starting point for relative path names. (2)
The directory in which you are working.
D
daemon. A program that runs unattended to
perform a standard service. Some daemons are
triggered automatically to perform their task;
others operate periodically.
database. A collection of data that can be
accessed and operated upon by a data
processing system for a specific purpose.
default. A value that is used when an alternative
is not specified by the user.
default query. A database search, defined for a
specific TeamConnection window, that is issued
each time that TeamConnection window is
opened. See also
search
.
Glossary 315