Issue 14902: Inconsistent definition of CommunicationChannel properties (marte-rtf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Significant Summary: Annex F defines a CommunicationChannel.msgSize property while the meta-model and the profile defines a packetSize property. Note that the term 'packet' may not generic enough for the concept of CommunicationChannel Resolution: For consistency, change the attributes of a CommunicationChannel in Annex F section F.10.4, and the GaCommChannel stereotype description in section 15.3.2.3 so that they appear as packetSize and utilization, like in Fig 15.5. Revised Text: In Section F.10.4 CommunicationChannel, page 673, change Attributes from: msgSize: NFP_DataSize [0..1] The size of the message. To: packetSize: NFP_DataSize [0..1] The size of the data unit handled by the channel. utilization: NFP_Real [0..1] The fraction of the Communication Host capacity used by the Channel. This is typically a result of the analysis better than a specification.. In Section 15.3.2.3 GaCommChannel page 300, change Attributes from: • packetSize: NFP_DataSize [0..1] The size of the data unit handled by the channel. To: • packetSize: NFP_DataSize [0..1] The size of the data unit handled by the channel. • utilization: NFP_Real [0..1] The fraction of the Communication Host capacity used by the Channel. This is typically a result of the analysis better than a specification.. Disposition: Resolved Actions taken: December 31, 2009: received issue January 14, 2011: closed issue Discussion: The term “packet” is used here to emphasize the “quantum”-based nature of the channel usage. The term messageSize is more adequate for looking at the concept from the users/application side while packet seems more adequate for the platform/resource viewpoint. For consistency I suggest to correct the Annex F accordingly. Also the attribute utilization that appears in Fig15.5 should be in both annex F description and the stereotype description. End of Annotations:===== m: webmaster@omg.org Date: 31 Dec 2009 07:45:57 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Séstien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: MARTE Section: GQAM FormalNumber: 09-11-02 Version: 1.0 RevisionDate: 11/2009 Page: 293 Title: Inconsistent definition of CommunicationChannel properties Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: Annex F defines a CommunicationChannel.msgSize property while the meta-model and the profile defines a packetSize property. Note that the term 'packet' may not generic enough for the concept of CommunicationChannel.