Open ronaldtse opened 4 years ago
class Boss
class Employee {
+name
-salary
}
Boss ..> (permit) Employee
@ronaldtse ucd
gem already have this syntax for defining dependency:
class Boss {
dependency Employee
}
class Employee {
+name
-salary
}
OK, let's adopt this syntax. But where do you write <<permit>>
?
OK, let's adopt this syntax. But where do you write
<<permit>>
?
In that case, we can use the explicit syntax as described in https://github.com/lutaml/lutaml-uml/issues/23#issuecomment-671696360
Sounds good. @w00lf once the decision is made could you please help move it to the specification document? Thanks!
Sounds good. @w00lf once the decision is made could you please help move it to the specification document? Thanks!
Ok, will do
Dependencies
Notation & Semantics
Causes of Dependencies
Types of dependency relationships
Abstraction relationship: dependency relationship between model elements at various abstraction levels. Used with a stereotype. Default stereotypes: <>, <> and <>.
An abstraction relationship always has a mapping rule, specifying how the participating elements relate to one another (formal o informal).
The relationship can also be bidirectional, depending on the stereotype and mapping rule.
A special abstraction relationship is realization, a relationship between an implementation an its specification element.
A substitution relationship specifies that instances of the independent element can be substituted by instances of the dependent element at runtime. (e.g. When the elements implement the same interfaces).
<<call>>
<<Create>>
<<derive>>
<<instantiate>>
<<permit>>
<<refine>>
<<trace>>
<<use>>