CSS 496 Business Process Re-engineering for BS(CS)

Department of Computer Science 1

CSS 496 Business Process Re-

engineering for BS(CS)

Chapter 4: Business Process Modeling Notations

Khurram [email protected]

Based on Petia, Marlon, Aalst and Weske Lectures


Business Process Modeling Notation Business Process Modeling Notation,

developed under the coordination of Object Management Group.

Benefits Combines best practices of existing approaches Readily undersandable by all business users Users can use it without extensive training

Department of Computer Science

BPMN Elements

3

Poo

lFlow Objects

Events

Activities Place Order

Gateways

Connecting Objects

Sequence Flow

Message Flow

Association

Swimlanes

Lane

Data Object

Group

Artefacts

Annotation

Fig 4.78. Business Process Modeling Notation: categories of elements

M. W

eske

: Bus

ine

ss P

roce

ss M

anag

em

ent,

© S

prin

ger

-Ver

lag

Ber

lin H

eid

elbe

rg 2

007


More Elements

4

Data-based XOR ORAND

ComplexEvent-based XOR

Fig 4.84. Gateway types in the BPMN, Object Management Group (2006) M. W

esk

e: B

usi

ness

Pro

cess

Man

age

men

t,

© S

prin

ger

-Ve

rlag

Ber

lin H

eid

elb

erg

20

07

Start

Intermediate

End

Termination

Message Timer Rule Error Link Multiple

Fig 4.80. Event types in the BPMN, Object Management Group (2006)

M. W

eske

: Bu

sin

ess

Pro

cess

Man

agem

ent,

© S

prin

ger-

Ve

rlag

Ber

lin H

eide

lber

g 20

07Data-based XOR ORAND



esk

e: B

usin

ess

Pro

cess

Man

age

men

t, ©

Spr

inge

r-V

erla

g B

erlin

He

idel

berg

20

07

Events

OR

Data-based XOR ORAND



esk

e: B

usi

ness

Pro

cess

Man

age

men

t,

© S

prin

ger

-Ve

rlag

Ber

lin H

eid

elb

erg

20

07

AND

XOR

Gateways


Principles

Process model starts with an event Whenever the conditions of a gateway are

designed so that always all outgoing edges are activated, the gateway should be marked with the + symbol to indicate the and split semantics of the gateway.

Continue… as patterns


Example 1

6

Analyze Order

Check Stock

Ship Products

Purchase Raw

Material

Make Production

Plan

Manufacture Products

Send billReceive payment

In stock

Not in stockOrder

Make products

Fig 4.77. Business process diagram expressed in BPMN

M. W

eske

: Bus

ines

s P

roce

ss M

ana

gem

ent,

© S

prin

ger-

Ver

lag

Ber

lin H

eide

lbe

rg 2

007


Example 2

7

Buy

er Place Order

Receive Invoice

Receive Products

Settle Invoice

Analyze Market

Fig 4.90. Private business process

M. W

eske

: Bu

sin

ess

Pro

cess

Ma

nage

men

t, ©

Sp

ringe

r-V

erla

g B

erli

n H

eide

lber

g 2

007


Possible States

not started closed

init ready running terminated

initialize enable begin terminate

skip

skipped

Fig 4.1. State transition diagram for activity instances

M. W

eske

: Bus

ines

s P

roce

ss M

anag

emen

t, ©

Spr

inge

r-V

erla

g B

erlin

Hei

delb

erg

2007


Patterns (Sequence and loop pattern)

A B

a

enable begin terminate enable begin terminate

b

Even ordering induced by sequence

Fig 4.2. Sequence pattern, with event diagram of process instance

M. W

eske

: Bus

ine

ss P

roce

ss M

anag

emen

t, ©

Spr

inge

r-V

erla

g B

erlin

Hei

delb

erg

200

7A B

a1 b1 a2 b2 a3 b3

Fig 4.3. Sequence pattern as part of a loop and event diagram showing three loop iterations

M. W

eske

: Bu

sin

ess

Pro

cess

Man

agem

ent,

© S

prin

ger-

Ve

rlag

Ber

lin H

eid

elbe

rg 2

007


Patterns (AND Split)

A

B

C terminate(a)

enable(b)

Even ordering induced by and split

enable(c)

Fig 4.4. And split pattern

