MARTE 1.0 FTF Avatar
  1. OMG Issue

MARTE_ — stereotype GRM::SchedulableResource should have an attribute describing its activation parameters

  • Key: MARTE_-66
  • Legacy Issue Number: 13655
  • Status: closed  
  • Source: Fundacion Tecnalia Research and Innovation ( Huascar Espinoza)
  • Summary:

    The stereotype GRM::SchedulableResource should have an attribute describing its activation parameters (arrival pattern and parameters). This is useful in multi-rate systems, where, in addition to the activations defined at application level (activation events triggering action/event chains), OS tasks/threads can be defined with a given activation rate. For instance, almost all automotive systems are multi-rate systems. Even if the functional application appears as a single rate system, multiplexing mechanisms both in the communication or in data sampling mechanisms can induce to more complicated timing behaviors, which are a characteristics of multi-rate systems.

  • Reported: MARTE 1.0b2 — Tue, 3 Mar 2009 05:00 GMT
  • Disposition: Resolved — MARTE 1.0
  • Disposition Summary:

    The activation pattern is a characteristic of the application, not of the platform. In
    fact it is usually different in each execution scenario. The concept of task, as
    used in languages and formalisms is for all of them a way to create an
    application, not a description of the platform. A modeling element that may serve
    for this purpose would be much closer in meaning to an RTUnit than to a
    SchedulableReource. So the extension requested is not in the scope of GRM. A
    task is clearly a design modeling element and if not in HLAM it may probably fit in
    SRM.

  • Updated: Wed, 11 Mar 2015 01:53 GMT