Specification of an Architecture Meta-Model - SPES 2020

Specification of an Architecture Meta-Model
RichComponent +component
Port
1 +port
0..*
+ isConjugated: Boolean
Figure 2.19: Ports.
Generalizations: NavigableFeature, MultiplicityElement
Attributes
«isOfType»
+type
1
PortSpecification
• isConjugated : Boolean [1] If true, the flow/service directions defined in the
corresponding port specification are all treated as if reversed. By default, the
value is false. This facility allows to specify peer ports (i. e. with the same
flows/services but complementary directions.) For flows, the complementary
directions are: in for out, out for in, and bidirectional for bidirectional. For services,
the complementary directions are: required for provided, and vice versa.
Associations
• type : PortSpecification [1] The port specification that types the port.
• component : RichComponent [1] The rich component that owns the port.
2.1.15 Components and Attributes
In this section the concept of variables as depicted in Figure 2.20 is described.
+component +attribute
+type
RichComponent Variable
DataType
2.1.15.1 Variable
0..1
0..*
Figure 2.20: Variables.
«isOfType»
A variable associates a name with a data type. It represents a permanent storage unit
for a value of the data type. The name is inherited from meta-class NamedElement via
NavigableFeature.
Variables are used to define attributes for rich components, local variables for composite
actions and local variables for machine blocks.
34/135
1