Dependency is a relationship between two artifacts showing that one depends on the other.
Within the UML metamodel,
Dependency is a
Dependency is represented as a dashed line with an open arrow head from the depending artifact to that which it is dependent upon.
The details tabs that are active for dependencies are as follows.
Standard tab. See Section 13.4, “Documentation Tab”.
The values for the bounds of the dependency are downlighted, given the dependency is tied to a particular modelelement.
Standard tab. In the UML metamodel,
Dependency has no tagged values of its own, but
through superclasses has the following standard tagged values
derived (from the superclass,
true, meaning the dependency
relationship is redundant???it can be formally derived from
other elements, or
false meaning it
Derived dependencies still have their value in analysis to introduce useful names or concepts.
Navigate up through the package structure of the model. For a dependency this will be the package containing the dependency.
This creates a new Stereotype (see Section 16.5, “Stereotype”) for the selected dependency, navigating immediately to the properties tab for that stereotype.
This deletes the selected dependency from the model.
This is a deletion from the model
not just the diagram. To delete a
dependency from the diagram, but keep it within the model,
use the main menu
Text box. The name of the dependency.
It is quite common to leave dependencies unnamed.
ArgoUML does not enforce any naming convention for associations.
There is no representation of the name of a dependency on the diagram.
Drop down selector. Dependency has no standard stereotypes of its own under UML 1.3. and so ArgoUML does not provide any. The stereotype is shown between ?? and ?? above or across the generalization.
icon. If a stereotype has been selected, this will navigate to the stereotype property panel (see Section 16.5, “Stereotype”).
Text box. Records the namespace for the dependency. This is the package hierarchy.
Text area. Lists the end of the relationship that is supplying what is needed by the other end.
Button 1 double click on a supplier will navigate to that element.
Text area. Lists the “depending” ends of the relationship, i.e. the end that makes use of the other end.
Button 1 double click on a client will navigate to that element.