Toward a Formal Semantics for Control-Flow Process Models

Toward a Formal Semantics for Control-Flow Process Models

Henry H. Bi, John Nolt
Copyright: © 2012 |Pages: 26
DOI: 10.4018/jdm.2012040104
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

A number of information systems have been developed to automate business processes. For process modeling, verification, and automation in information systems, a formal semantics of control-flow process models is needed. Usually process modeling languages (e.g., BPMN, EPC, IDEF3, UML, and WfMC standards) are used to represent control-flow process models. When these process modeling languages are developed, their informal semantics are typically described using examples, but their formal semantics are not defined. Although many different semantics for control-flow process models have been proposed, the existing semantics specifications have limitations because they do not support certain desirable features. In this paper, we propose a new formal semantics for control-flow process models. We show that it is more accurate, complete, and applicable than the existing semantics specifications.
Article Preview
Top

Introduction

A number of information systems, such as ERP systems (Wagner & Monk, 2008) and business process management (BPM) systems (Chang, 2005; WfMC, 1999), have been developed to automate business processes. Those information systems employ a variety of process modeling languages, including BPMN (OMG, 2010a), EPC (Scheer, 1999), IDEF3 (Mayer et al., 1995), UML activity diagrams (Ambler, 2004; OMG, 2010b), and Workflow Management Coalition (WfMC) standards (WfMC, 1999).

These modeling languages represent business activities and their ordering relationships as control-flow process models. Activities are called tasks in BPMN, functions in EPC, units of behavior in IDEF3, and actions in UML. Typical ordering relationships include sequence (e.g., voting after discussing), AND for concurrency (e.g., scheduling production and purchasing production materials separately and concurrently), XOR for exclusive (exactly one) choices (e.g., approving or disapproving an application), and OR for inclusive (at least one) choices (e.g., interviewing one or more of suspect, victim, and witness separately and concurrently). To study the common syntactic and semantic features of process modeling languages, Figure 1 gives examples of control-flow process models represented in five different modeling languages. Appendix A provides a comparison of those modeling languages by using them to represent the same process. The process structures in the process models in Figure 1 will be used in discussions throughout this paper.

Figure 1.

Control-flow process models represented in five different process modeling languages

jdm.2012040104.f01

Because a formal semantics of control-flow process models is needed for process modeling, verification, and automation in information systems, substantial research efforts have been made on specifying a formal semantics of control-flow process models for more than a decade (Chen & Scheer, 1994; Dehnert & van der Aalst, 2004; Dumas, Grosskopf, Hettel, & Wynn, 2007; Kindler, 2006; Langner, Schneider, & Wehler, 1998; Mendling & van der Aalst, 2006, 2007; Rittgen, 2000; van der Aalst, 1998, 1999; van der Aalst & ter Hofstede, 2005; Wynn, Edmond, van der Aalst, & ter Hofstede, 2005). However, there is still lack of well-accepted formal semantics of control-flow process models for two reasons. First, when modeling languages like BPMN, EPC, IDEF3, UML, and WfMC standards are developed, their informal semantics are typically described using examples, but their formal semantics are not defined. Second, although a number of formal semantics have been proposed, the existing semantics specifications have limitations in terms of accuracy and completeness. Those limitations will be discussed in detail later.

To address this research problem, the objective of this paper is to propose a more accurate and complete formal semantics for control-flow process models than the existing semantics specifications. To accomplish this research objective, we will provide an in-depth review of the existing semantics specifications, propose a new formal semantics for control-flow process models, and provide a comparison to show the desirable features that are supported by this new semantics but not by the existing semantics specifications. We will also discuss possible extensions of this new semantics.

Complete Article List

Search this Journal:
Reset
Volume 35: 1 Issue (2024)
Volume 34: 3 Issues (2023)
Volume 33: 5 Issues (2022): 4 Released, 1 Forthcoming
Volume 32: 4 Issues (2021)
Volume 31: 4 Issues (2020)
Volume 30: 4 Issues (2019)
Volume 29: 4 Issues (2018)
Volume 28: 4 Issues (2017)
Volume 27: 4 Issues (2016)
Volume 26: 4 Issues (2015)
Volume 25: 4 Issues (2014)
Volume 24: 4 Issues (2013)
Volume 23: 4 Issues (2012)
Volume 22: 4 Issues (2011)
Volume 21: 4 Issues (2010)
Volume 20: 4 Issues (2009)
Volume 19: 4 Issues (2008)
Volume 18: 4 Issues (2007)
Volume 17: 4 Issues (2006)
Volume 16: 4 Issues (2005)
Volume 15: 4 Issues (2004)
Volume 14: 4 Issues (2003)
Volume 13: 4 Issues (2002)
Volume 12: 4 Issues (2001)
Volume 11: 4 Issues (2000)
Volume 10: 4 Issues (1999)
Volume 9: 4 Issues (1998)
Volume 8: 4 Issues (1997)
Volume 7: 4 Issues (1996)
Volume 6: 4 Issues (1995)
Volume 5: 4 Issues (1994)
Volume 4: 4 Issues (1993)
Volume 3: 4 Issues (1992)
Volume 2: 4 Issues (1991)
Volume 1: 2 Issues (1990)
View Complete Journal Contents Listing