Asynchronous Messaging Notation for Sequendiagrams

[Kevin G. Watson]

Hello, I know this question is going to make me seem incredible sad and lonely!)

However, now that C# has asynchronous language semantics as well as static and dynamic synchronous.

Am I right that whereas a synchronous message is illustrated with a full arrowhead, asynchronous messages with the lower half of the arrow occluded.

Are asynchronous return messages shown with a dotted line but with the upper half of the arrow occluded?

Diagram would help yeah....



SkyDrive sharing nopes



Checking that twitter is cool with ya'd all [smiley=2vrolijk_08.gif] Nopes back to images hack I guess[smiley=2vrolijk_08.gif]

[Eve]

Don't see any mention of that in the UML spec.

Notation
A message is shown as a line from the sender message end to the receiver message end. The line must be such that every line fragment is either horizontal or downwards when traversed from send event to receive event. The send and receive events may both be on the same lifeline. The form of the line or arrowhead reflects properties of the message:

• Asynchronous Messages have an open arrow head.
• Synchronous Messages typically represent operation calls and are shown with a filled arrow head.
• The reply message from a method has a dashed line.
• Object creation Message has a dashed line with an open arrow.
• Object deletion Message should end in a DestructionOccurrenceSpecification.
• Lost Messages are described as a small black circle at the arrow end of the Message.
• Found Messages are described as a small black circle at the starting end of the Message.
• On Communication Diagrams, the Messages are decorated by a small arrow in the direction of the Message close to the Message name and sequence number along the line between the lifelines (See Table 14.4 and Figure 14.27).