Which notation best represents asynchronous message triggers without immediate execution occurrence in UML Sequence Diagrams?

Answer

The standard UML way to show an asynchronous message that does not cause immediate execution is a solid line with an open (stick) arrowhead pointing to the receiver lifeline.

Explanation

According to the UML 2.x Superstructure, an asynchronous message is represented by a line whose arrowhead is not filled. This indicates that the sender does not wait for a response, but it does not specify when the receiver begins processing. The notation itself does not include a symbol for queuing or latency.

To visually convey that the message is held in a buffer before the receiver acts, you can:

• Insert an additional lifeline representing a queue or buffer between sender and receiver, drawing two asynchronous messages (sender→queue, queue→receiver).
• Add a note or a time‑duration constraint near the message to indicate a delay.
• Use a small “queue” symbol (a rectangle with a label) as a passive object on the receiver’s lifeline to show the message is waiting.

These approaches keep the core asynchronous‑message notation unchanged while making the latency explicit.

Verification Steps

1. Open a UML modeling tool (e.g., Enterprise Architect, Visual Paradigm).
2. Create two lifelines and draw a message from the sender to the receiver.
3. Set the message’s arrowhead to “open” (stick).
4. Confirm that the line is solid and the arrowhead is not filled.
5. Optionally add a queue lifeline and repeat the message to see the two‑step representation.