-
Key: UML14-993
-
Legacy Issue Number: 3281
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
The semantics of the stick arrowhead is described as:
[p 124, notation] Flat flow of control. Each arrow shows the
progression to the next step in sequence. Normally all of the
messages are asynchronous.[p 128, notation] stick arrowhead: flat flow of control
(normally asynchronous).What is a "flat flow of control"? How is it different than an
asynchronous operation or signal? It is ambiguous to say that it
is "normally" asychronous. How does the user tell whether it is
or isn't in any particular case?It is more confusing when compared to the descriptions for
half-stick:[p 124, notation] Asynchronous flow of control. Used instead of
the stick arrowhead to explicitly show an asynchronous
communication between two Objects in a procedural sequence.[p 128] half stick arrowhead: an asynchronous operation invocation
How is a "flat flow of control" different from a "procedural
sequence"?This topics has been very confusing for the agent modelers, who
are using sequence diagrams to model agent protocols. -
Reported: UML 1.2 — Sat, 5 Feb 2000 05:00 GMT
-
Disposition: Resolved — UML 1.3
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 21:37 GMT
UML14 — UML RTF 1.4 Issue: Arrowhead semantics in collaboration unclear
- Key: UML14-993
- OMG Task Force: UML 1.4 RTF