Omg issue Number

Summary of Changes Made

The MARTE FTF made changes that:

• 
  Fixed numerous minor consistency problems.
  
• 
  Added some minor features required for the MARTE domain.
  
• 
  Increased the clarity of the specification.
  
• 
  Fixed editorial mistakes.
  

Although there are some deferred issues (28 deferred issues), most of them are alignments with other specifications (SysML, AADL), clarification issues (e.g., precise semantics for VSL grammar), as well as enhancement issues for advanced features, which do not affect the consistency and broad modeling coverage of the MARTE specification.

Disposition: Resolved

OMG Issue No: 11337

Title: attribute “Naming conventions and typing errors”

Source:

• 
  Name: Philippe Soulard
  
• 
  Company: SODIUS
  
• 
  mailFrom: [e-mail]
  

Summary:

Naming conventions and typing errors: - MARTE::MARTE_Foundations::GRM::GRService -> GrService for coherence - MARTE_Library::GRM_BasicTypes::EDFParameters -> EDF_Parameters or EdfParameters - MARTE::MARTE_AnalysisModel::SAM::SaSchedObs::suspentions -> suspensions

Resolution:
The convention of using uppercase for the prefixes would have been more consistent with the English style, but it has been almost consistently used along the spec the capitalization of only the first letter to reduce space, for this reason is probably better to just correct GRService in GRM as well as EDFParameters suspentios is clearly a typo to correct.

Revised Text:

Replace GRService by GrService in Figures 10.17, 14.25, 14.66, 14.73 and in sections 10.3.1, 10.3.2.1, 10.3.2.8, 10.3.2.11, 14.1.3.2(pag196),

Replace EDFParameters by EDF_Parameters in Figures 10.19, D.9, and in sections 10.3.3.1, 10.3.3.8
Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11338

Title: MARTE_Library::MeasurementUnits model library

Source:

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

Summary:

MARTE_Library::MeasurementUnits model library contains following bugs. In FrequencyUnitKind enumeration baseUnit tag value specified is W instead of Hz. In LenghtUnitKind enumeration baseUnit tag value is m for mm literal. In AreaUnitKind enumeration baseUnit tag value is mm2 for um2 litreal. In DataTxRateUnitKind convaFactor is 1024 instead of 1E3.

Resolution:

Modify Figures D.3 according to proposed corrections.

Revised Text:

Page 435 old figure



Figure D.3 – MARTE library of measurement units

Page 435 new figure (note that the modification includes Issue 11877)



Figure D.3. – MARTE library of measurement units

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11339

Title: Section: Annex B3.3.3

Source:

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

Summary:

The rule references an rule that is not defined in the VSL grammar.

Resolution:

VSL expressions are specified in OpaqueExpressions. Adding new opaque expressions within a VSL expression would make VSL expressions complex, and without a real added value. Hence, we do not support in VSL nested expressions written in new languages. Note that this doesn’t mean that we do not allow one to extend VSL. VSL can be extended by reusing its metaclasses, as the Clock Constraint Language in MARTE.

Hence, the term in the VSL grammar is not right. This resolution proposes to remove that term from the VSL grammar.
Revised Text:

In section B.3.3, page 397, remove the term:

The new rule for will be
::= | | | | | | | |

Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11340

Title: Section: Annex B3.3.3 p 397 (circular reference in time expression grammar)

Source:

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

Summary:

A circular reference between the -> -> -> rules prevents a straightforward implementation of the VSL BNF grammar.

Resolution:

We modify the grammar for time expressions to prevent the circular reference.

Revised Text:

-In Section B.3.3.17, replace the second and third rules by:

::= ( ( | ) [‘+’ ] ) | ( [ ‘+’ ] )

::= ( | ) | | ( ‘(’ ‘-’ ‘)’ )
Disposition: Resolved

Disposition: Resolved

OMG Issue No: 11402

Title: attribute “concept of resource(both classifier/instance)”

Source:

Thales: Sébastien Demathieu, [e-mail])

Summary:

The General Resource Model of MARTE seems to define the concept of "resource" both at the instance and classifier levels. For instance, the GRM::Resource stereotype extends both InstanceSpecification and Classifier.

The SwResource stereotype defined in the Software Resource Model of MARTE specializes the GRM::Resource stereotype. However, reading the SRM chapter, it seems that its use is much more focused on description of classifiers (to characterize properties or behavioral features for instance) than instances.

In that context, does it make sense to apply a SRM::SwResource stereotype or one of its subclasses (for instance SRM::SwSchedulableResource) on an instance specification? Note that it seems to be legal given that SRM::SwResource specializes GRM::Resource, which extends InstanceSpecification.

I would be pretty handy to do so, in order to describe a resource platform model provided in input of a scheduling analysis.

Resolution:
Complete the paragraph 7.3 with the rules for the default values of attributes of the stereotypes for instance of classifiers also stereotyped.

Revised Text:

Add the following paragraph to section 7.3:

When a stereotype is applied on an instance, and provided it can be also applied on classifiers, the value of the attributes not explicitly assigned in the annotation of the instance are taken in principle from the defaults in the profile stereotype definition, but they might be overridden by those in its corresponding classifier, if it happens to be annotated with the same stereotype.
Disposition: Resolved