Guide42.2K views3,832 votes0 replies4,923 following
Specify Service Protocol Paths with UML 2.x Combined Fragments
Use UML 2.x alt, opt, loop, and break fragments to make service protocol branches explicit before implementation.
Loading…
ReadMeFeed / Community knowledge
#sequence-diagram
Real questions. Useful conversations. Find the people who know your stack.
Blog148.9K views2,033 votes0 replies3,866 following
Modeling Complex Control Flow in UML Sequence Diagrams with Combined Fragments
UML 2.5 Combined Fragments (alt, opt, loop, par) model retries, optional flows, and true concurrency in one sequence diagram. Includes a payment-service example, nesting limits, guard portability, and why par needs a companion component diagram.
Blog114.7K views2,948 votes0 replies2,106 following
Using UML Sequence Diagrams to Tame Asynchronous Chaos
UML Sequence Diagrams help map asynchronous API calls and identify edge cases before code is written, preventing integration errors in distributed systems.
asynchronous-programmingdistributed-systemsumlTasadduq Burneyowner34.8K rep · 18 Jan 2026, 03:09 UTC
Guide17K views3,310 votes0 replies2,815 following
Modeling REST API Interactions with UML 2.5 Sequence Diagrams: A Practical Guide
A step-by-step guide to creating UML 2.5 sequence diagrams from OpenAPI specs — covering lifelines, synchronous/asynchronous messages, combined fragments for error handling, and validation checks that keep diagrams aligned with implementation.
openapiBlog64.9K views1,076 votes0 replies3,633 following
Using UML Sequence Diagrams to Verify Inter‑Service Calls in a Distributed Microservice System
Discover how to model and validate OrderService → PaymentService interactions with UML sequence diagrams, check real call order with logs, and understand when async messaging can break the model.
Guide91.6K views1,867 votes1 reply1 comment4,247 following
Choosing Between UML Sequence and Communication Diagrams for Interaction Modeling
Decide whether to use a UML Sequence Diagram for timing details or a Communication Diagram for structural relationships based on your stakeholder's needs.
Editorial question120.5K views2,507 votes1 answer1 comment2,177 following
AI-generatedUML Sequence Diagram Combined Fragment Nesting Limits
Interaction Flow Control The Unified Modeling Language (UML) specification defines combined fragments to manage interaction flow through operators such as alt , opt , loop , and par . These fragments allow developers to model conditional logic and concurrency within a sequence diagram. Execution Semantics in Nested Fragments While the individual operators ha
Editorial question109.3K views1,049 votes1 answer1 comment1,921 following
AI-generatedUML 2.5.1 Combined Fragments: Parallel and Critical Region Nesting
The UML 2.5.1 specification provides the par operator to model concurrent interactions and the critical region operator to ensure atomicity. While these fragments are documented for managing execution flow, ambiguity arises when these operators are nested within one another. The goal is to define a consistent semantic behavior for a critical region placed in
Editorial question102.1K views4,601 votes1 answer1 comment4,409 following
AI-generatedUML `alt` Fragment vs Per-Message Guards for Deterministic Sequence Traces
Goal: generate deterministic executable traces from a UML 2.x sequence diagram for model-based testing, where each simulated run selects exactly one message path. Constraint: an `alt` combined fragment requires exactly one operand guard to evaluate true, but an omitted otherwise case can produce no trace when every guard is false. Per-message guards avoid gr