Re-usable Guards for State Transitions

Chandon,

Lacking insight into your organization's model standards and conventions (yes, I think this case should be documented there), I'll suggest you consider modeling a Constraint (std, not a constraint block) using OCL and linking your recurring state machine Guards to the Constraint. Hopefully your tooling supports model simulation when using OCL for this purpose.

Regards,
Geoff

Hi Geoff, thanks for the suggestion.  I tried this and I am able to point a transition to a constraint (owned by the state machine's classifier), but that creates a copy of the original constraint under the transition. 

If i am interpreting UML spec correctly (v2.5.1, section 14.2.2), it appears that a guard (as constraint) can be owned by up to one transition, so the language may not support the exact feature I'm looking for.

Respectfully,

Chandan

I forgot to mention - I can drag/drop a constraint onto a transition and that will create a constraint on the transition, but that constraint is not set as the guard.

I forgot to mention - I can drag/drop a constraint onto a transition and that will create a constraint on the transition, but that constraint is not set as the guard.