Getting Rid of the OR-Join in Business Process Models

Mendling, Jan; Aalst, Wil M. P. van der

doi:10.1109/edoc.2007.10

Cited by 8 publications

(3 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[36,39]) and in one incarnation or another it occurs in a number of systems and languages. The original definition of the OR-join for YAWL in [7] was superceded by the definition provided in [57].…”

Section: Core Yawlmentioning

confidence: 99%

Surmounting BPM challenges: the YAWL story

Russell

Hofstede

2009

Comp. Sci. Res. Dev.

View full text Add to dashboard Cite

The field of Business Process Management (BPM) has evolved considerably over the past decade. Many proposals for business process modelling and/or execution have emerged and some of these have faded into oblivion again. The Workflow Patterns Initiative aimed at achieving a more structured approach to language comparison and development. The patterns that were distilled served as the basis for YAWL (Yet Another Workflow Language). In this paper YAWL is positioned with respect to historical developments in BPM and current challenges in the field.

show abstract

Section: Core Yawlmentioning

confidence: 99%

Surmounting BPM challenges: the YAWL story

Russell

Hofstede

2009

Comp. Sci. Res. Dev.

View full text Add to dashboard Cite

show abstract

“…This approach can be used to transform a Petri Net via a transition system into another behaviour-equivalent Petri net. Respective techniques allow to elimate unnecessary net elements (e.g., silent activities, unnecessary places) [32] or to discard OR-joins from process models [33].…”

Section: Related Workmentioning

confidence: 99%

Refactoring Process Models in Large Process Repositories

Weber

Reichert

2008

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

With the increasing adoption of process-aware information systems (PAIS), large process model repositories have emerged. Over time respective models have to be re-aligned to the real-world business processes through customization or adaptation. This bears the risk that model redundancies are introduced and complexity is increased. If no continuous investment is made in keeping models simple, changes are becoming increasingly costly and error-prone. Though refactoring techniques are widely used in software engineering to address related problems, this does not yet constitute state-of-the art in business process management. Process designers either have to refactor process models by hand or cannot apply respective techniques at all. This paper proposes a set of behaviour-preserving techniques for refactoring large process repositories. This enables process designers to effectively deal with model complexity by making process models better understandable and easier to maintain.

show abstract

“…Most notable is the work on Petri net synthesis from a labeled transition system [54,55]. This work has been used to eliminate OR-joins from process models [56]. Further research discusses the untangling of unstructured loops and the derivation of structured BPEL from arbitrary Petri nets [57,58].…”

Section: Implications For Future Researchmentioning

confidence: 99%

Empirical Studies in Process Model Verification

Mendling

2009

Transactions on Petri Nets and Other Models of Concurrency II

View full text Add to dashboard Cite

Abstract. Despite the large body of knowledge on formal analysis techniques for process models, in particular Petri nets, there has been a notable gap of empirical research into verification. In this paper we compare the few studies that report results from applying verification techniques to real-world process model collections. For this comparison we are particularly interested in the different approaches, their computational performance, and the number of errors found. Our comparison reveals that most of the samples have error rates of 10% to 20%. Some of the studies have established a connection between error probability and process model metrics, as well as between model understanding and both metrics and modeling competence of the model reader. Based on these results, we discuss implications and directions for future research.

show abstract

Getting Rid of the OR-Join in Business Process Models

Abstract: Abstract-In practice, the development of process-aware information systems suffers from a gap between conceptual business process models and executable workflow specifications. Because of this gap, conceptual models are hardly reused as execution templates.

Cited by 8 publications

References 25 publications

Surmounting BPM challenges: the YAWL story

Surmounting BPM challenges: the YAWL story

Refactoring Process Models in Large Process Repositories

Empirical Studies in Process Model Verification

Contact Info

Product

Resources

About