Issue 13197: Representation of nested object nodes in activity diagrams (sysml-rtf) Source: (Mr. Sanford A. Friedenthal, ) Nature: Clarification Severity: Minor Summary: Issue: Representation of nested object nodes in activity diagrams. Discussion: It is desirable to be able to represnt nesting of object nodes on activity diagrams to reflect one or more levels of nested properties of the classifier that types the object node. For example, if water is shown as an object node, and it is desired to refer to the temperature of water, then it should be possible to reflect this property on the activity diagram using the notations that are used on ibd's. In particular, one may want to use either a nested rectangle to represent the property, or the dot notation. Proposed update. In the diagram extensions for activity diagrams in Section 11.3.1.4, add a clarifying statement that nested properties of the classifier that types an object node can be represented on activity diagrams either using the nested rectangle notation or the dot notation similar to the use of nesting on ibd's and parametric diagrams. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: December 31, 2008: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: Following is the discussion from a previous deferred resolution by the SysML 1.2 RTF: Filer’s elaboration: Intent is to be able to represent object nodes on activity diagrams with nested properties using either the nested notation or dot notation. An example where this would be useful is to model the manufacturing process as a series of assembly steps for an assembly such as an engine. Assume any given action represents a step in the process where a partially assembled engine is input along with another input part such as a cylinder. The output is a partially assembled engine with the cylinder included. I would like to highlight the output object node as the engine with the cylinder part nested in the engine. The intent would be to use the "create" parameter effect (refer to ParameterEffectKind in UML superstructure 12.3.4.1, .2 which shows the ParameterEffectKind as create, read, update, delete or the SysML equivalent of create, not modify, modify, destroy). In the engine assembly process, the effect kind would be create indicating the creation of the new engine assembly with the cylinder included. SysML 1.3 RTF Disposition: Deferred OMG Issue No: 13197 Document ptc/2011-08-08 Page 180 The addition of class notation to an activity would not specify that the output engine has the cylinder, this could only be done by postconditions on the assembly action/subactivity. It would also be a significant change to introduce class notations onto the activity diagrams, requiring changes in vendor implementations. The proposed modification doesn't address the use case and would require significant changes in implementation. The issue is deferred for further discussion of other solutions. This issue is being deferred because no proposed resolution was voted on during the schedule of the SysML 1.3 RTF. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 31 Dec 2008 19:58:06 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Sanford Friedenthal Company: Lockheed Martin mailFrom: sanford.friedenthal@lmco.com Notification: Yes Specification: SysML Section: 11.3.1.4 FormalNumber: formal/2008-11-02 Version: 1.1 RevisionDate: November, 2008 Page: 97-98 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; MS-RTC LM 8) Description Issue: Representation of nested object nodes in activity diagrams. Discussion: It is desirable to be able to represnt nesting of object nodes on activity diagrams to reflect one or more levels of nested properties of the classifier that types the object node. For example, if water is shown as an object node, and it is desired to refer to the temperature of water, then it should be possible to reflect this property on the activity diagram using the notations that are used on ibd's. In particular, one may want to use either a nested rectangle to represent the property, or the dot notation. Proposed update. In the diagram extensions for activity diagrams in Section 11.3.1.4, add a clarifying statement that nested properties of the classifier that types an object node can be represented on activity diagrams either using the nested rectangle notation or the dot notation similar to the use of nesting on ibd's and parametric diagrams. Date: Sun, 05 Jul 2009 08:20:05 -0400 From: "Friedenthal, Sanford" Subject: RE: draft Ballot 1 available for discussion through July 12, 2009 To: "conrad.bock@nist.gov" , Burkhart Roger M Cc: "sysml-rtf@omg.org" Thread-Topic: draft Ballot 1 available for discussion through July 12, 2009 Thread-Index: Acn7ie2TNSJYILgCTO+FF3h04xidVQB2ZiUA Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Conrad I would like to propose the following changes to the activities resolutions for Ballot 2 per the attached and summarized below. 13155- Minor tweek to wording of resolution. Changed .binding connection. to .binding connector. and added figure number. 13197 . Change resolution from closed/no change to defer (perhaps we can do this in a later version) Roger If no objections, please update the proposed resolutions per the attached. Sandy From: Burkhart Roger M [mailto:BurkhartRogerM@JohnDeere.com] Sent: Thursday, July 02, 2009 10:57 PM To: sysml-rtf@omg.org Subject: draft Ballot 1 available for discussion through July 12, 2009 A draft Ballot 2 is available on the SysML RTF wiki at http://www.omg.org/members/sysml-rtf-wiki/doku.php. (Click on the Ballot 2 link.) Ballot 2 will be open for discussion through July 12, 2009. As we discussed during this week's telecon, due to the small number of weeks remaining before our San Antonio OMG meeting deadline, we are starting to compress our schedules so we can get all our voting completed on the resolutions we currently expect to include in SysML 1.2. This discussion period is just over a week, but we still expect the voting to occur over the regular two weeks. Ballot 3, and Ballot 4 if we end up needing it, may end up needing to compress the voting period as well as the discussion period, but any revised schedule will be announced with each ballot. While the discussion period is open, please send comments about any proposed resolutions to the sysml-rtf@omg.org mailing list so everyone can see them and respond with any further comments. If there is significant open discussion about any resolution in the ballot then it can be removed from this ballot for reconsideration in a future ballot. This week's regular Wednesday telecon will also be available to discuss any of the proposed resolutions in this ballot. Thanks to everyone who contributed draft resolutions to this ballot. --Roger 13155_resolved-sf.doc 13197_defer-sf.doc