UML Profile for MARTE Avatar
  1. OMG Specification

UML Profile for MARTE — Open Issues

  • Acronym: MARTE
  • Issues Count: 11
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

MARTE issue: Observation does not allow specification of time value

  • Key: MARTE13-14
  • Legacy Issue Number: 18657
  • Status: open  
  • Source: Simula Research Laboratory ( Bran Selic)
  • Summary:

    In the current UML metamodel, there is no link from the metaclass Observation to a ValueSpecificaiton that can be used to specify the time value of the Observation. As a result, it is not possible to directly assign time values to TimedInstantObservation or TimedDurationObservation.

    This means that it is not possible to refer to the time values of such observations in a time expression.

    One easy solution is to create an association from the TimedObservation stereotype to the UML ValueSpecification metaclass (role name "value"). This could then be used to store the time value associated with either kind of time observation.

  • Reported: MARTE 1.0 — Fri, 12 Apr 2013 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

The notion of "access connection" needs to be explicited in the AADL annex (A.2) of MARTE

  • Key: MARTE13-13
  • Legacy Issue Number: 15275
  • Status: open  
  • Source: THALES ( Madeleine Faugere)
  • Summary:

    The notion of "access connection" needs to be explicited in the AADL annex (A.2) of MARTE

  • Reported: MARTE 1.0 — Sat, 5 Jun 2010 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

Precise the shape of an array of ports of an array of parts

  • Key: MARTE13-12
  • Legacy Issue Number: 15659
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    When a shaped port belongs to a shaped part, one should understand its shape as the product of both shapes as stated in the definition of the tiler. This should be stated here for the case when the reshape stereotype can be ommitted.

  • Reported: MARTE 1.0 — Tue, 28 Sep 2010 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

[Time: Examples]

  • Key: MARTE13-9
  • Legacy Issue Number: 11767
  • Status: open  
  • Source: Fundacion Tecnalia Research and Innovation ( Huascar Espinoza)
  • Summary:

    [Time: Examples] One important specification feature in the embedded system domain is the Timing diagram. I propose to include examples to illustrate the use of the MARTE observation concepts and time expressions with Timing Diagrams

  • Reported: MARTE 1.0b1 — Fri, 7 Dec 2007 05:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

Missing mappings between analysis duration, arrival patterns and clock constraints

  • Key: MARTE13-8
  • Legacy Issue Number: 13654
  • Status: open  
  • Source: Fundacion Tecnalia Research and Innovation ( Huascar Espinoza)
  • Summary:

    Having icons and symbols for stereotypes improves models comprehesibility. For instance, HRM and SRM chapters provide graphical representations for most of the stereotypes. However, the GRM subprofile, which is shared by other chapters (analysis modeling parts of MARTE), has not such graphical representation. We propose to add icons and symbols (likely similar to SRM and HRM's ones) to GRM stereotypes.

  • Reported: MARTE 1.0b2 — Tue, 3 Mar 2009 05:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

Missing mappings between analysis duration, arrival patterns and clock constraints

  • Key: MARTE13-7
  • Legacy Issue Number: 14899
  • Status: open  
  • Source: THALES ( Sebastien Demathieu)
  • Summary:

    The mappings between the analysis arrival patterns (periodic, sporatic, …) and Time durations, and clock constraints in CCSL should be defined in the specification.

  • Reported: MARTE 1.0 — Thu, 31 Dec 2009 05:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

Align the NFP profile and domain model with the QUVD meta-model

  • Key: MARTE13-6
  • Legacy Issue Number: 14893
  • Status: open  
  • Source: THALES ( Sebastien Demathieu)
  • Summary:

    Previous discussions between the SysML and MARTE communities have allowed relationships between both languages. An important convergence area relates to the notions of quantities, unit and dimensions. The SysML 1.2 RTF and the MARTE FTF work resulted in the definition of the QUVD meta-model (SysML Annex C.5). The MARTE NFP profile has not been yet entirely aligned on the QUVD meta-model. It would need aligned stereotyped when applicable (e.g. dimension vs. quantity type)

  • Reported: MARTE 1.0 — Thu, 31 Dec 2009 05:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

SwResource should be a direct specialization of Resource, like its hardware counterpart

  • Key: MARTE13-5
  • Legacy Issue Number: 14898
  • Status: open  
  • Source: THALES ( Sebastien Demathieu)
  • Summary:

    In the SRM meta-model, the SwResource specializes ResourceManager which makes SwSchedulableResource themselves. SwResource should be a direct specialization of Resource, like its hardware counterpart.

  • Reported: MARTE 1.0 — Thu, 31 Dec 2009 05:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

Questions on observators within GQAM and SAM

  • Key: MARTE13-3
  • Legacy Issue Number: 18567
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Sebastien Gerard)
  • Summary:

    I was wondering, why two kinds of observators was designed within the GQAM as denoted in the figure shown below:

    Why not gathering both into one single stereotype? I propose to keep the second one, GaLatencyObs.

    In addition, I was also wondering why the <<SaSchedObs>> stereotype defined within SAM was not inheriting from <<GaLatencyObs>> instead of <<GaTimedObs>>?

    What do you think?

  • Reported: MARTE 1.0 — Tue, 19 Mar 2013 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

«GaWorkloadGenerator» and its pop attribute

  • Key: MARTE13-2
  • Legacy Issue Number: 18576
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Sebastien Gerard)
  • Summary:

    Can someone clarify the meaning of the pop attribute of the «GaWorkloadGenerator» stereotype?

  • Reported: MARTE 1.0 — Mon, 25 Mar 2013 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT

About Gacenario::

  • Key: MARTE13-1
  • Legacy Issue Number: 18581
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Sebastien Gerard)
  • Summary:

    GaScenario has the attribute utilization. Its definition is : “The occupancy of the scenario, computed as the mean number of scenario instances active at any one time.”. What does “occupancy” mean?

  • Reported: MARTE 1.0 — Tue, 26 Mar 2013 04:00 GMT
  • Updated: Tue, 8 Jan 2019 19:22 GMT