A swimlane diagram traces one user action across a product, assigning each backend service to a lane and plotting calls left to right in execution order. It exposes the hidden service chain behind a gesture and identifies the step that keeps the user waiting. section 8.4
Build a useful swimlane view by:
- Choose six to eight representative actions whose API paths differ in kind, including read-only, write-heavy, scheduled, and admin-only flows. section 8.4
- Use API routes and feature groups to identify participating services, then place services in lanes and calls as ordered events. section 8.4
- Annotate each flow with its lane count, event count, and the lane responsible for the user's wait. section 8.4
- Escalate from a surface map to swimlanes, then inspect a single endpoint with a UML sequence diagram when deeper detail is warranted. section 8.6
Tracing an online shop
Map browsing the catalog, placing an order, a nightly abandoned-cart reminder, and an administrator issuing a refund. Each action activates a different service set, making read, write, scheduled, and administrative workflows comparable. section 8.4
