Legacy Issue Number: 3284
Source: NIST ( Conrad Bock)
Flow relationship has the incorrect semantics specified for it:
[p 2-33] It usually connects an activity to or from an object
flow state, or two object flow states. It can also connect from
a fork or to a branch.
Specifies a Flow relationship, source and target of which
represent the same instance at different points in time, but
each with potentially different values, state instance, and
roles. A Become Dependency from A to B means that instance A
becomes B with possibly new values, state instance, and roles at
a different moment in time/space.
Specifies a Flow relationship, the source and target of which
are different instances, but each with the same values, state
instance, and roles (but a distinct identity). A Copy Dependency
from A to B means that B is an exact copy of A. Future changes
in A are not necessarily reflected in B.
Reported: UML 1.2 — Sat, 5 Feb 2000 05:00 GMT
Disposition: Resolved — UML 1.3
No Data Available
Updated: Fri, 6 Mar 2015 21:37 GMT