Issue 11810: MARTE PAM Parameters for behaviour demanded by a Step
Issue 11811: Movement of some stereotypes and attributes from PA to GA
Issue 12401: SendFlowAction and FlowSendAction
Issue 12408: Base unit errors in Figure D.3
Issue 11810: MARTE PAM Parameters for behaviour demanded by a Step (marte-ftf)
Click here for this issue's archive.
Source: Carleton University (Dr. Murray Woodside, cmw@sce.carleton.ca)
Nature: Uncategorized Issue
Severity:
Summary:
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. Possible resolution: 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.
Some stereotypes were introduced in PA because they were identified by these authors as being useful... but they might be equally useful to someone in other analyses. An example is the <<noSync>> stereotype on a branch of a par, to say explicitly that this branch does not synchronize at the end of the par. This provides forks that do not join... a performance optimization in some cases.
Two different terms, SendFlowAction and FlowSendAction, are being used for describing the invocation action related to send a data flow to connected components. Example: see figure 11.5 and 11.6 on pages 120 and 121
Base unit errors in Figure D.3 The base unit for "KHz", "MHz", "GHz" and "rpm" is "W" while it is expected to be "Hz". The base unit for "mm" is "bits" while it is expected to be "m". The base unit for "um2" is "bits" while it is expected to be "mm2".