Dependency is a relationship between two artifacts showing that one depends on the other.
Within the UML metamodel, Dependency is a
sub-class of Relationship.
Dependency is represented as a dotted line with an open arrow head from the depending artifact to that which it is dependent upon (see Figure 16.1, “Possible artifacts on a use case diagram.”).
The details tabs that are active for dependencies are as follows.
![[Note]](images/note.png) | Note |
|---|---|
There is no source tab, since there is no source code that could be generated for a dependency relationship. | |
ToDoItemStandard tab.
PropertiesSee Section 17.13.2, “Dependency Property Toolbar” and Section 17.13.3, “Property Fields For Dependency” below.
DocumentationStandard tab. See Section 12.5, “Documentation Tab”.
StyleStandard tab
Note The values for the bounds of the dependency appear to have no meaning. Changing them has no effect on the diagram. This is sensible behavior, given the dependency is tied to a particular use case.
ConstraintsStandard tab. ArgoUML only supports constraints on Classes and Features (Attributes, Operations, Receptions, and Methods), so this tab is grayed out.
Tagged ValuesStandard tab. In the UML metamodel,
Dependencyhas no tagged values of its own, but through superclasses has the following standard tagged values defined.derived(from the superclass,ModelElement). Valuestrue, meaning the dependency relationship is redundant—it can be formally derived from other elements, orfalsemeaning it cannot.Note Derived dependencies still have their value in analysis to introduce useful names or concepts.
Go upNavigate up through the package structure of the model. For a dependency this will be the package containing the dependency.
DeleteThis deletes the selected dependency from the model.
![[Warning]](images/warning.png)
Warning 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
Remove From Diagram(or press the Delete key).
NameText box. The name of the dependency.
![[Tip]](images/tip.png)
Tip It is quite common to leave dependencies unnamed.
Note ArgoUML does not enforce any naming convention for associations.
Note There is no representation of the name of a dependency on the diagram.
StereotypeDrop 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.
Navigate Stereotype
icon. If a
stereotype has been selected, this will navigate to the
stereotype property panel (see Section 15.4, “Stereotype”).NamespaceText box. Records the namespace for the dependency. This is the package hierarchy.
SuppliersText area. Lists the “depending” ends of the relationship, i.e. the end supplying what is needed by the other end.
Button 1 Double Click on a client will navigate to that use case.
ClientsText 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 use case.