Specification of an Architecture Meta-Model - SPES 2020

Specification of an Architecture Meta-Model
two or more interconnection ends. There are four concrete sub-classes are defined
for fixed interconnections: FlowBinding that connects (instances of) flows; Service-
Binding that connects (instances of) services; Connector that connects (instances of)
ports; and ElaboratedInterconnection (see Section 2.1.18). An interconnection is also
a named element.
Generalizations: NamedElement
Associations
• component : RichComponent [1] Specifies the rich component that owns the
interconnection.
2.1.16.2 Connector
A connector is a kind of fixed interconnections. The interconnection ends owned by
a connector must be 2 or more port ends, which represent one instance (or an array
of instances) of a port of the rich component that owns the connector, or of a subcomponent
of the owning component.
Generalizations: Interconnection
Aggregations
• end : Connector port [1..*] Specifies the ends of the interconnection.
Constraints Connectors are subject to the following constraints:
1. The interconnection ends owned by a connector must be port ends.
Formal OCL constraint TBD.
2.1.16.3 Connector port
Connector port is an InterconnectionEnd and references exactly one port of the component
that owns the connector or one instantiated port of the component’s parts. In
the second case the associated component parts denotes the instantiated context of the
component port which is the target of the reference.
Since a ports belongs to a component specification an interconnection which shall
be linked to ports of rich component parts requires a reference to the respective Rich-
ComponentProperty which is typed by the RichComponent. This is called an instance
reference. Such a mechanism is realized by a connector end which references both
the instantiated context and the concrete target port of the respective component as
depicted in Figure 2.22.
36/135