The document discusses business event modeling and event thinking as an alternative to traditional process modeling. It focuses on modeling non-process elements like external events, states, decisions, and activities, rather than pre-planned process sequences. Examples of business events include customer orders and payments as well as supplier deliveries and invoices. The document also distinguishes between simple event processing, which involves extracting, transforming and loading data, and complex event processing, which can detect organized events directed through decisions without a predefined process.

1. Chapter 5
Part1
Business Events Modeling
1

2. 2
It is a shift from a focus on the Internal Processes to a focus on the External
Non-process elements.
 The process viewpoint depicts a preconceived map of activities with a set
of pre-planned sequences. The process model is composed of activities,
sequences, gateways, and other elements.
 The non-process viewpoint focuses on distribution of states, random
events, decisions, and activities.
Event thinking

3. 3
simple process fragment with a gateway
Event thinking
The process viewpoint depicts a preconceived map of activities with a set of pre-planned sequences. The
process model is composed of activities, sequences, gateways, and other elements.

4. 4
Event thinking
Internal processes
controlled by decisions
from the external cloud
• The non-process viewpoint
focuses on distribution of states,
random events, decisions, and
activities.

5. 5
The event is a natural focus of a use case.
 Customer events include Orders, Receipts, Payments, and Returns.
 Supplier events include Deliveries and Invoices
Event thinking

6. 6
There are two new distinctions:
 It is possible for activities and responses to be expressed as a
collection of organized events, often directed through decisions,
but not necessarily as a process. This is called complex event
detection.
 It is also possible to have a disorganized process with no event
sequence. This is called an ad hoc process.
Event thinking

7. 7
Types of Events

8. 8
Types of Events
Event Trigger Source Use Case Response Destination
User clicks on
item in online
catalogue
Inventory
request
User /
customer
Event Table
Display
inventory
quantity
Web page
inventory
report
User /
customer
Time to produce
daily sales report
“ end of
the day”
system produce daily
sales report
Sales
report
manager
Reorder
point is
reached
Inv falls below
reorder point Reorder
Inventory
system
Purchase
report
Supplier
purchasing
manager

9. 9
Event Processing

10. 10
Event Processing
Data Processing Domain

11. 11
Event Processing
Data Processing Domain

12. 12
Simple Event Processing (SEP)

13. 13
Complex Event Processing (CEP)

14. 14
Simple Event Processing (SEP)
Extract, transform, and load
(ETL) is the process data-
driven organizations use to
gather data from multiple
sources and then bring it
together to support
discovery, reporting,
analysis, and decision-
making.

15. 15
Complex Event Processing (CEP)

16. 16
Sample Architecture

17. 17
Complex Event Processing (CEP)

18. 18

19. 19

20. 20

21. 21
Thank You