Business+Process+Modelling

Business Process Modelling

[|Business Process Management Workshops] [|Lecture Notes in Business Information Processing], 2010, Volume 43, Part 1, 5-16, DOI: 10.1007/978-3-642-12186-9_2

**Business Process Management Workshops** 2010 Rinderle-Ma, Stefanie Sadiq, Shazia Leymann, Frank

BPMN maps (can be transformed) to BPEL (Execution Language) - Data modelling important for this.

Data Objects - read or written by activities - objects states can be pre-conditions or effects of activities.

Data anomalies may result from concurrent activities

Semantics of data sets left to interpreter of model, but input sets can be specified for activities, where a conjunction of data conditions must hold before the activity can run. Once any inout set's conditions are met, the activity can run.

Processes may handle a single copy of data object, but state of that object may change.

Process models - deadloacks. livelocks etc.

Control flow versus Data Flow - Cohesion and coupling?

Process flows must meet correctness criteria - ie: soundness - activities are not left running when process finishes,

Logic - XOR, AND etc.

Kunti (2010):

Business Functions - eg: Manage Purchases, Manage Loans - consist of Business Processes.

Business Processes may be generic then customised (varied) to a particular application.

Business processes designed to run on WorkFlow engines?