Legacy Issue Number: 11810
Source: Carleton University ( Murray Woodside)
A PaStep can make a demand for a behaviour, much like a macro, to be included in the Step. An example of the use of this, is to include a complex handshake protocol for exchanging a message between objects on different nodes.
The profile has
behaviourDemands: list of Scenarios to be included
behaviourCount: corresponding list of number of invocations during the step
It also should support parameters to the Scenario, such as the message size. This requires a way of binding a value in the invocation to a value in the Scenario.
Add behaviorParm : a corresponding list of tuples. Each element of a tuple could be expressed as (variable=value), with the variable name corresponding to the variable used in the Scenario
More complex and powerful resolution: Let the context variables decdlared for a Scenario be implicitly regarded as an ordered list of arguments, when the Scenario is invoked. The tuple could then give just the values for the list. A NUL value could be used to mean, do not override the value given within the Scenario.
The same considerations apply to PAM::externalOpDemands. A similar concern applies to GQAM::servDemands, but the resolution may have to be different as Operations already have arguments and the defining scenario is attached indirectly.
A broader version of this issue is parameterizing behaviours in general: it seems to be incomplete in MARTE.
Reported: MARTE 1.0b1 — Sun, 9 Dec 2007 05:00 GMT
Disposition: Resolved — MARTE 1.0b2
withdrawn by submitter
Updated: Fri, 6 Mar 2015 22:56 GMT