Issue 12125: Item Flows on Activity Diagrams (sysml-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: Since ItemFlow is a stereotype of InformationFlow, it can be related to an ActivityEdge and depicted on an Activity Diagram. At least one tool has provided this capability. Clarify the use of ItemFlows on Activity Diagrams in the specification: If this is not desirable, then an additional constraint must be added to ItemFlows to prevent it. Personally, I like the idea of representing ItemFlows on ObjectFlows, but the semantic meaning of this representation is unclear. If this is retained, then it should be discussed in both chapter 9 and chapter 11. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: January 2, 2008: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: The UML metamodel shows information flows can be realized by activity edges, and that realization of information flow is intended to link more abstract models to more concrete (realizing) ones in ways determined by the modeler. Agreeing on the specific ways this is done with realizing activity edges and whether to standardize those in SysML will take more time. Disposition: Deferred Discussion: This issue is deferred because no other proposed resolution was voted on during the schedule of the SysML 1.2 RTF. Following is the discussion from a previous deferred resolution by the SysML 1.1 RTF: The UML metamodel shows information flows can be realized by activity edges, and that realization of information flow is intended to link more abstract models to more concrete (realizing) ones in ways determined by the modeler. Agreeing on the specific ways this is done with realizing activity edges and whether to standardize those in SysML will take more time. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 02 Jan 2008 14:24:02 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Rick Steiner Company: Raytheon mailFrom: fsteiner@raytheon.com Notification: Yes Specification: SysML Section: 9 FormalNumber: 2007-09-01 Version: 1.0 RevisionDate: 09//2007 Page: 64 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Description Item Flows on Activity Diagrams Since ItemFlow is a stereotype of InformationFlow, it can be related to an ActivityEdge and depicted on an Activity Diagram. At least one tool has provided this capability. Clarify the use of ItemFlows on Activity Diagrams in the specification: If this is not desirable, then an additional constraint must be added to ItemFlows to prevent it. Personally, I like the idea of representing ItemFlows on ObjectFlows, but the semantic meaning of this representation is unclear. If this is retained, then it should be discussed in both chapter 9 and chapter 11.