${taskforce.name} Avatar
  1. OMG Task Force

UML Profile for Scheduling RTF — Open Issues

Open Closed All
Issues not resolved

Issues Descriptions

General issue

  • Key: SPTP11-1
  • Legacy Issue Number: 5875
  • Status: open  
  • Source: The MathWorks ( Alan Moore)
  • Summary:

    Need to say for each association in the domain models, how they map
    to UML with the SPT profile applied.

  • Reported: SPTP 1.0b1 — Fri, 28 Feb 2003 05:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Support high-level schedulability analysis

  • Key: SPTP11-2
  • Legacy Issue Number: 5919
  • Status: open  
  • Source: The MathWorks ( Alan Moore)
  • Summary:

    Often in the early stages of analysis, an the active objects, rather than
    their internal operations are treated as the schedulable entity. In order to
    support this mode of analysis, the stereotypes associated to schedulable
    entities, SAtrigger and SAresponse, must include in their base types all
    relevant classifiers and Instance

  • Reported: SPTP 1.0 — Tue, 29 Apr 2003 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

defining different UML extenssions

  • Key: SPTP11-5
  • Legacy Issue Number: 5998
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Sebastien Gerard)
  • Summary:

    1 - when defining the different UML extenssions (stereotypes/tagged
    > values) proposed ;in the context of the SPT profile, some of the
    > extenssions may be applied on different UML base class, but without having
    > everttime the same semantics. So the clear semantics of every extenssion
    > attached a given UML base class should be clarified every time it is
    > reuqired, that is to say every time there atre possible ambiguities

  • Reported: SPTP 1.0 — Fri, 18 Jul 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Performance Profile Loads need tags for throughput

  • Key: SPTP11-3
  • Legacy Issue Number: 5989
  • Status: open  
  • Source: Carleton University ( Murray Woodside)
  • Summary:

    The PAclosedLoad and PAopenLoad stereotypes should both have tags for
    throughput
    in [responses/unit_time]. The PAresource stereotype has already a
    PAthroughput tag
    of type Real, so this would be suitable.

    A more appropriate type for Throughput would be desirable.

    • PAperfValue is suitable for describing delay, and time between
      events, but
      not a rate.
    • RTarrivalPattern type is good for describing event sequences, but
      it
      assumes that the event pattern is imposed on the system. Throughput is
      usually a
      result, and often we don't know its pattern but only the mean rate.
    • A full treatment of throughput might have to treat traffic
      variability and
      self-similarity!!
  • Reported: SPTP 1.0 — Thu, 3 Jul 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Page: 3-38

  • Key: SPTP11-7
  • Legacy Issue Number: 8701
  • Status: open  
  • Source: Dalhousie University ( Xiaojia Deng)
  • Summary:

    On page 3-38, the table for stereotype <<GRMrelease>>, there are two "method" base class

  • Reported: SPTP 1.1 — Sat, 23 Apr 2005 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

PAstep needs tags for message size

  • Key: SPTP11-4
  • Legacy Issue Number: 5990
  • Status: open  
  • Source: Carleton University ( Murray Woodside)
  • Summary:

    There are no tags for message size, which is really important when the
    messages are
    transmitted over a communication network. For a synchronous message, there
    are in
    fact two message sizes: one for the request and the other for the reply.

    • As the UML messages are stereotyped as PAStep, an easy fix would be
      to add
      two tags to a step, PAinSize and PAoutSize of type Integer, to describe the
      size of
      the data needed as input for the step, and the size of the results produced
      by the
      step. Most steps would not need these tags.
  • Reported: SPTP 1.0 — Thu, 3 Jul 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

concepts that are redundant in schedulability and performance sub-profiles

  • Key: SPTP11-6
  • Legacy Issue Number: 6000
  • Status: open  
  • Source: CEA ( Gerard Sebastien)
  • Summary:

    3 - There are concepts that are redundant in both schedulability and
    > performance sub-profiles. The spt profile should have an additionnal
    > package factorizing these concepts. Moreover as one of the SPT use cases
    > ensures also modelling of real-time systems, this new package should be
    > dedicated to offer the users UML extenssions required to model real-time
    > aspects of application without any purpouse of validation, performance,
    > schedulability analysis ... , just modelling for example for code
    > generation.

  • Reported: SPTP 1.0 — Fri, 18 Jul 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT