Where did I go wrong? : explaining errors in business process models

N. Lohmann, D. Fahland

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

9 Citations (Scopus)

Abstract

Business process modeling is still a challenging task — especially since more and more aspects are added to the models, such as data lifecycles, security constraints, or compliance rules. At the same time, formal methods allow for a detection of errors in the early modeling phase. Detected errors are usually explained with a path from the initial to the error state. These paths can grow unmanageably and make the understanding and fixing of errors very time consuming. This paper addresses this issue and proposes a novel explanation of errors: Instead of listing the actions on the path to the error, only the decisions that lead to it are reported and highlighted in the original model. Furthermore, we exploit concurrency to create a compact artifact to explain errors.
Original languageEnglish
Title of host publicationBusiness Process Management (12th International Conference, BPM 2014, Haifa, Israel, September 7-11, 2014. Proceedings)
EditorsS. Sadiq, P. Soffer, H. Völzer
Place of PublicationBerlin
PublisherSpringer
Pages283-300
ISBN (Print)978-3-319-10171-2
DOIs
Publication statusPublished - 2014
Event12th International Conference on Business Process Management (BPM 2014) - Eindhoven, Netherlands
Duration: 7 Sep 201411 Sep 2014
Conference number: 12
http://bpm2014.haifa.ac.il/evover.net_9090/bpm2014.html

Publication series

NameLecture Notes in Computer Science
Volume8659
ISSN (Print)0302-9743

Conference

Conference12th International Conference on Business Process Management (BPM 2014)
Abbreviated titleBPM 2014
CountryNetherlands
CityEindhoven
Period7/09/1411/09/14
OtherConference was originally planned in Haifa, but due to the unstable situation in southern Israel, it was relocated to Eindhoven
Internet address

Fingerprint Dive into the research topics of 'Where did I go wrong? : explaining errors in business process models'. Together they form a unique fingerprint.

Cite this