Specification of an Architecture Meta-Model - SPES 2020

Specification of an Architecture Meta-Model
approaches. The specification of abstraction levels, perspectives, and aspects (also
called viewpoints) is also possible with the SPESMM core.
2.1 Component Meta-Model
In this section a modeling concept for rich component design is presented. The approach
is based on the HRC meta-model.
2.1.1 Model Elements
Model elements are elements which have specific semantics for modelling such as
components, requirements, trace links, attributes etc. As depicted in Figure 2.2 they
can be extended by specific domain-, user-, or tool-specific extension types and by
respective extension attribute values.
ExtensionAttributeValue +extensionAttributeValue
+extensionType
Element
ExtensionType
0..*
2.1.1.1 Element {abstract}
NamedElement
+ comment :String [0..*]
+ name :String
+ /qualifiedName :String {readOnly}
Figure 2.2: Elements.
0..*
OpaqueExtensionElement
An element is a model entity with defined semantics such as components, requirements,
ports, attributes or trace links. An element can be extended by extension types.
These define specific semantics und structure of an element. The attributes of an extension
type can be used for the element by defining extension attribute values.
Element is an abstract meta-class. Its sub-classes define concrete semantics. Extension
types define specific semantics for an element. Extension attribute values that are
owned by an element must be instances of attributes that belong to referenced extension
types of an element. There are two sub-classes of Element, namely NamedElement
and OpaqueExtensionElement.
Aggregations
• extensionAttributeValue : ExtensionAttributeValue [0..*] A set of attribute
values coming with domain-, user-, or tool-specific extensions.
8/135