Specification of an Architecture Meta-Model - SPES 2020

Specification of an Architecture Meta-Model
event indicates an interaction point where only at certain time instants there is a value
available and the values may change from instant to instant.
2.1.17.6 ActivationFlow
An activation flow is the communication point through which the rich component that
owns the port that owns it, communicates to the environment the possibility to execute,
i. e. there is a valid outgoing transition from the current active state. Thus the direction
of an activation flow is always out, the kind is discrete and the type is Boolean.
ActivationFlow inherits form Flow.
Generalizations: Flow
Constraints Activation flows are subject to the following constraints:
1. An activation flow must be of kind discrete:
context ActivationFlow inv isDiscrete:
self .kind = FlowKind:: discrete
2. An activation flow must be of direction out:
context ActivationFlow inv isOut:
self .direction = FlowDirection::out
3. An activation flow must be of type Boolean:
context ActivationFlow inv isBoolean:
self .type.isBoolean()
2.1.17.7 EnablingFlow
An enabling flow is a flow constituting the communication point through which the
environment can control the execution of a rich component. The rich component that
owns an enabling flow disables its execution (is forced to take an empty self-loop
transition) if the value of this enabling flow is true. The enabling flow can be set
only by the environment, thus the direction is in. The kind is discrete and the type is
Boolean, since it is the counterparting coordination port of the activation flow.
Generalizations: Flow
44/135