Filter
Top Products
originator. The user who opens a defect or
feature and is responsible for verifying the
outcome of the defect or feature on a verification
record. This responsibility can be reassigned.
owner. The user who is responsible for a
TeamConnection object within a TeamConnection
family, either because the user created the object
or was assigned ownership of the object.
P
parent component. All components in each
TeamConnection family, except the root
component, are created in reference to an existing
component. The existing component is the parent
component. See also
child component
and
component
.
parent part. Any part in a build tree that has a
child defined. See also
part
and
child part
.
parser. A tool that can read a source file and
report back a list of dependencies of that source
file. It frees a developer from knowing the
dependencies one part has on other parts to
ensure a complete build is performed.
part. A collection of data that is stored by the
family server and retrieved by a path name. They
include text objects, binary objects, and modeled
objects. These parts can be stored by the user or
the tool, or they can be generated from other
parts, such as when a linker generates an
executable file.
path name. The name of the part under
TeamConnection control. A path name can be a
directory structure and a base name or just a base
name. It must be unique within each release. See
also
base name
.
pool. See
build pool
.
pop-up menu. A menu that, when requested,
appears next to the object it is associated with.
prerequisite work areas. If a part is changed to
resolve more than one defect or feature, the work
area referenced by the first change is a
prerequisite of the work area referenced by later
changes. A work area is a prerequisite to another
work area if:
v Part changes are checked in, but not
committed, for the first work area.
v One or more of the same parts are checked
out, changed, and checked in again for the
second work area.
problem tracking. The process of tracking all
reported defects through to resolution and all
proposed features through to implementation.
process. A combination of TeamConnection
subprocesses, configured by the family
administrator, that controls the general movement
of TeamConnection objects (defects, features,
work areas, and drivers) from state to state within
a component or release. See also
subprocess
and
state
.
Q
query. A request for information from a
database, for example, a search for all defects
that are in the open state. See also
default query
and
search
.
R
raw format. Information retrieved on the report
command that has the vertical bar delimiter
separating field information, and each line of
output corresponds to one database record.
refresh. This TeamConnection action updates a
work area with any changes from the release, and
it also freezes the work area, if it is not already
frozen.
relative path name. The name of a directory or
a part expressed as a sequence of directories
followed by a part name, beginning from the
current directory.
release. A TeamConnection object defined by a
user that contains all the parts that must be built,
tested, and distributed as a single entity.
Glossary 319