Class UML 2.4.1::Dependency
Description:
A dependency is a relationship that signifies that a single or a set of
model elements requires other model elements for their specification or
implementation. This means that the complete semantics of the depending
elements is either semantically or structurally dependent on the definition
of the supplier element(s).
Direct Superclasses: PackageableElement,
DirectedRelationshipDirect Subclasses: Usage,
Deployment,
AbstractionClass Precedence List: Dependency,
PackageableElement,
ParameterableElement,
NamedElement,
DirectedRelationship,
Relationship,
ElementProperties:
client :
NamedElement (1 *); -- source
Dependency supplier :
NamedElement (1 *); -- source
DependencyThe element(s) independent of the client element(s), in the same respect
and the same dependency relationship. In some directed dependency relationships
(such as Refinement Abstractions), a common convention in the domain of
class-based OO software is to put the more abstract element in this role.
Despite this convention, users of UML may stipulate a sense of dependency
suitable for their domain, which makes a more abstract element dependent
on that which is more specific.
Subsets: DirectedRelationship.target
visibility :
VisibilityKind (1 1); -- source
PackageableElement owningTemplateParameter :
TemplateParameter (0 1); -- source
ParameterableElement templateParameter :
TemplateParameter (0 1); -- source
ParameterableElement clientDependency :
Dependency (0 *); -- source
NamedElement name : String (0 1); -- source
NamedElement nameExpression :
StringExpression (0 1); -- source
NamedElement namespace :
Namespace (0 1); -- source
NamedElement qualifiedName : String (0 1); -- source
NamedElement source :
Element (1 *); -- source
DirectedRelationship target :
Element (1 *); -- source
DirectedRelationship relatedElement :
Element (1 *); -- source
Relationship ownedComment :
Comment (0 *); -- source
Element ownedElement :
Element (0 *); -- source
Element owner :
Element (0 1); -- source
ElementConstraints:
No additional constraints.
Operations:
No additional operations.
Send questions or comments to
[email protected].