Issue 8471: Decision node (uml2-rtf)
Source:  (, )
Nature: Revision
Severity: Minor
Summary: Decision node should be able to take decision based on input separate from the flow being routed
Resolution: Resolution:
This issue is already resolved in UML 2.2 (see Issue 10815).
Revised Text:
None
Disposition:	Duplicate

Revised Text: 
Actions taken:
March 6, 2005: received issue
April 26, 2010: closed issue
April 26, 2010: closed issue
Discussion: 
Disposition:	Deferred to UML 2.4 RTF
End of Annotations:=====

m: webmaster@omg.org 
Date: 06 Mar 2005 10:07:58 -0500 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Antonino Sabetta
Company: 
mailFrom: as@sabetta.com
Notification: No
Specification: UML 2 Superstructure
Section: Activities
FormalNumber: ptc/04-10-02
Version: 
RevisionDate: 
Page: 
Nature: Revision
Severity: Minor
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Description
Decision node should be able to take decision based on input separate from the flow being routed. 

Subject: RE: ,ac,,av, AA WG internal discussion for ballot 10
Date: Tue, 13 Sep 2005 06:09:29 +0200
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ,ac,,av, AA WG internal discussion for ballot 10
Thread-Index: AcWz0OB4uPs/OePBQMGZUYR2qItoawDo2LLg
From: "Tim Weilkiens" <Tim.Weilkiens@oose.de>
To: <conrad.bock@nist.gov>, "Ed Seidewitz" <ed-s@enterprisecomponent.com>,
   "Jim Amsden" <jamsden@us.ibm.com>,
   "Sebastien Gerard" <sebastien.gerard@cea.fr>,
   "Guus Ramackers" <guus.ramackers@oracle.com>
Cc: "uml2rtf" <uml2-rtf@omg.org>
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id j8D4TDhh019764


Conrad,


do you know the requirement for this issue? 


I think it isn't easy to introduce that feature. On the first sketch I
think of:


- Implicit synchronisation at decision node?
- Notation: How to differ the notation from the notational shortcut to
draw decision and merge with one node?
- Decision inout behavior needs an input pin?


Just a few of my 


> -----Original Message-----
> From: Conrad Bock [mailto:conrad.bock@nist.gov] 
> Sent: Wednesday, September 07, 2005 7:20 PM
> To: Tim Weilkiens; Ed Seidewitz; Jim Amsden; Sebastien 
> Gerard; Guus Ramackers
> Cc: uml2rtf
> Subject: RE: ,ac,,av, AA WG internal discussion for ballot 10
> 
> Tim,
> 
> Thanks for the proposals.  Regarding 8471 (Decision node), this is a
> request for an additional kind of incoming ede to decisions 
> that is used
> to decide where to route tokens arriving at the other incoming edge.
> 
> Conrad
>     

Subject: Proposed issue resolutions, set 1: Activities -- No change and duplicates
Date: Fri, 30 Jan 2009 18:00:16 -0500
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed issue resolutions, set 1: Activities -- No change and duplicates
thread-index: AcmDLoPo5ZLYjIHbRwaX3F8d2ZwvGA==
From: "Ed Seidewitz" <ed-s@modeldriven.com>
To: <uml2-rtf@omg.org>


Attached is a Word document with draft resolutions for Activities issues that I propose to close with no change or that I have identified as duplicates of other issues.

 

-- Ed



 UML 2.3 Resolutions 090130 Seidewitz 1.doc 

OMG Issue No:  8471
Title:	Decision Node 
Source:
(Antonino Sabetta, as@sabetta.com)
Summary:
Decision node should be able to take decision based on input separate from the flow being routed
Resolution:
This issue is already resolved in UML 2.2 (see Issue 10815).
Revised Text:
None
Disposition:	Duplicate