Omg issue Number

OMG Issue No: 11774

Title: : GQAM: Domain Model & Profile (01), <
>

Source:

Commissariat a l Energie Atomique-CEA/LIST (Mr. Huascar Espinoza, [e-mail])

Summary:

The PrecedenceRelation concept (fig 15.3) could be used to specify delays due to e.g., queues. However, PrecedenceRelation only exists in the Domain Model. Its implementation is intended to be supported by existing UML concepts (e.g., forks, joints, etc.) I’d suggest to define the corresponding stereotype (<

>) in order to allow for modelling delays or other precedence patterns like event divisors: a number of event occurrences triggers an execution.

Resolution:

This enhancement is not necessary, since everything it would provide can already be done using scenario Steps, and done better. However the method for showing an event divisor using steps should be added to the text.

Since a precedence relation always leads to one or more steps, properties such as queueing etc can be attached to the step. The step is a better place for these properties because there may be multiple branches in a precedence relation (a branch or fork), each with its own properties. For example, a fork precedence would have a different waiting on each branch of the fork, which would be complex to describe or specify within the fork, but very easy on the following steps.

An event divisor or multiplier can be provided using the CommStep stereotype. We assume that the event is a call invoking a Step. The call can be stereotyped as a CommStep, which has a repetition attribute. If this is set to N, it means the call is repeated N times, giving event multiplication. If it is set to 1/N, it means that every Nth execution of the sender gives a call... an event divisor. If the repetition attribute is specified as a deterministic NFP, it should be defined to be interpreted as 1/N for an integer N, determined by rounding to an integer if necessary. A stochastic division is also possible.

Revised Text:

p 264, 3rd-last para, before:

A CommunicationStep defines the conveyance of a message between system entities, and has an attribute of the message size.

after: A CommunicationStep defines the conveyance of a message between system entities, and has an attribute of the message size. The repetitions attribute of a CommunicationStep Inherited from Step) denotes multiple sendings (event multiplication) if >1, or decimation of sendings (event division) if <1. If repetitions is deterministic and less than 1 it is interpreted as event division by N = 1/repetitions, rounded to the nearest integer. That is, every Nth execution of the sending Step causes on cal to occur. Repetitions may also be a random quantity.

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11777

Title: {title of the issue}

Source:

Commissariat a l Energie Atomique-CEA/LIST (Mr. Huascar Espinoza, [e-mail])

Summary:

[GQAM: Domain Model & Profile] A TimingObserver (Fig. 15-4) refers to 0 or 1 start event occurrence and 0 or 1 end event occurrences, which are modelled by TimedInstantObservation elements. However, more refined TimingObservers can define the synchronization between several events.

Resolution:

Change the multiplicity of the start and end observation points to [*].

Revised Text:

1. 
   Fig 15.4 p 266, the startObs and endObs associations should both have multiplicity of [*] at the TimedInstantObservation end.
   
2. 
   Fig 15.8 p 272, the startObs and endObs associations should be replaced:
   

old text: “startObs 0..1” and “endObs 0..1”

new text: “startEvent * ” and “endEvent * ”

3. 
   Sec 15.3.2.14,
   
   1. 
      the stereotype is TimingObs not TimingObserver
      

(b) the StartEvent and EndEvent associations should both have multiplicity of [*]

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11778

Title: What is the Meaning of "Business Management Perspective"?

Source:

Thales (Sebastien Demathieu, [e-mail])

Summary:

I would suggest explaining what is the "business management perspective".

Resolution:

(FTF Group) Strike the phrase “Business Management Perspective” Change it by “system perspective”

Revised Text:

In section 2.1, in paragraph 1, in the second sentence, replace:

“Though all of them are related from the business management perspective and…”
By
““Though all of them are related from the system perspective and…”.

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11779

Title: attribute “GRM, GQAM, SAM: DomainModel & Profile SAM”

Source:

Commissariat a l Energie Atomique-CEA/LIST (Mr. Huascar Espinoza, [e-mail])

Summary:

A number of non-functional properties for scheduling analysis are specified by a worst-case and a best-case duration value. The MARTE library for NFP types defines a NFP_BoundedDuration data type. This type could be used to type ‘bounded’ durations in SAM. For instance: endToEndTime (fig. 16-7), execTime (fig. 10-18), latency (fig. 15-8), contextSwitchTime, ISRswithTime (fig. 16-9).

Resolution:

This two attributes may be not sufficient, it is better to have all the statistical qualifiers over multiple values of NFP_Duration supported. To minimize editorial impact and a deep revision of side effects, the additional attributes provided in NFP_BoundedDuration will be added to NFP_Duration. With the variation that “min” will be represented as “best” and “max” as “worst”, this keeps the dual dimension in the utilization of multiple values and the specification of variability in the context in which the value is used. This implies minimal changes to NFP_Duration, eliminating NFP_BoundedDuration, and change the only reference to it (in RealTimeFeature) to NFP_Duration.

Revised Text:

2. 
   Modify Fig.D.5 adding the two attributes “worst: Real” and “best: Real” in the definition of NFP_Duration
   
3. 
   Modify the definition of the RealTimeFeature element so that the attribute boundDI has type NFP_Duration instead of NFP_BoundedDuration, in Figure 13.5, and sections 13.3.2.9 rtf, and F.7.10 RealTimeFeature.
   
4. 
   Eliminate the type NFP_BoundedDuration from Fig D.5
   

Disposition: Resolved