M. W

eske

: Bus

ine

ss P

roce

ss M

anag

emen

t, ©

Spr

ing

er-V

erla

g B

erlin

Hei

delb

erg

200

7

B

C

D

terminate(c)

enable(d)

Even ordering induced by and join

terminate(b)

Fig 4.5. And join pattern

M. W

eske

: Bus

ines

s P

roce

ss M

anag

emen

t, ©

Spr

inge

r-V

erla

g B

erlin

Hei

del

berg

200

7


Patterns (AND Split)

Update Inventory

Get Order

Send Invoice

Ship Goods

Fig 4.87. Example of an and split and and join gateway

M. W

eske

: Bu

sin

ess

Pro

cess

Ma

nage

me

nt,

© S

prin

ger-

Ve

rlag

Be

rlin

Hei

delb

erg

200

7


Patterns (XOR Split and Join)

A

B

C

terminate(a)

enable(b)

enable(c)

terminate(a)

Option 1: Enable b

Option 2: Enable c

Fig 4.6. Xor split pattern

M. W

eske

: Bus

ine

ss P

roce

ss M

anag

emen

t, ©

Spr

ing

er-V

erla

g B

erlin

Hei

delb

erg

200

7

B

C

D

enable(d)

terminate(b)

terminate(c)

enable(d)

Option 2: c terminates

Option 1: b terminates

Fig 4.7. Xor join pattern

M. W

eske

: Bu

sin

ess

Pro

cess

Man

agem

ent,

© S

prin

ger-

Ve

rlag

Be

rlin

Hei

delb

erg

200

7


Patterns (XOR Split and Join)

Grant Credit

Evaluate Credit Risk

Reject Credit Request

Advanced Credit Check

Fig 4.88. Sample business process with sequence flow and default sequence flow

M. W

eske

: Bu

sin

ess

Pro

cess

Ma

nage

me

nt,

© S

prin

ger-

Ve

rlag

Be

rlin

Hei

delb

erg

200

7


Patterns (OR Split)

A

B

C

terminate(a)

enable(b)

enable(c)

terminate(a)

Option 1: Enable b

Option 2: Enable c

terminate(a)

enable(b)

enable(c)

Option 3: Enable b and c

Fig 4.8. Or split pattern

M. W

eske

: Bu

sin

ess

Pro

cess

Man

age

men

t, ©

Sp

ringe

r-V

erla

g B

erlin

Hei

delb

erg

200

7


Patterns (OR Join)

B

C

D

enable(d)

terminate(b)

terminate(c)

enable(d)

Option 2: c terminates

Option 1: b terminates

terminate(c)

enable(d)

Option 3: b and c terminate

terminate(b)

Fig 4.9. Or join pattern

M. W

eske

: Bus

ine

ss P

roce

ss M

anag

emen

t, ©

Spr

ing

er-V

erla

g B

erlin

Hei

delb

erg

200

7


Book Flight

Plan Trip

Book Rental Car

Book Hotel

Fig 4.86. Example of an inclusive or gateway

M. W

eske

: B

usin

ess

Pro

cess

Man

age

me

nt,

© S

prin

ger

-Ver

lag

Ber

lin H

eid

elbe

rg 2

007

Example (OR Join)


Patterns (Multiple Merge)

B

C

MM D

enable(d1)

terminate(b)

terminate(c)

enable(d2)

When c terminates

When b terminates

Fig 4.10. Multi-merge pattern

M. W

eske

: Bus

ines

s P

roce

ss M

ana

gem

ent,

© S

prin

ger-

Ver

lag

Ber

lin H

eide

lbe

rg 2

007


Interacting Processes Process involving multiple organizational

entities can interact with each other BPMN is not restricted to single organization

processes Ready to express interacting processes of multiple

organizations Swimlanes are used to assign processes/parts

to organizational entities Pools represent specific process participants

business entity role like supplier and customer


Pools Pools represent business process

participants. They are used to partition a set of activities. Can be a business entity or a business

role.

Sequence flows cannot cross the boundaries of a Pool.

Interaction between Pools are captured through Message Flow (dashed lines with an arrow)

Pool


Interacting Processes

Man

ufa

ctur

erS

uppl

ier

Receive Order

Send Invoice

Send Material

Receive Payment

