Issue 15310: GRM:Support for Time table driven schedules (marte-rtf)
Source: Universidad de Cantabria (Dr. Julio Medina, julio.medina(at)unican.es)
Nature: Enhancement
Severity: Significant
Summary: Having the opaque expresion attribute "schedule" in the Scheduler in GRM lead to a very open way of expressing fixed schedules or non-traditional scheduling policies. This is the case of time triggered sets of tasks in particular, but also of any form of table driven schedule, like IMA platforms. Following a general approach but formalizing the way of expressing schedules as a set of labeled timed windows would make the exchange of information between strict time triggered platforms design intent and its corresponding analysis models easyer and in a standardized way.  

An alternative to study may be formalizing the attribute “schedule” of a scheduler to include at least the frame_cycle_time, and the list of “windows” or “time_slots” to be managed as schedulable resources. To do this the easiest way may be to make them part of a list inside the schedule indexed by a key that match the scheduling parameters field of the schedulable resources that are attached to the scheduler.
Resolution: 
Revised Text: 
Actions taken:
June 26, 2010: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 26 Jun 2010 16:37:10 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Julio Medina
Company:       Universidad de Cantabria
mailFrom:      julio.medina@unican.es
Notification:  Yes
Specification: UML Profile for MARTE
Section:       GRM
FormalNumber:  formal/2009-11-02
Version:       1.0
RevisionDate:  November 2009
Page:          96-97
Title:         GRM:Support for Time table driven schedules.
Nature:        Enhancement
Severity:      Significant
test:          3qw8
B1:            Report Issue


Description:


Having the opaque expresion attribute "schedule" in the Scheduler in GRM lead to a very open way of expressing fixed schedules or non-traditional scheduling policies. This is the case of time triggered sets of tasks in particular, but also of any form of table driven schedule, like IMA platforms. Following a general approach but formalizing the way of expressing schedules as a set of labeled timed windows would make the exchange of information between strict time triggered platforms design intent and its corresponding analysis models easyer and in a standardized way.  

An alternative to study may be formalizing the attribute .schedule. of a scheduler to include at least the frame_cycle_time, and the list of .windows. or .time_slots. to be managed as schedulable resources. To do this the easiest way may be to make them part of a list inside the schedule indexed by a key that match the scheduling parameters field of the schedulable resources that are attached to the scheduler.