Issue 11659: Section: 11.2.1 (marte-ftf) Source: Commissariat a l Energie Atomique-CEA (Dr. Arnaud Cuccuru, arnaud.cuccuru(at)cea.fr) Nature: Enhancement Severity: Significant Summary: The ability to type FlowPorts by Signals (or by FlowSpecifications containing FlowProperties typed by Signals) is confusing. MessagePorts (which are just a light specialization of UML ports) already enable signal-based communications. Things would be clearer if FlowPorts would only enable data-flow communications, and if MessagePorts would be used for service or signal-based communications (just as classical UML ports are). I suppose that this feature is inherited from SysML, but this is however confusing in the context of UML Resolution: Revised Text: Actions taken: November 20, 2007: received issue February 17, 2010: closed issue Discussion: The design rationale for GCM was to rely on the concept of FlowPort already defined in SysML. The ability to type a flow port by a signal directly comes from SysML. That needs to be leave as unchanged to keep the consistency with the SysML::FlowPort. Disposition: Closed, no change End of Annotations:===== m: webmaster@omg.org Date: 20 Nov 2007 09:51:14 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Arnaud Cuccuru Company: Commissariat a l Energie Atomique - CEA/LIST mailFrom: arnaud.cuccuru@cea.fr Notification: Yes Specification: A UML Profile for MARTE Section: 11.2.1 FormalNumber: ptc/07-08-04 Version: Beta 1 RevisionDate: 04/08/07 Page: 119 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0 Description The ability to type FlowPorts by Signals (or by FlowSpecifications containing FlowProperties typed by Signals) is confusing. MessagePorts (which are just a light specialization of UML ports) already enable signal-based communications. Things would be clearer if FlowPorts would only enable data-flow communications, and if MessagePorts would be used for service or signal-based communications (just as classical UML ports are). I suppose that this feature is inherited from SysML, but this is however confusing in the context of UML.