When multiple triggers are defined for a Transition, they are logically disjunctive, that is, if any of them are enabled, the Transition will be triggered. Source Unified Modeling Language 2.5.1
A Transition may own a set of Triggers, each of which specifies an Event whose occurrence, when dispatched, may trigger traversal of the Transition. A Transition trigger is said to be enabled if the dispatched Event occurrence matches its Event type. Source Unified Modeling Language 2.5.1
Transition::guard : Constraint [0..1] ... If the guard is true at that time, the Transition may be enabled, otherwise, it is disabled. Guards should be pure expressions without side effects. Guard expressions with side effects are ill formed. Source Unified Modeling Language 2.5.1
Transition::guard : Constraint [0..1] ... A guard is a Constraint that provides a fine-grained control over the firing of the Transition. The guard is evaluated when an Event occurrence is dispatched by the StateMachine. ... Source Unified Modeling Language 2.5.1
StateMachine execution is represented by transitions from one active state configuration to another in response to Event occurrences that match the Triggers of the StateMachine. Source Unified Modeling Language 2.5.1
A SignalEvent represents the receipt of an asynchronous Signal instance. Source Unified Modeling Language 2.5.1
A CallEvent models the receipt by an object of a message invoking a call of an Operation. Source Unified Modeling Language 2.5.1
A trigger for an AnyReceiveEvent is triggered by the receipt of any message that is not explicitly handled by any related trigger. Source Unified Modeling Language 2.5.1
A TimeEvent is an Event that occurs at a specific point in time. Source Unified Modeling Language 2.5.1
A ChangeEvent models a change in the system configuration that makes a condition true. Source Unified Modeling Language 2.5.1
An Event is the specification of some occurrence that may potentially trigger effects by an object. Source Unified Modeling Language 2.5.1
A MessageEvent specifies the receipt by an object of either an Operation call or a Signal instance. Source Unified Modeling Language 2.5.1
The “hybridSUV” lifeline represents another interaction which further elaborates what happens inside the “hybridSUV” when the vehicle is started. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.9 shows an interaction that includes events and messages communicated between the driver and vehicle during the starting of the vehicle. Source OMG Systems Modeling Language (SysML) 1.6
trigger_with_ports: If a Trigger specifies one or more ports, the event of the Trigger must be a MessageEvent. Source Unified Modeling Language 2.5.1
A Trigger may be qualified by the Port on which the Event occurred. Source Unified Modeling Language 2.5.1
A Trigger specifies a specific point at which an Event occurrence may trigger an effect in a Behavior. Source Unified Modeling Language 2.5.1
The context object for an AcceptEventAction is the context object of the Behavior execution within which the AcceptEventAction is executing (which may be the Behavior execution itself ...) Source Unified Modeling Language 2.5.1
AcceptEventAction is an Action with Triggers for one or more Events. When an AcceptEventAction is executed, it waits for an Event occurrence to be dispatched from the event pool of the context object for its execution that matches one of its Triggers. Source Unified Modeling Language 2.5.1
However, in addition, an AcceptEventAction with no incoming edges remains enabled after it accepts an Event occurrence. Source Unified Modeling Language 2.5.1
