Omg issue Number

Disposition: Resolved

OMG Issue No: 11889

Title: Typos

Source:

Carleton University (Dr. Dorina C. Petriu, [e-mail])

Summary:

- Page 265, the first paragraph: “between the two between”

- Page 280, the second line from the bottom: “sorrespond”

- Page 311, the first paragraph: “ypical performance”

- Page 315, in the middle: “PProcesses”

- Page 325, in the middle: “avalilable”

Resolution:

Corrections are described in the revised text.

Revised Text:

In section 15.2.2.2, p.265, first paragraph of the Time Intervals section, replace “The inter-occurrence time interval between the two between successive initiations…” by “The inter-occurrence time interval between two successive initiations…”.

In section 15.3.2.13, p.280, constraint [1], replace “… servDemand and servCount sorrespond, …” by “… servDemand and servCount correspond…”.

In section 17.2.1, p.311, first paragraph, replace “ypical performance properties include…” by “Typical performance properties include…”.

In section 17.2.2.6, p.315, second item of the first enumeration, replace “… in different PProcesses…” by “… in different processes…”

In section 17.4.1, p.325, second paragraph, replace “…(multiplicity of avalilable resource instances)…” by “…(multiplicity of available instances)…”.

Disposition: Resolved

Disposition: Resolved

OMG Issue No: {12194}

Source:,) Nature: Revision Severity: Minor Summary:

Resolution:

Title: ExecHost.thoughput

Source: THALES (Mr. Sebastien Demathieu, [e-mail]

Summary:

In GQAM, the profile diagram (Figure 15.6) defines a stereotype attribute GaExecHost.throughput that is not documented in section 15.3.2 or introduced in the domain model (Figure 15.5)

Resolution:

Add to Domain model and document it. Add to Fig 15.5

Revised Text:

(1) In Sec. 15.3.2.7 GaExecHost: add an atttribute

throughput: NFP_Frequency [*] the throughput of the host in scheduled initiations/sec.

(2) In Sec , p 266, second-last paragraph,

old text:

In use it will also have an output NFP of resource utilization (for a multiple resource this is defined as the mean number of busy units).

new text:

In use it will also have an output NFP of resource utilization (for a multiple resource this is defined as the mean number of busy units), and for throughput (the number of requests handled successfully per unit time).

(3) Fig 15.5, add attribute

throughput: NFP_Frequency [*]

to class ExecutionHost.

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 12214

Title: Wrong direction of the allocation

Source:

INRIA (Dr. Frederic Mallet, [e-mail])

Summary:

Wrong direction of the allocation: The MARTE allocation mechanism is directly inspired from SysML. SysML has chosen a convention contrary to UML and draws the arrow from the suppliers (usually a target) to the clients (usually a source). So as to be compatible MARTE has followed SysML with that convention. Now, the SysML RTF is considering that this triggers too many problems with tool vendors and thus considers using the same convention than UML. An alignment between SysML and MARTE is required as much as possible and MARTE FTF should then think through this issue and adopt the same convention than UML.

Resolution:

The only text that was wrong has been removed in the resolution for issue 11770. The new text in this resolution assumed that sources are referred as clients and targets are referred as suppliers.

This resolution has no impact on any other section since the wrong “direction” was only in the vocabulary used (clients vs. suppliers) and the graphical notation was already correct.

Revised Text:

See resolution for issue 11770 for details.

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 12232

Title: Rename every instance of "SaEnd2EndFlow" to "SaEndToEndFlow"

Source:

ARTISAN Software Tools (Mr. Lonnie VanZandt, [e-mail])

Summary:

Rename every instance of "SaEnd2EndFlow" to "SaEndToEndFlow". While this issue is specific to the cited text, it SHOULD be applied throughout the specification whereever attributes are so named. The rationale for the change is that the substitution of numerals such as "1", "2", and "4" for the non-numeric concepts expressed by the truncated words "a", "to", and "for", respectively, lead to needless cognitive dissonance. CamelCase is acceptable but there is no longer any need for variable names which use substitutions and truncations to satisfy machine or language constraints.

Resolution:

Proceed with the suggested modification.

The only place where a numeral is used as substitute of words is in the stereotype “SaEnd2EndFlow” and in two of their attributes.

Revised Text:

-In page 294, replace the last sentence of the fourth paragraph with (the former text had also some minor typos corrected here):

A "SaEndToEndFlow" will make reference implicitly to one or more GQAM "GaWorkloadEvent" and to one "GaScenario" commonly by means of a containment relationship (owned elements) or allocation stereotypes.

-In page 294, replace Fig. 16-7 with the following figure (note that the shared resource attributed was added to reflect Issue 11778 resolution in Ballot 1).

-In page 295, replace the last sentence of the second paragraph by:

For instance, "SaEndToEndFlow" has an association (timing) that define a meta-association between this element and UML constraints stereotyped as "GaTimingObserver", or its child stereotypes.

-In page 296, replace section 16.3.2.1 by:

16.3.2.1 SaEndToEndFlow

-Replace the first sentence of this subsection with:

The SaEndToEndFlow stereotype maps the EndToEndFlow domain element (section Error: Reference source not found, p. Error: Reference source not found) denoted in Error: Reference source not found.

-Replace the names of the third and fourth attributes in this subsection with:

EndToEndT

EndToEndD

-In page 304, replace Fig. 16-11 with:

-In page 643, Annex H, replace the word ‘End2EndFlow’ in the fifth row, second column, with ‘SaEndToEndFlow’.

Disposition: Resolved