Statement that the implementation or functioning of one or more elements requires the presence of one or more other elements.
In the metamodel, a Dependency is a directed relationship from a client (or clients) to a supplier (or suppliers), stating that the client is dependent on the supplier (in other words, the client element requires the presence and knowledge of the supplier element). In the metamodel, an Abstraction is a Dependency in which there is mapping between the supplier and the client. Depending on the specific stereotype of Abstraction, mapping may be formal or informal, and may be unidirectional or bidirectional. If an Abstraction element has more than one client element, the supplier element maps into the set of client elements as a group. For example, an analysis-level Class might be split into several design-level Classes. The situation is similar if there is more than one supplier element. Dependencies are widely used inside Modelio to manage traceability. Any ModelElement can be traced to another ModelElement using this association. In Modelio, a Dependency can only have one client and one supplier. In Modelio, in order to comply with UML 2.0, the roles are swapped and renamed. The correspondence from UML 2.0 is now as follows: Dependency.client = Dependency.Impacted; Dependency.supplier = Dependency.DependsOn; Element.supplierDependency = ModelElement.ImpactedDependency; Element.clientDependency = ModelElement.DependsOnDependency. A Dependency now belongs to the impacted element (the client in UML 2.0).
: Dependency (architecture_autodiagram)
Figure 125 : Dependency (architecture_autodiagram)
string DependsOnId [1..1]
string DependsOnName [1..1]
DependsOn : ModelElement [0..1]
The element independent of the client element, in the same respect and the same dependency relationship.
Impacted : ModelElement [1..1]