Fig 4.89. Business processes interacting by message flow

M. W

eske

: Bus

ine

ss P

roce

ss M

ana

gem

ent,

© S

prin

ger

-Ver

lag

Ber

lin H

eide

lber

g 2

007

Sequence flow is allowed only between nodes in a single pool Communication occurs through message

flows


Categories of business processes BPMN support three categories of

processes Private Business Processes Public Business Processes Global Business Processes


Private Business Processes Contains only activities that are enacted

within a company All activities that contribute to process are

represented

Buy

er Place Order

Receive Invoice

Receive Products

Settle Invoice

Analyze Market

Fig 4.90. Private business process

M. W

eske

: Bu

sine

ss P

roce

ss M

ana

gem

ent,

© S

prin

ger-

Ve

rlag

Ber

lin H

eid

elb

erg

2007


Public Business Processes Represent only activities that communicate

with other business processes Externally visible behavior of processes

Buy

er Place Order

Receive Invoice

Receive Products

Settle Invoice

Res

elle

r

Fig 4.91. Public business process of buyer and corresponding abstract business process of reseller

M. W

eske

: Bus

ines

s P

roce

ss M

anag

emen

t, ©

Spr

inge

r-V

erla

g B

erlin

Hei

delb

erg

2007


Global Business Processes Global view on internals of all other parties

Buy

er Place Order

Receive Invoice

Receive Products

Settle Invoice

Res

elle

r

Receive Order

Send Invoice

Ship Products

Receive Payment

Fig 4.92. Collaborative business process, representing the combined public business processes

M. W

eske

: Bu

sin

ess

Pro

cess

Man

age

men

t, ©

Sp

ringe

r-V

erla

g B

erlin

Hei

del

berg

200

7


Sub-processes

A task in a process can be decomposed into a “sub-process”.

Use this feature to: Break down large models into smaller ones,

making them easier to understand and to explain


Sub-processes



Get Credit data

Assess risk

Send evaluation

Fig 4.81. Collapsed and expanded subprocess M. W

eske

: Bu

sin

ess

Pro

cess

Man

agem

ent

, ©

Sp

ringe

r-V

erla

g B

erli

n H

eid

elb

erg

200

7


Sub-processes: example

Check Purchase Order

OK Payment

...

...

Order Handling Process

Payment Process

Issue Invoice to Customer

...

Receive Payment Notice from Bank

Confirm Payment to Customer


Example: Publishing Article


Example P

C C

ha

ir

Publish CFP

Assign reviewers

Collect submissions

Collect reviews

Send notification

Collect final

versions

Prepare Proceedings

Re

vie

we

rA

uth

or Read CFP

Write paperSubmit paper

Receive notification

Prepare final version

Send final version

Rejected

Accepted

Prepare reviews

Get review information

Submit reviews

Fig 4.79. Business process diagram of a scientific conference review process

M. W

eske

: Bus

ines

s P

roce

ss M

anag

emen

t, ©

Spr

inge

r-V

erla

g B

erlin

Hei

delb

erg

200

7


Assignment 1

30


When a claim is received, it is first checked whether the claimant is insured by the organization. If not, the claimant is informed that the claim must be rejected. Otherwise, the severity of the claim is evaluated. Based on the outcome (simple or complex claims), relevant forms are sent to the claimant. Once the forms are returned, they are checked for completeness. If the forms provide all relevant details, the claim is registered in the Claims Management system, which ends the Claims Notification process. Otherwise, the claimant is informed to update the forms. Upon reception of the updated forms, they are checked again.

BPMN Exercise 1:Claims Notification process at a car insurer


When a claim related to a major car accident is evaluated, a clerk first retrieves the corresponding car accident report in the Police Reports database. If the report is retrieved, it is attached to the claim file. The claim file and the police report serve as input to a claims handler who calculates an initial claim estimate. Then, an “action plan” is created based on a “checklist”. Based on the action plan and the initial claims estimate, a claims manager negotiates a settlement with the customer. After this negotiation, the claims manager makes a final decision, updates the claim file to record this decision, and sends a letter to the claimant to inform him/her of the decision.

BPMN Exercise 2

CSS 496 Business Process Re-engineering for BS(CS)

Documents

Transcript of CSS 496 Business Process Re-engineering for BS(CS)