
Metamodel user guide
An Abstraction is a relationship that relates two Elements or sets of Elements that represent the same concept at different levels of abstraction or from different viewpoints.
An Abstraction is a Dependency in which the supplier and the client are mapped.

Attribute | Description |
---|---|
string mapping [0..1] | Composition of an Expression that states the Abstraction relationship between the supplier and the client. In some cases, such as Derivation, this is usually formal and unidirectional. In other cases, such as Trace, it is usually informal and bidirectional. The mapping expression is optional and may be omitted if the precise relationship between the elements is not specified. Depending on the specific stereotype of Abstraction, mapping may be formal or informal, and unidirectional or bidirectional. Abstraction has predefined stereotypes (such as «derive», «refine», and «trace»), which are defined in the Standard Profiles chapter. 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. |