Issue 13655: stereotype GRM::SchedulableResource should have an attribute describing its activation parameters (marte-rtf) Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com) Nature: Enhancement Severity: Critical 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. Resolution: 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. Revised Text: Actions taken: March 3, 2009: received issue February 17, 2010: transferred from MARTE FTF January 14, 2011: closed issue Discussion: Closed the issue with no change to the specification End of Annotations:===== m: webmaster@omg.org Date: 03 Mar 2009 03:35:05 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Huascar Espinoza Company: CEA mailFrom: huascar.espinoza@cea.fr Notification: Yes Specification: MARTE Section: GRM FormalNumber: 08-05-24 Version: Beta 2 RevisionDate: 08-05-24 Page: 93 Nature: Enhancement Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; MS-RTC LM 8) Description 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. Date: Wed, 4 Mar 2009 09:50:37 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: Juergen Boldt cc: marte-ftf@omg.org Subject: Re: Fwd: issue 13655 -- MARTE FTF issue User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) This is not necessary. The activation of resources is determined by activation parameters of functionality, i.e. by workload parameters in the analysis. Thus the resource activation is a partial result of the analysis. If there is no functionality defined, then a default scenario with a single step and a workload could be defined to convey resource activation. I think it is a mistake to push analysis attributes down into the core chapters. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Wed, 4 Mar 2009, Juergen Boldt wrote: X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 04 Mar 2009 07:43:56 -0500 To: issues@omg.org, mars@omg.org From: Juergen Boldt Subject: issue 13655 -- MARTE FTF issue From: webmaster@omg.org Date: 03 Mar 2009 03:35:05 -0500 To: Subject: Issue/Bug Report __________________________________________________________________________________________________ o Name: Huascar Espinoza o Company: CEA o mailFrom: huascar.espinoza@cea.fr o Notification: Yes o Specification: MARTE o Section: GRM o FormalNumber: 08-05-24 o Version: Beta 2 o RevisionDate: 08-05-24 o Page: 93 o Nature: Enhancement o Severity: Critical o HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; MS-RTC LM 8) Description 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. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Date: Wed, 04 Mar 2009 16:56:48 +0100 From: Julio Medina User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en To: cmw@sce.carleton.ca CC: Juergen Boldt , marte-ftf@omg.org Subject: Re: Fwd: issue 13655 -- MARTE FTF issue X-OriginalArrivalTime: 04 Mar 2009 15:58:58.0236 (UTC) FILETIME=[20B9CFC0:01C99CE2] X-imss-version: 2.053 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:5.6.1016(16500.000) X-imss-scores: Clean:99.73300 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) I have given this same opinion, and I do think that having activation rates is clearly a description of the application not of the resources. Whoever needs this combination may either define a specific platform configuration with SRM, a model of computation with RTUnits or an analysis context with the appropriate platform and workloadbehaviors (which includes the arrivalpattern/step[or scenario]/observations) I suggest to close no change this issue, but if you prefer to keep it for future revisions of MARTE, this kind of modeling patterns is a good candidate to be included either in an enhanced version of SRM or as one of the possible models of computation (the simplest one) to be described in HLAM. Cheers, Julio Murray Woodside wrote: This is not necessary. The activation of resources is determined by activation parameters of functionality, i.e. by workload parameters in the analysis. Thus the resource activation is a partial result of the analysis. If there is no functionality defined, then a default scenario with a single step and a workload could be defined to convey resource activation. I think it is a mistake to push analysis attributes down into the core chapters. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Wed, 4 Mar 2009, Juergen Boldt wrote: X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 04 Mar 2009 07:43:56 -0500 To: issues@omg.org, mars@omg.org From: Juergen Boldt Subject: issue 13655 -- MARTE FTF issue From: webmaster@omg.org Date: 03 Mar 2009 03:35:05 -0500 To: Subject: Issue/Bug Report __________________________________________________________________________________________________ o Name: Huascar Espinoza o Company: CEA o mailFrom: huascar.espinoza@cea.fr o Notification: Yes o Specification: MARTE o Section: GRM o FormalNumber: 08-05-24 o Version: Beta 2 o RevisionDate: 08-05-24 o Page: 93 o Nature: Enhancement o Severity: Critical o HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; MS-RTC LM 8) Description 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. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Date: Fri, 28 May 2010 12:51:52 -0400 From: "Chonoles, Michael J" Subject: RE: MARTE Ballot 2: Problem with resolution of Issue 13655 To: "Chonoles, Michael J" , GERARD Sebastien 166342 , "marte-rtf@omg.org" Thread-Topic: MARTE Ballot 2: Problem with resolution of Issue 13655 Thread-Index: Acr8DzFGhiB+VCqbR2y6U/G7O41oSgCdSC1AAAA8MrA= Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: In this issue, Dr. Espinoza, identifies a missing attribute for the GRM::SchedulableResource. The responder indicates that the missing attribute does not belong on SchedulableResource and closes it as not in the scope of GRM. See below: Discussion: 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. Is this RTF for GRM or for MARTE as a whole? We normally don.t require the issue writer to completely describe the fix. Are you requesting Dr Espinoza to reword it against HLAM, and if that doesn.t work, to reissue it against SRM? I believe the RTFs responses should speak for the RTF, not just the area of one package leader. Michael Lockheed Martin From: Chonoles, Michael J Sent: Friday, May 28, 2010 12:43 PM To: 'GERARD Sebastien 166342'; marte-rtf@omg.org Subject: MARTE Ballot 2: Problem with resolution of Issue 12411 Looking at the resolution 12411 (no-change), the discussion says: Discussion: The example is not a composite structure; the caption text of the figure may have mislead the reader. It shows just a class diagram with dependencies among them. It seems to me, that if we can find a part of the spec to blame for the confusion, then that part of spec should be changed. In this case, the change should be simple and non-controversial. But as currently stated, LMCO would not vote for ignoring a confusing caption. Michael Jesse Chonoles Lockheed Martin From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Tuesday, May 25, 2010 9:36 AM To: marte-rtf@omg.org Subject: MARTE 1.1 RTF: start of ballot 2 voting period Hi all, Following this link you will find a bundle of the resolutions gathered in the ballot 2 for MARTE 1.1 RTF: http://www.omgwiki.org/marte1.1-rtf/doku.php?id=marte_1.0_rtf_ballot_2#voting_material_for_ballot_2 The timing for the MARTE 1.1 RTF ballot 2 voting period is: From Mai 25 to June 5 (12 pm CET), 2010. For memory, following companies did not vote on ballot1: 88solutions (Manfred Koethe), BAE SYSTEMS (Stu Lewin), EADS (Yves Bernard), International Business Machines (Irv Badr - co-chair), No Magic, Inc. (Andrius Strazdauskas) and Universidad de Cantabria (Julio Mdeina). èf these companies miss the next vote, according to the rules, they will lost their voting right from the RTF!!! Thanks for your incoming votes, Best. Séstien. Dr. Séstien Gérd Head of MDD for DRES research project CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE) Boî courrier 94, GIF SUR YVETTE CEDEX, F-91191 France Phone/fax : +33 1 69 08 58 24 / 83 95 Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org http://www.eclipse.org/modeling/mdt/?project=papyrus Before printing, think about the environment Subject: RE: MARTE Ballot 2: Problem with resolution of Issue 13655 Date: Sat, 29 May 2010 19:30:46 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MARTE Ballot 2: Problem with resolution of Issue 13655 Thread-Index: Acr8DzFGhiB+VCqbR2y6U/G7O41oSgCdSC1AAAA8MrAAM7O+0A== From: "GERARD Sebastien 166342" To: "Chonoles, Michael J" , X-OriginalArrivalTime: 29 May 2010 17:30:46.0884 (UTC) FILETIME=[AC700A40:01CAFF54] Hi, I agree that the text of the resolution is maybe not clear, but I think that the resolution wants to say that the extension required in the issue on a concept of GRM seems to be irrelevant for any concept of GRM so the sentence: ".it as not in the scope of GRM.". For achieving what the issue is required, the discussion concludes that the user can use concepts of HLAM as for exemple and that it is not needed to extend GRM for that. Séstien. Dr. Séstien Gérd Head of MDD for DRES research project CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE) Boî courrier 94, GIF SUR YVETTE CEDEX, F-91191 France Phone/fax : +33 1 69 08 58 24 / 83 95 Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org http://www.eclipse.org/modeling/mdt/?project=papyrus Before printing, think about the environment -------------------------------------------------------------------------------- De : Chonoles, Michael J [mailto:michael.j.chonoles@lmco.com] Envoyé vendredi 28 mai 2010 18:52 À: Chonoles, Michael J; GERARD Sebastien 166342; marte-rtf@omg.org Objet : RE: MARTE Ballot 2: Problem with resolution of Issue 13655 In this issue, Dr. Espinoza, identifies a missing attribute for the GRM::SchedulableResource. The responder indicates that the missing attribute does not belong on SchedulableResource and closes it as not in the scope of GRM. See below: Discussion: 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. Is this RTF for GRM or for MARTE as a whole? We normally don.t require the issue writer to completely describe the fix. Are you requesting Dr Espinoza to reword it against HLAM, and if that doesn.t work, to reissue it against SRM? I believe the RTFs responses should speak for the RTF, not just the area of one package leader. Michael Lockheed Martin From: Chonoles, Michael J Sent: Friday, May 28, 2010 12:43 PM To: 'GERARD Sebastien 166342'; marte-rtf@omg.org Subject: MARTE Ballot 2: Problem with resolution of Issue 12411 Looking at the resolution 12411 (no-change), the discussion says: Discussion: The example is not a composite structure; the caption text of the figure may have mislead the reader. It shows just a class diagram with dependencies among them. It seems to me, that if we can find a part of the spec to blame for the confusion, then that part of spec should be changed. In this case, the change should be simple and non-controversial. But as currently stated, LMCO would not vote for ignoring a confusing caption. Michael Jesse Chonoles Lockheed Martin From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Tuesday, May 25, 2010 9:36 AM To: marte-rtf@omg.org Subject: MARTE 1.1 RTF: start of ballot 2 voting period Hi all, Following this link you will find a bundle of the resolutions gathered in the ballot 2 for MARTE 1.1 RTF: http://www.omgwiki.org/marte1.1-rtf/doku.php?id=marte_1.0_rtf_ballot_2#voting_material_for_ballot_2 The timing for the MARTE 1.1 RTF ballot 2 voting period is: From Mai 25 to June 5 (12 pm CET), 2010. For memory, following companies did not vote on ballot1: 88solutions (Manfred Koethe), BAE SYSTEMS (Stu Lewin), EADS (Yves Bernard), International Business Machines (Irv Badr - co-chair), No Magic, Inc. (Andrius Strazdauskas) and Universidad de Cantabria (Julio Mdeina). èf these companies miss the next vote, according to the rules, they will lost their voting right from the RTF!!! Thanks for your incoming votes, Best. Séstien. Dr. Séstien Gérd Head of MDD for DRES research project CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE) Boî courrier 94, GIF SUR YVETTE CEDEX, F-91191 France Phone/fax : +33 1 69 08 58 24 / 83 95 Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org http://www.eclipse.org/modeling/mdt/?project=papyrus Before printing, think about the environment Date: Mon, 31 May 2010 21:04:42 -0400 From: "Chonoles, Michael J" Subject: RE: MARTE Ballot 2: Problem with resolution of Issue 13655 To: GERARD Sebastien 166342 , "marte-rtf@omg.org" Thread-Topic: MARTE Ballot 2: Problem with resolution of Issue 13655 Thread-Index: Acr8DzFGhiB+VCqbR2y6U/G7O41oSgCdSC1AAAA8MrAAM7O+0AB0gxug Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Yes, but it appears that you are asking the submitter to re-submit the issue and directed it to HLAM. Generally, the RTF response should be for the whole of MARTE not just for one area. Michael From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Saturday, May 29, 2010 1:31 PM To: Chonoles, Michael J; marte-rtf@omg.org Subject: RE: MARTE Ballot 2: Problem with resolution of Issue 13655 Hi, I agree that the text of the resolution is maybe not clear, but I think that the resolution wants to say that the extension required in the issue on a concept of GRM seems to be irrelevant for any concept of GRM so the sentence: ".it as not in the scope of GRM.". For achieving what the issue is required, the discussion concludes that the user can use concepts of HLAM as for exemple and that it is not needed to extend GRM for that. Séstien. Dr. Séstien Gérd Head of MDD for DRES research project CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE) Boî courrier 94, GIF SUR YVETTE CEDEX, F-91191 France Phone/fax : +33 1 69 08 58 24 / 83 95 Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org http://www.eclipse.org/modeling/mdt/?project=papyrus Before printing, think about the environment -------------------------------------------------------------------------------- De : Chonoles, Michael J [mailto:michael.j.chonoles@lmco.com] Envoyé vendredi 28 mai 2010 18:52 À: Chonoles, Michael J; GERARD Sebastien 166342; marte-rtf@omg.org Objet : RE: MARTE Ballot 2: Problem with resolution of Issue 13655 In this issue, Dr. Espinoza, identifies a missing attribute for the GRM::SchedulableResource. The responder indicates that the missing attribute does not belong on SchedulableResource and closes it as not in the scope of GRM. See below: Discussion: 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. Is this RTF for GRM or for MARTE as a whole? We normally don.t require the issue writer to completely describe the fix. Are you requesting Dr Espinoza to reword it against HLAM, and if that doesn.t work, to reissue it against SRM? I believe the RTFs responses should speak for the RTF, not just the area of one package leader. Michael Lockheed Martin From: Chonoles, Michael J Sent: Friday, May 28, 2010 12:43 PM To: 'GERARD Sebastien 166342'; marte-rtf@omg.org Subject: MARTE Ballot 2: Problem with resolution of Issue 12411 Looking at the resolution 12411 (no-change), the discussion says: Discussion: The example is not a composite structure; the caption text of the figure may have mislead the reader. It shows just a class diagram with dependencies among them. It seems to me, that if we can find a part of the spec to blame for the confusion, then that part of spec should be changed. In this case, the change should be simple and non-controversial. But as currently stated, LMCO would not vote for ignoring a confusing caption. Michael Jesse Chonoles Lockheed Martin From: GERARD Sebastien 166342 [mailto:Sebastien.GERARD@cea.fr] Sent: Tuesday, May 25, 2010 9:36 AM To: marte-rtf@omg.org Subject: MARTE 1.1 RTF: start of ballot 2 voting period Hi all, Following this link you will find a bundle of the resolutions gathered in the ballot 2 for MARTE 1.1 RTF: http://www.omgwiki.org/marte1.1-rtf/doku.php?id=marte_1.0_rtf_ballot_2#voting_material_for_ballot_2 The timing for the MARTE 1.1 RTF ballot 2 voting period is: From Mai 25 to June 5 (12 pm CET), 2010. For memory, following companies did not vote on ballot1: 88solutions (Manfred Koethe), BAE SYSTEMS (Stu Lewin), EADS (Yves Bernard), International Business Machines (Irv Badr - co-chair), No Magic, Inc. (Andrius Strazdauskas) and Universidad de Cantabria (Julio Mdeina). èf these companies miss the next vote, according to the rules, they will lost their voting right from the RTF!!! Thanks for your incoming votes, Best. Séstien. Dr. Séstien Gérd Head of MDD for DRES research project CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE) Boî courrier 94, GIF SUR YVETTE CEDEX, F-91191 France Phone/fax : +33 1 69 08 58 24 / 83 95 Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org http://www.eclipse.org/modeling/mdt/?project=papyrus Before printing, think about the environment