Issue 18194: Allow a notation to allow for a default assignment of a decision to the owner of the activity (uml25-ftf) Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org) Nature: Uncategorized Issue Severity: Summary: Allow a notation to allow for a default assignment of a decision to the owner of the activity (this is probably the normal circumstances). This is both a UML / SysML issue Resolution: Revised Text: Actions taken: October 22, 2012: received issue Discussion: End of Annotations:===== s is issue # 18194 Date: Mon, 22 Oct 2012 17:37:21 +0000 From: "Chonoles, Michael J" Subject: RE: EXTERNAL: Re: Several issues on Decision nodes in Activity diagrams X-Originating-IP: [158.186.156.94] To: Juergen Boldt Thread-Topic: EXTERNAL: Re: Several issues on Decision nodes in Activity diagrams Thread-Index: AQHNp7PUrvNsc9z9X0GkevPHKycxw5fFqDKg Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-22_02:2012-10-22,2012-10-22,1970-01-01 signatures=0 As mentioned below 1 & 3 are UML, 2 & 3 are SysML At 02:00 AM 4/23/2012, you wrote: Decision nodes in activity diagrams appear to be a sort of activity node, and as such can be contained in partitions (swimlanes). However, in some circumstances, it is not practical to delineate partitions. However, the alternative approach given in the spec, is only defined for activities. 3) Allow a notation to allow for a default assignment of a decision to the owner of the activity (this is probably the normal circumstances). This is both a UML / SysML issue Depending on the response/discussion of these issues, we may need to open addition issues on forks/merges etc. Michael Chonoles LMCO