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 |
---|---|
There is no source tab, since there is no source code that could be generated for a dependency relationship. |
ToDoItem
Standard tab.
Properties
See Section 17.13.2, “Dependency Property Toolbar” and Section 17.13.3, “Property Fields For Dependency” below.
Documentation
Standard tab. See Section 12.5, “Documentation Tab”.
Style
Standard 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. |
Constraints
Standard tab. ArgoUML only supports constraints on Classes and Features (Attributes, Operations, Receptions, and Methods), so this tab is grayed out.
Tagged Values
Standard tab. In the UML metamodel,
Dependency
has no tagged values of its own, but
through superclasses has the following standard tagged values
defined.
derived
(from the superclass,
ModelElement
). Values
true
, meaning the dependency relationship is
redundant—it can be formally derived from other elements,
or false
meaning it cannot.
![]() | Note |
---|---|
Derived dependencies still have their value in analysis to introduce useful names or concepts. |
Go
up
Navigate up through the package structure of the model. For a dependency this will be the package containing the dependency.
Delete
This deletes the selected dependency from the model.
![]() | 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 |
Name
Text box. The name of the dependency.
![]() | 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. |
Stereotype
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.
Navigate Stereotype
icon. If a
stereotype has been selected, this will navigate to the
stereotype property panel (see Section 15.4, “Stereotype”).
Namespace
Text box. Records the namespace for the dependency. This is the package hierarchy.
Suppliers
Text 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.
Clients
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 use case.