Process Modeling

Part II
Samuel Ady Sanjaya
Review Process Modeling Part I
• Branching and Merging
• Exclussive Decissions
• Parallel Execution
• Inclusive Decissions
• Rework or Repetition
• Process Model Reuse
 01
Rework and
Repetition
Parallel Repetition
• The loop activity allows us to capture sequential repetition
• Sometimes though, we may need to execute multiple instances of the same
activity at the same time
Parallel Repetition
Problems
• Larger Suppliers,
larger model
• Need to revised
model if the number
of supplier changed
Parallel Repetition
Uncontrolled Repetition
• Need to model that one or more activities can be repeated a number of times
without a specific order until a condition is met
• The customer needs to inquire about the progress of its order
• The customer may attempt to cancel the order or update the personal details
• To model a set of uncontrolled activities, we can use an ad hoc sub-process
Uncontrolled Repetition
 01

Handling Event
Message Events
• Start event: mark with an empty envelope to specify that new process
instances are triggered by the receipt of a message
• End event: mark with an envelope to capture the interaction between our
process and another party
Message Events
Temporal Events
• Besides the message event, there are other triggers that can be specified for
a start event
• This event type indicates that process instances start upon the occurrence of
a specific temporal event
• A timer event may also be used as an intermediate event to capture that a
temporal interval needs to elapse before the process instance can proceed
• To indicate a timer event, we mark the event symbol with a watch inside the
circle
Temporal Events
Racing Events
• A typical scenario encountered when modeling processes with events is the
one where two external events race against one another
• The first of the two events that occurs determines the continuation of the
process
• For example, after an insurance quote has been sent to a client, the client
may reply either with an acceptance message, in which case an insurance
contract will be made, or with a rejection, in which case the quote will be
discarded
Racing Events
• This race between external events is captured by means of the event-based
exclusive (XOR) split
• An event-based exclusive split is represented by a gateway marked with an
empty pentagon enclosed in a double-line circle
 01
Handling
Exceptions
Handling Exceptions
• Exceptions are events that deviate a process from its normal course
• Identify all possible causes of problems in a given process
• Exceptions include business faults such as an out-of-stock or discontinued
product and technology faults like a database crash, a network outage or a
program logic violation
• They cause the interruption or abortion of the running process
Process Abortion
• The simplest way of handling an exception is to abort the running process
and signal an abnormal process termination
Process Abortion
Internal Exeptions
• Instead of aborting the whole process, we can handle an exception by
interrupting the specific activity that has caused the exception
• start a recovery procedure to bring the process back to a consistent state and
continue its execution, and if this is not possible, only then, abort the
process altogether
Internal Exeptions
External Exeptions
• An exception may also be caused by an external event occurring during an
activity
• Example: out of stock, cancellation and new order on the same time
Activity Timeout
• Another type of exception is the interruption of an activity which is taking
too long to complete
• we can attach an intermediate timer event to the boundary of the activity:
the timer is activated when the enclosing activity starts
Event Sub-process
• An alternative notation to boundary events is the event sub-process
• An event subprocess is started by the event, which would otherwise be
attached to the boundary of an activity, and encloses the procedure that
would be triggered by the boundary event
• Event sub-processes do not need to refer to a specific activity, but can model
events that occur during the execution of the whole process
Event Sub-process
Activity Compensation
• As part of a recovery procedure, we may need to undo one or more steps
that have already been completed, due to an exception that occurred in the
enclosing sub-process
• The results of these steps, and possibly their side effects, may no longer be
desired and for this reason they should be reversed
• His operation is called compensation and tries to restore the process to a
business state close to the one before starting the sub-process that was
interrupted.
Activity Compensation
Tugas
• Carilah salah satu studi kasus untuk dimodelkan dalam BPMN, antar
kelompok tidak perlu unik yang penting tidak contek2an.
• Pengantar
• Kelompok 2 orang
• Deadline 22 April 2021
• Tools: bpmn.io
• Wajib:
• Gateway (Jenisnya minimal 2: AND, OR, XOR)
• Handling Events
• Handling Exceptions
Info UTS
• Waktu : Jumat 30 April 2021, Jam 8.30 – 9.30
• Jenis : Individual, teori, pilihan ganda, live on cam, open book
• Materi : Week 1 – Week 7
 Thanks!
CREDITS: This presentation template was created by Slidesgo,
including icons by Flaticon, infographics & images by Freepik