A relationship between tasks, such that one requires input from the other to begin. ()
A relationship between requirements such that the requirement that is depended upon must normally be satisfied for the other requirements to be able to meet their objectives.
A dependency exists between elements and expresses that elements within one package use elements from the package on which it depends, implying that a change in one element may affect or supply information needed by the other element.
a file that is used as input to create the target
a relationship between two things within which a change to one thing (the independent element) may affect the semantics of the other thing (the dependent element)
a relationship that may exist between two columns
a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation
a relationship where the client does not have semantic knowledge of the supplier
a type of relationship expressed between two classes in which one class relies on the other
a type of relationship that signifies that one element, or group of elements, acting as the client depends on another element or group of elements that act as a supplier
The relationship between two interdependent tasks in a project or series of projects.
A relationship between two or more deliverables, requirements, and/or project artifacts that implies that a change in one item in a dependency relationship likely requires a change in the other items.
A relationships between one or more activities or tasks. An task may be dependent upon another task if that task cannot be started until the other task has been completed.
A task has a dependency if it involves an activity, resource or work product which is subsequently required by another task. Dependencies come in many forms: a test plan can’t be executed until a build of the software is delivered; code might depend on classes or modules built in earlier stages; a user interface cannot be built until the design is reviewed. If Wideband Delphi is used to generate estimates, many of these dependencies will already be represented in the assumptions.
A relationship in which one depends on another for support in whole or in part.
This term refers to a relationship between two entities. Some relationships, like Fix Pnt Rel Pnt, involve an independent and dependent entity. The point that is fixed relative to another is said to be dependent (form a dependency) on the other point. If the independent point is moved, then the dependent (relative) point moves along with it automatically.
See logical relationship.
The relationship between a source and a target. This comes in three flavors, as indicated by the operator between the target and the source. : gives a straight time-wise dependency (if the target is older than the source, the target is out-of-date), while ! provides simply an ordering and always considers the target out-of-date. :: is much like :, save it creates multiple instances of a target each of which depends on its own list of sources.
A relationship between two operations in which the first operation must successfully finish before the second operation can begin.
A logical relationship between two or more activities. The four types of dependencies are: start-to-finish, start-to-start, finish-to-start, and finish-to-finish.
A relationship between two modeling elements, in which a change to one modeling element (the independent element) will affect the other modeling element (the dependent element).
The relationship of one task to another where the start or end date of the second task (successor) is constrained by the start or end date of the first (predecessor).
The relationships among prepared statements and dictionary objects in a database. Cloudscape tracks the dependency that publications, stored prepared statements, and prepared statements have on the dictionary objects they access. If dropping or modifying a dictionary object would cause an open prepared statement to be invalidated, the change is not permitted.
A dependency in the Unified Modeling Language exists between two defined elements if a change to the definition of one may result in a change to the other. In UML this is indicated by a dashed line pointing from the dependent (or client) to the independent (or supplier) element.