Issue 11840: Support for flows in activities (marte-ftf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Significant Summary: Subject: Support for flows in activities. Details: The current specification provides a limited support for flow in activity diagrams. The GCM chapter introduces the FlowSendAction stereotype. However, there is no way to indicate the pins used to define the data to send. At the same time, there is no action (such as FlowReceiveAction) to indicate how to receive a flow. It seems that activity parameters are an interesing alternative to specify incoming and outgoing flows in activity diagrams (SysML follows this approach). Proposed resolution: Remove the FlowSendAction stereotype and provide a support for BOTH incoming and outgoing flows through activity parameters (maybe a stereotype would need to be defined here). Resolution: See issue 11839 for disposition Revised Text: Disposition: See issue 11839 for disposition Actions taken: December 20, 2007: received issue October 16, 2009: closed issue Discussion: Discussion: Defining a complete support for flow in activities can be done with two different approaches. The first approach is to define actions for sending and receiving flows. GCM currently follows this approach but provides an incomplete support because it defines only a SendFlowAction action and not its accept/receive counterpart. The second approach is to follow SysML and to extend activity parameters and pins by a specific stereotype. This approach has advantages as it leverages more the capabilities offered by plain UML, for which execution semantics have been already precisely defined. The FTF as a whole did not have the opportunity to discuss the pros and cons of the two approaches. Therefore, it is better to defer this issue to collect everyone's input on this issue. Related issue: 11662 Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 20 Dec 2007 14:41:41 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Sébastien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: UML profile for MARTE Section: 11 FormalNumber: 07-08-04 Version: Beta 1 RevisionDate: 08/2007 Page: 117 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Description Subject: Support for flows in activities. Details: The current specification provides a limited support for flow in activity diagrams. The GCM chapter introduces the FlowSendAction stereotype. However, there is no way to indicate the pins used to define the data to send. At the same time, there is no action (such as FlowReceiveAction) to indicate how to receive a flow. It seems that activity parameters are an interesing alternative to specify incoming and outgoing flows in activity diagrams (SysML follows this approach). Proposed resolution: Remove the FlowSendAction stereotype and provide a support for BOTH incoming and outgoing flows through activity parameters (maybe a stereotype would need to be defined here).