EditorialDiagramSoftware Engineering
Editorial Sequence Diagram Designer — No Shadows, No Mermaid Slop
Make a checkout trace legible with ordered messages, dashed lifelines and correctly encoded returns. Eight participants are split into authorization and fulfillment traces, with an explicit handoff between them.
Take it with you
Free PNG includes an EditorialDiagram watermark.
Layout Grammar & Anti-Patterns
Four rules for this diagram
- 01
Place actor boxes above dashed vertical lifelines. Time runs downward, with horizontal messages and at least 24px between message levels.
- 02
Sync calls use filled arrowheads. Returns use dashed strokes with filled heads; fire-and-forget messages use dashed strokes with open heads.
- 03
Limit each trace panel to five lifelines and the complete example to twelve messages. Split a larger interaction into named overview and detail traces.
- 04
Bound activation bars to the control interval. When logic branches, use a labelled ALT, OPT or LOOP frame instead of floating if/else arrows.
Three mistakes to avoid
- An upward message reverses time and makes a return look like a new request.
- An open return marker or a filled async marker changes the protocol meaning.
- Deeply nested fragments and labels across unrelated lifelines obscure which actors participate in the branch.
Engineer vs. Executive
The two renders use the same illustrative source. Executive mode groups detail deliberately; read the captions before using an overview for a technical review.
Eight actor identities and twelve messages are retained in two four-lifeline trace panels.
Four business participants summarize successful checkout instead of exposing each protocol exchange.
When to use another diagram instead
System Architecture Diagram
Use architecture when the reader needs service dependencies without the temporal trace.
Swimlane Diagram
Use swimlanes for team-owned activities and cross-functional handoffs rather than protocol messages.
Flowchart
Use a flowchart when branching decisions matter but message exchanges between named actors do not.
Questions about this diagram
Why is the eight-participant checkout example split into two traces?
Eight actors exceed the reference budget of five lifelines per trace. The example keeps four authorization actors beside four fulfillment actors and labels the gateway-to-orders handoff. All eight participant identities remain visible, while each local trace keeps readable message spacing.
How can I distinguish a return from an asynchronous notification?
Both can use a dashed stroke, so the arrowhead matters. A return to a synchronous call keeps a filled arrowhead. The Orders-to-Events notification uses an open head because it is a one-way event. Neither line style is a substitute for ordering the messages down the time axis.
Does Executive mode retain every token and inventory message?
No. It groups the trace into four business participants: Customer, Access, Fulfillment and Payment. That view communicates the successful checkout narrative. Use Engineer mode for token verification, stock reservation, payment replies and the accepted-order event.
Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.
Cached examples are free. Starter Pack is $9.9 once; Pro Pass is $8.9 per month. Every generation costs 10 credits, including one automatic geometry repair. Pricing