Issue 15292: GRM:Support for Time table driven schedules (marte-rtf) Source: Universidad de Cantabria (Dr. Julio Medina, julio.medina(at)unican.es) Nature: Uncategorized Issue Severity: Summary: MARTE, formal/2009-11-02, GRM chapter, pag 96-97, enhancement GRM:Support for Time table driven schedules. Having the opaque expression 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. 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 easier 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: The current structure grants the designer the capacity of describing the schedule to use by means of an opaque expression, and the scheduling parameters for the table driven policy in the way of an open format string. In order to facilitate the description of more precise and standardized schedules, a concrete format for these types has been proposed. The necessary attributes are presented. For the scheduler the attribute “schedule” will be formalized to include at least the frame_cycle_time, and the list of “windows” or “time_slots” for the partitions, for doing this there are two alternatives (a) 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, or (b) compose the list by considering the allocated schedulable resources with their corresponding schedulingParameters, changing the current type string used for the TableEntry field into the necessary time_slot data type tuple. Alternative (a) is easier to set into the standard and the models are easier to check for consistency, hence is the one proposed. It comprises the formalization of the opaque expression used for the attribute “schedule” into a structure like the one shown in the next figure: Revised Text: see pages 156 - 162 of ptc/2010-08-30 for revised text Actions taken: June 27, 2010: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== te: Sat, 26 Jun 2010 23:10:09 +0200 From: Julio Medina User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) To: Juergen Boldt Subject: Issue Number for MARTE:GRM:Support for Time table driven schedules. X-OriginalArrivalTime: 26 Jun 2010 21:10:03.0593 (UTC) FILETIME=[F2038390:01CB1573] X-imss-version: 2.054 X-imss-result: Passed X-imss-scanInfo: M:P L:E SM:0 X-imss-tmaseResult: TT:0 TS:0.0000 TC:00 TRN:0 TV:6.0.1038(17470.002) X-imss-scores: Clean:86.67921 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:2 S:2 R:2 (0.0000 0.0000) Hi Juergen, I am sorry for writing on Saturday to you, but there is an issue about which people in the RTF of MARTE need to discuss soon next week in the context of an european project review, which I have just sent using the web page dialog. I need the issue number to refer to it in the documents that we will deliver on Monday. I understand you may have many other things to do on Monday, but considering the time shift if you get that number for us along the morning would really help. Just in case I include here the data sent: --------------------------------------------------- MARTE, formal/2009-11-02, GRM chapter, pag 96-97, enhancement GRM:Support for Time table driven schedules. Having the opaque expression 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. 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 easier 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. ------------------------------------------- Thank you very much for your attention Juergen. With my best regards, Julio --------------------------------------------------------------------- Julio Luis Medina Pasaje PhD. Assistant Professor E-mail: julio.medina@unican.es Grupo de Computadores y Tiempo Real URL: http://www.ctr.unican.es Dpto. de ElectrĂła y Computadores Phone : +34 942 201477 Universidad de Cantabria Fax : +34 942 201402 Avda. Los Castros s/n - 39005 - Santander - SPAIN --------------------------------------------------------------------