Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content UML Event types for triggering Transitions SysMLv1: CAUTION: Only a Signal can be used for a SendSignalAction or MessageEvent trigger of an AcceptEventAction, not a Block or ValueType, even if they are valid types for a SysML FlowProperty! But you can "wrap" a Block or ValueType in a Signal. Source Unified Modeling Language 2.5.1 Copyright information About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes Snippet kind INFO UML keywords Event MessageEvent object Operation Signal CallEvent SignalEvent AnyReceiveEvent Previous snippet Full quote A MessageEvent specifies the receipt by an object of either an Operation call or a Signal instance. Next snippet Related snippets Related snippets (backlinks) An Event is the specification of some occurrence that may potentially trigger effects by an object. A ChangeEvent models a change in the system configuration that makes a condition true. A TimeEvent is an Event that occurs at a specific point in time. A trigger for an AnyReceiveEvent is triggered by the receipt of any message that is not explicitly handled by any related trigger. A CallEvent models the receipt by an object of a message invoking a call of an Operation. A SignalEvent represents the receipt of an asynchronous Signal instance. Visit also Visit also (backlinks) Flags
