1. Standard predefined dependencies

2. Differences with UML link

3. See also

4. References

5. Further reading

6. External links

In the Unified Modeling Language (UML), a Dependency is a relationship that shows that an element, or set of elements, requires other model elements for their specification or implementation.^[1] The element is dependent upon the independent element, called the supplier. Two or more elements in this relationship are called tuples.

In the UML, this is indicated by a dashed line pointing from the dependent (or client) to the independent (or supplier) element. The arrow representing a Dependency specifies the direction of a relationship, not the direction of a process.

Standard predefined dependencies

UML - defined dependencies include {{Citation needed|date=October 2016}}:

• «call2» UML2: The client (an operation) may call the supplier (an operation)
• «create» UML2: The client (a classifier) may create instances of the supplier (a classifier)
• «derive» UML2: The client (e.g., attribute value, link) may be computed from the supplier(s)
• «instantiate» UML2: Operations of the client (a classifier) may create instances of the supplier (a classifier)
• «permit» UML2: Obsolete
• «realize» UML2: Obsolete
• «refine» UML2: The client element(s) are at a "later" semantic level than the supplier(s)
• «send» UML2: The client (an operation) sends the supplier (a signal)
• «substitute» UML2: The client element can replace (under some circumstances) the supplier
• «trace» UML2: The client elements "trace" to the suppliers. Typically used for levels of requirements
• «use» UML2: The client element somehow "uses" the supplier

Differences with UML link

A UML link is run-time relationship between instances of classifiers, while a dependency is a model-time relationship between definitions.

A typical uni-directional link requires the one instance to know about, and thus depend, upon the other, but this is not required. A uni-directional link only requires the possibility of navigation not dependency.

Likewise, a bi-directional link requires that both instances may traverse to each other, but this also does not require dependency.

However, after the traversal of the association, if some property of the target instance's definition is accessed, such as an operation or attribute, a dependency is created.

See also

• functional dependency

References

Further reading

External links

• Dependency Relationship in UML 2
• Documents associated with Unified Modeling Language (UML), v2.4.1

• Battle of the nek
• Battle of The Nek
• Battle of the neretva
• Battle of the network reality stars
• Battle of the network stars
• Battle of the neva
• Battle of the niemen river
• Battle Of The Nile
• Battle of the nive
• Battle of the Nobles
• Battle of the nobles
• Battle of the north fork of the red river
• Battle of the north inch
• Battle of the North Inch of Perth
• Battle of The North Valley of Quneitra
• Battle of The Notch
• Battle of the Notch
• Battle of the novgorodians with the suzdalians
• Battle of the Novgorodians with the Suzdalians
• Battle of the Nude Men
• Battle of the Nudes (album)
• Battle of the Nudes (disambiguation)
• Battle of the Nudes (engraving)
• Battle of the Nueces
• Battle of the Oasis