Analysis of Most Common Process Modelling

Mistakes in BPMN Process Models

Transcript
Analysis of Most Common Process Modelling Mistakes in BPMN Process Models dr. Tomislav
Rozman, Gregor Polančič, doc. dr. Romana Vajde Horvat 26. – 28. September 2007 Potsdam,
Germany Faculty of Electrical Engineering and Computer Science University of Maribor,
Slovenia Institute of Informatics Contents of the article

 Introduction
o What is Business Process Management & Modelling
o A little bit of history
o Similar work
 Research method
 Findings – process model antipatterns
 Conclusion s
 Discussion

What is Business Process management ?

 … a field of knowledge at the intersection between management and information technology,

encompassing methods, techniques and tools to design, enact, control, and analyze operational
business processes involving humans, organizations, applications, documents and other
sources of information 1 or
 …most overused word in the last few years?

1 van der Aalst, W.M.P., ter Hofstede, A.H.M. and Weske, M.: "Business Process
Management: A Survey", in Business Process Management, Proceedings of the First
International Conference. Springer Verlag, 2003. Business process management / business
process lifecycle What is (Business) Process modelling ?

 Better: Discrete process modelling

 Goal: to capture the knowledge how people (machines) perform their work (or, how we would
like them to perform it)
 M ain purpose : to ensure at least repeatability of organisation's processes
 Plethora of methods, methodologies, notations,…
 … but n o silver bullet

… Some process modelling notations

 EPC ,
 ARIS ,
 UML Activity diagrams ,
 OPM – Object Process Methodology ,
 BPMN – Business Process Modelling notation

Ontologically most complete (Recker et al, 2005) BPMN notation

 Visual representation of (business) processes – workflow

 It defines graphical symbols and additional attributes for process description
 Covers the process modelling concepts and patterns very well
 Easy to learn
 Based on : EPC, Petri nets, Activity diagrams (UML)
 Defines the mapping to execution languages (XPDL, BPEL4WS)
 Merging with UML?

A quick introduction to BPMN notation (1/2) Atomic activity – task Looping activity Ad-hoc
process Looping ad-hoc process Process (hidden details) Looping process (hidden details)
Process with details Branching (parallel execution) Data-based OR-decision  Event -based
OR-decision Merging A quick introduction to BPMN notation (2/2)  events gateways   pools
and messages A little bit of history

 BPMN notation has been taught since 2001 (University of Maribor, Faculty of electrical
engineering and computer science)
 BSc. Students of Information Systems, 8 th semester “ Information processing organization and
management” practical lectures
 The aim: (business) processes modeling , software standards, software projects organisation
 The modeling tool : Modified Microsoft Visio (‘’in-house’ symbols stencil)

Similar work

 Project ‘anti-pattern’
o = a pitfall, or, set of classes of commonly-reinvented bad solutions to problems
o = commonly repeated bad practices
 workflow patterns
o control flow patterns, resource patterns, data patterns and exception handling patterns

The problem

 BPMN does not prevent us to design bad process models, including syntactical, semantic and
pragmatically errors.
 P oor quality of process models can cause poor quality software requirements resulting in a
poor information system .

Research method

 Research question: What are the most common mistakes when modelling business process
diagrams using BPMN notation?
 a multiple case study research
 Analysis of t he process models ( designed by students ) from 2002 to 2007 by three
independent persons
 Extraction & classification of most common mistakes -> process anti-pattern
 Syntactical, semantic and pragmatic mistakes

Findings

 A set of 15 proces model anti-patterns

o Connecting elements (1-9)
o Other mistakes (9-15)
 Description of the antipatterns:
o Name,
o Possible practical impacts ,
o Type of error ,
o Proposed solution .

Pattern 1. Activities in one pool are not connected Pattern 2. Process does not contain a start
event Pattern 3. Process does not contain an end event Pattern 4. Sequence flow crosses
process boundary Pattern 5. Sequence flow crosses pool boundary Pattern 6. Gateway
 receives, evaluates or sends a message Pattern 7. Intermediate events are placed on the edge
of the pool Pattern 8. Hanging intermediate events or activities Pattern 9. Each lane in the pool
contains start event Pattern 10. Incorrect use of time events Solution: the meaning! Pattern 11.
Sequence and message event represent data flow Pattern 12. Event is used as a message flow
source Pattern 13. Improper use of flow elements Pattern 14. Starting timer placed instead of
intermediate timer Pattern 15. Exception flow is not connected to the exception Frequencies of
the anti-patterns appearance Exception is modelled, but not connected   Process does not
contain a end event  Sequence flow crosses process boundary  Hanging intermediate events
or activities Starting timer placed instead of intermediate timer  Conclusions

 We identified unique collection of most common process modelling mistakes or anti-patterns

 Possible p ractical problems:
o unwanted delays in the process performance,
o non-execution of the activities or
o simply ambiguity which could hinder the process performers at their work
 Practical implications:
o Improvement of the learning materials
o Design of A2 poster with anti-patterns & solutions
o Possible improvement of the BPMN
o Improvements of BPMN modelling tool: verification!
 Discussion