MARTE11 — GCM behavioral representation

The current version of the MARTE::GCM specification presents a mechanism to model data received and sent via ports. However, receptions are modelled in the higher level as GCMTriggers which extends UML Trigger, applicable in State Machine diagrams; while invocations are modelled using GCMInvocationActions, which extends UML InvocationAction, applicable in Activity diagrams.

For the sake of applicability I would propose to extend the GCM metamodel with extra stereotypes so that invocations can be modelled in STM and receptions can be modelled in Activity diagrams. I this wouldn't be possible I would propose to include some examples showing how this can be modelled in the later cases.

The issue addresses two different problems. The first one regarding receptions in
Activity diagrams and the second one regarding invocations in state machine
diagrams.
The first part of the issue can be closed, since it is possible to model this kind of
receptions using UML AcceptEventActions; which can be associated with a
GCMTrigger. Example 3, on Figure 12.23, illustrates this.
The second part of the issue; however it is not currently covered by MARTE or
UML. The proposed resolution is to add a new stereotype,
GCMInvocatingBehavior, which models the invocations taking place inside a
behavior without having to look at its internals (particularly interesting in the case
of OpaqueBehaviors). This stereotype will allow specifying communications in
the scope of a single component and independently from other components (in
opposition with Interactions, which specify communications between different
components, with a system wide scope).