In the context of state and activity diagrams, Event refers to a trigger for a state transition.
However, this work product covers "event" in the more general sense, as occurrences to which the system must respond,
including signals, calls, state changes, or time events.
Also see Artifact: Signal.
Event characteristics can be captured in a spreadsheet, database, requirements management database, or as a table in
the Software Architecture Document.
They can even be captured as classes, stereotyped <<event>>, although this should be treated as a
convenient way of capturing management information about events, and not be confused with data transmitted when the
event occurs. If a call event results in the transmission of data, the data should be represented by the signature of
the called operation. If the event is a signal, its data can be modeled explicitly (see Artifact: Signal).