volume_mute
Sequence Diagram Notation Elements
publish date: 2026/06/08 06:26:26.504431 UTC
volume_muteMatch each sequence diagram element to its correct meaning.
To complete the line match
- Click on an item in the first group
- Click on the match in the second group
To delete a match, double click on a line
Element
Dotted vertical line below an object/actor
Thin rectangle on a dotted lifeline
Solid horizontal arrow between lifelines
Dashed horizontal arrow between lifelines
[condition] on an arrow or inside an alt box
Meaning
A guard condition — the interaction only occurs if the condition is true
The lifeline — shows the existence of that object/actor over time; you read the sequence top to bottom
An activation box — the period during which that object instance is involved in the computation
A synchronous call or message sent from one object to another
A return value or response message
Correct Answer
(1) Dotted vertical line below an object/actor,The lifeline — shows the existence of that object/actor over time; you read the sequence top to bottom
(2) Thin rectangle on a dotted lifeline,An activation box — the period during which that object instance is involved in the computation
(3) Solid horizontal arrow between lifelines,A synchronous call or message sent from one object to another
(4) Dashed horizontal arrow between lifelines,A return value or response message
(5) [condition] on an arrow or inside an alt box,A guard condition — the interaction only occurs if the condition is true
Explanation
Sequence diagram notation: Dotted vertical lines = lifelines (objects/actors exist over time; read top to bottom); Thin rectangles on lifelines = activation boxes (object is actively involved); Solid arrows = messages/calls sent between objects; Dashed arrows = return values or responses; [condition] = guards specifying when an interaction occurs.
| Symbol | Notation Title | Meaning & Description |
|---|---|---|
| Dotted vertical lines | Represents lifelines, indicating that objects or actors exist over a period of time. These lines are read sequentially from top to bottom. | |
| Thin rectangles on lifelines | Represents activation boxes, which visually demonstrate the period during which an object is actively involved in an operation or processing a request. | |
| Solid arrows | Represents messages or calls sent synchronously between distinct lifelines/objects. | |
| Dashed arrows | Represents return values or responses sent back to the requester from a previous message activation. | |
| [condition] | Guard conditions | Acts as guards, specifying evaluation criteria or conditional logic that must be true for that specific interaction or message exchange to take place. |
Reference
Software Engineering, Ian Sommerville, 9th edition
