-
Key: UML14-106
-
Legacy Issue Number: 5659
-
Status: closed
-
Source: Texas Department of Human Services ( Srinivas Nedunuri)
-
Summary:
Section 3.90.2.2 says
"In other words when a state prodices an outpout that is input to the
subsequent state, that object flow relationship implies a control
constraint."I take it that this is not the same as isSynch being true? That is isSynch
means that an object in an object flow is rather like a token in a Petri
net. ie once it flows out to the consuming state, its gone from its place.
Is that correct? -
Reported: XMI 1.3 — Fri, 27 Sep 2002 04:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT