A business event represents a semantically defined set of states, relevant for the business domain. Event serves as informal description and is used in the scope (context) of entire model of the business domain.
Business events per se cannot be manupulated by computers as they are sheer abstractions and in order to manipulate them, an application system must create an event object - an electronic signal or a message of the event. A message consisting of an event object is called notification.
In other words, event is a happening, while notification is a report of the happening.
Events are used in order to synchronize business processes with their environment, that is to capture changes of interest for the course of business processes. The changes can be internal as well as external to the company and to the business process in particular. This type of synchronization helps to keep business more responsive to all changes affecting it directly or indirectly, or in other words it adds to business agility.
A call from a client would be a good example of a business event which triggers a certain business process or a group of processes into action, say, order registration or client check.
This particular event represents not just one business state, but a whole set of business states with the common part that says that there is a call received from a client, whereas all other parts of these states could be different.
Other examples are address change, stock trade, shipment delivery, bank transaction etc.
EXAMPLE: a product leaving a warehouse is an ordinary event, unless the price of the product exceeds $10000. If the price of the product is more then that amount, this event becomes notable and may invoke a whole range of actions, unlike an ordinary event.
happening