An Application Event is an Event, denoting a state change at the Application Layer.
Further clarification: Application Functions and other application behaviour may be triggered or interrupted by an Application Event. Also, application behaviour may raise events that trigger other application behaviour. An event is instantaneous; it does not have duration. Events may originate from the environment of the organization (e.g., from an external application), but also internal events may occur generated by, for example, other applications within the organization.
An Application Event may have a time attribute that denotes the moment or moments at which the event happens. For example, this can be used to model time schedules; e.g., an event that triggers a daily batch process.
An Application Event may trigger or be triggered (raised) by an Application Function, Process, or Interaction. An Application Event may access a Data Object and may be composed of other Application Events.
The name of an Application Event should preferably be a verb in the perfect tense.
Category: Application Layer and Behaviour aspect
Examples: Claim received, Request for quotation.
Sources:
- ArchiMate® 3.0 Specification - Chapter 9 Application Layer
- Archi - The Free ArchiMate Modelling Tool - Hint for the model element.
The backlinks below usually do not include the child and sibling items, nor the pages in the breadcrumbs.
#tagcoding tags for goods, services and bads