Specification of an Architecture Meta-Model - SPES 2020

Specification of an Architecture Meta-Model
points in the ports of the rich component.
A rich component may optionally own an initializer. The purpose of the initializer
is to assign initial values to the attributes of the instances of the rich component.
Moreover, if the rich component has nested sub-components, in the body of the initializer,
the corresponding initializers of the rich components that type these nested
sub-components can also be invoked to initialize the sub-instances (see Initialization-
Call).
The inter-connection configuration of a rich component and its sub-components are
specified by its interconnections. Two kinds of interconnections can be specified statically:
the finer one — bindings (including both flow bindings and service bindings),
which bind the interaction points of the component or its sub-components; and the
coarser one — connectors among ports, which serve as a short-cut to bind all the
interconnection points in each connected ports with the same names. All these interconnections
are owned by the rich component. In addition, a rich component may also
specify its inter-connection configuration dynamically in terms of “elaboration codes”.
The dynamics of a rich component is depicted by its contracts and its behavior.
Contracts are fulfilled by the rich component and expressed in terms of assumptions
and promises, requiring the environment to behave as assumed, and guaranteeing the
rich component to behave as promised. There are two kinds of contracts: an atomic
contract that owns a pair of assertions for the assumption and promise respectively, and
a composite contract that is a composition of contracts using a number of operators
such as: glb, parallel, and fusion. Please refer to ContractCompositionOperator for
details. Finally, according to the perspective from which a contract talks about the
specification of the component, contracts are categorized into viewpoints.
In contrast to contracts, the behavior of a rich component defines the inherent dynamics
of the rich component, where the behavior is specified by a block occurrence
to describe the dynamics at an abstracted level.
An HRC block exposes dynamics on its owned pins. Then an instance of such a
pin, which is owned by block occurrences of this HRC block, will be linked to either a
flow, a service, or an attribute of the rich component that owns this block occurrence,
to state that the dynamics of the component on the flow, the service, or the attribute is
as specified by the HRC block on the linked pin. Such links are owned by the same
rich component.
Generalizations: TemplatableElement, ReusableElement
Aggregations
• attribute : Variable [0..*] The set of attributes owned by the rich component.
• part : RichComponentProperty [0..*] The set of sub-components owned by
the rich component.
• port : Port [0..*] The set of ports owned by the rich component.
30/135