Sequence diagram
An interaction model where actors sit across the top, time moves downward, and horizontal messages explain a scenario.
Documenting API calls, protocols, authentication, or request/response behavior.
The goal is a static component inventory.
- Time always moves downward.
- Calls are solid and returns dashed.
- Use ALT, OPT, or LOOP frames for branches.
- Limit the default view to five actors and twelve messages.
- Who calls whom?
- In what order?
- What happens on failure?
id: sequence family: software reading_task: Follow messages between actors over time. grammar: - actors - lifelines - messages - activation_bars - fragments checks: - time_always_moves_downward - calls_are_solid_and_returns_dashed - use_alt_opt_or_loop_frames_for_branches - limit_the_default_view_to_five_actors_and_twelve_messages