Issue 12865: Section: GQAM-SAM-PAM (marte-ftf) Source: (, ) Nature: Revision Severity: Critical Summary: The attributes CommTxOvh and CommRcvOvh in a GQAM:ExecutionHost (F.10.8) limit comunication of a host to only one network/protocol. In fact the overhead due to communication maight be very dificultly expressed by simply a duration... Resolution: Revised Text: Actions taken: September 26, 2008: received issue October 16, 2009: closed issue Discussion: This is a misunderstanding. Communications overhead is not included in GQAM, but is included in PAM (chapter 17) The CommTxOvh and CommRcvOvh parameters are only a simplified way to express comunications behaviour and overheads. The alternatives as explained in Section 17.2.2.6 also include (1) describing a communications layer separately and invoking it as an “external operation” (i.e. defined separately). The protocol with its overheads and sources of delay can be described at any level of detail there. (2) describing a communications layer, similarly but tied more firmly to the layer objects and structure (3) describing the delays by a behaviour scenario Examples are given in chapter 17. For SAM, since timing is critical the communications process can be described in full as a subsystem. SACommStep includes only summary properties of an abstract view of communications delay, for situations where that is appropriate. Thus there are facilities for the desired modeling. They may not be perfect but they provide considerable power. Disposition: Closed, no change End of Annotations:===== m: webmaster@omg.org Date: 26 Sep 2008 10:20:12 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Patricia López Company: Universidad de Cantabria mailFrom: lopezpa@unican.es Notification: Yes Specification: UML Profile for MARTE Section: GQAM-SAM-PAM FormalNumber: ptc/08-06-08 Version: Beta 2 RevisionDate: 06/08/2008 Page: 109+ Nature: Revision Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Description - The attributes CommTxOvh and CommRcvOvh in a GQAM:ExecutionHost (F.10.8) limit comunication of a host to only one network/protocol. In fact the overhead due to communication maight be very dificultly expressed by simply a duration... Subject: [MARTE] Issue 12865: Time Overheads In Execution Hosts... Date: Fri, 13 Feb 2009 12:07:58 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MARTE] Issue 12865: Time Overheads In Execution Hosts... Thread-Index: AcmNy1PkpK3anBfhSjWftcCM4MkCOg== From: "ESPINOZA Huascar 218344" To: , , Cc: X-OriginalArrivalTime: 13 Feb 2009 11:07:59.0080 (UTC) FILETIME=[5468C680:01C98DCB] Hi Murray, all, Regarding issue 12865, with a resolution in Ballot 1 (I copied below the resolution for fast reference), I have some comments: 1) There is NO a misunderstanding as said below. Those communication overheads are defined in the GQAM chapter. 2) The solution should be common for SAM and PAM, so it should be in GQAM. 3) It is not clear for me (from the text) how to model different overheads for communication treatment (cost for sending and receiving messages) in the same processor. The delays of .behavior scenarios. or .steps. do not take into account these overheads explicitely. Thank you for your clarifications. Regards, Huascar Disposition: Closed, no change OMG Issue No: 12865 Title: Section: GQAM-SAM-PAM Source: none given Summary: The attributes CommTxOvh and CommRcvOvh in a GQAM:ExecutionHost (F.10.8) limit comunication of a host to only one network/protocol. In fact the overhead due to communication maight be very dificultly expressed by simply a duration... Discussion: This is a misunderstanding. Communications overhead is not included in GQAM, but is included in PAM (chapter 17) The CommTxOvh and CommRcvOvh parameters are only a simplified way to express comunications behaviour and overheads. The alternatives as explained in Section 17.2.2.6 also include (1) describing a communications layer separately and invoking it as an .external operation. (i.e. defined separately). The protocol with its overheads and sources of delay can be described at any level of detail there. (2) describing a communications layer, similarly but tied more firmly to the layer objects and structure (3) describing the delays by a behaviour scenario Examples are given in chapter 17. For SAM, since timing is critical the communications process can be described in full as a subsystem. SACommStep includes only summary properties of an abstract view of communications delay, for situations where that is appropriate. Thus there are facilities for the desired modeling. They may not be perfect but they provide considerable power. Disposition: Closed, no change -- Huascar ESPINOZA, Ph.D. CEA LIST Model-Driven Engineering for Real-Time Embedded Systems 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France