UML 2.5 Break Fragment Scope Inside Nested Loop Combined Fragments

Direct Answer

A break inside a loop operand terminates the remaining iterations of that loop, not just the current iteration. The break's suppression scope covers all lifelines participating in the enclosing loop combined fragment. For an ignore fragment nested under a break, the break guard is resolved first; a true guard prevents entry into the ignore operand entirely, so the ignore guard is never evaluated.

Confirmed Behavior (UML 2.5 Base Semantics)

• Loop termination: The break exits its nearest enclosing combined fragment. When that fragment is a loop, all subsequent iterations are skipped.
• Lifeline propagation: Messages after the break on any lifeline covered by the loop are suppressed for the remainder of the loop. Lifelines outside the loop's covered set are unaffected.
• Guard resolution order: break guard → if true, skip nested operand (including any ignore); if false, evaluate ignore guard normally.
• No rollback: Messages already executed in the current iteration before the break are not rolled back.

Uncertainty & Tool Conformance

The UML 2.5 specification describes break behavior informally. The exact boundary—current iteration, enclosing loop, or whole interaction—is not normatively precise. Vendors may implement break as loop-continue, fragment-exit, or interaction-abort. Confirm against your tool's UML 2.5 conformance statement.

Verification Steps

1. Model a minimal loop with a break on one lifeline and later messages on other covered lifelines.
2. Run the model in your tool and verify: remaining loop iterations are skipped and post-break messages on all covered lifelines are suppressed.
3. Nest an ignore under the break with a contrasting guard; confirm the ignore guard is not evaluated when the break guard is true.
4. Repeat in a second UML 2.5 tool to detect vendor-specific deviations.

One Diagnostic Detail Needed

Which UML modeling tool (and version) are you targeting? The recommendation changes if the tool documents a vendor-specific break semantics (e.g., loop-continue vs. fragment-exit).