2006QUT ePrints (Queensland University of Technology)Open access

On the Translation between BPMN and BPEL: Conceptual Mismatch between Process Modeling Languages

Jan Recker, Jan Mendling

Open full text 144 citations

Abstract

Abstract. Business practice shows that, often, different process models are employed in the various phases of the Business Process Management life cycle, each providing a different paradigm for capturing and representing the business process domain. Recently, significant efforts have been made to overcome the disintegration of process models by providing complementary language standards for process design (BPMN) and execution (BPEL), based on the claim that these languages are semantically integrated. However, the conceptual mapping between both languages remains unclear, thus it is undecided whether any BPMN diagram can be transformed to BPEL. In this paper we argue that there is conceptual mismatch between BPMN and BPEL that needs to be identified in order to guide the language integration process semantically. In our analysis we take into account the various perspectives of the Business Process Management life cycle, in particular business and technical analyst perspectives. Our approach is generic and can also be utilized as a guiding framework for identifying conceptual mismatch between other business process modeling languages. 1

Open-access reader

About this research paper

What this paper is about

Abstract. Business practice shows that, often, different process models are employed in the various phases of the Business Process Management life cycle, each providing a different paradigm for capturing and representing the business process domain. Recently, significant efforts have been made to overcome the disintegration of process models by providing complementary language standards for process design (BPMN) and execution (BPEL), based on the claim that these languages are semantically integrated. However, the conceptual mapping between both languages remains unclear, thus it is undecided whether any BPMN diagram can be transformed to BPEL. In this paper we argue that there is conceptual mismatch between BPMN and BPEL that needs to be identified in order to guide the language integration process semantically. In our analysis we take into account the various perspectives of the Business Process Management life cycle, in particular business and technical analyst perspectives. Our approach is generic and can also be utilized as a guiding framework for identifying conceptual mismatch between other business process modeling languages. 1

Why it matters

OpenAlex reports 144 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Abstract. Business practice shows that, often, different process models are employed in the various phases of the Business Process Management life cycle, each providing a different paradigm for capturing and representing the business process domain. Recently, significant efforts have been made to overcome the disintegration of process models by providing complementary language standards for process design (BPMN) and execution (BPEL), based on the claim that these languages are semantically integrated. However, the conceptual mapping between both languages remains unclear, thus it is undecided whether any BPMN diagram can be transformed to BPEL. In this paper we argue that there is conceptual mismatch between BPMN and BPEL that needs to be identified in order to guide the language integration process semantically. In our analysis we take into account the various perspectives of the Business Process Management life cycle, in particular business and technical analyst perspectives. Our approach is generic and can also be utilized as a guiding framework for identifying conceptual mismatch between other business process modeling languages. 1

Key concepts: Business Process Model and Notation, Business Process Execution Language, Computer science, Business process modeling, Process modeling, Business process, Business process management, Artifact-centric business process model

Related papers

Back to paper searchBrowse research topicsOriginal source
On the Translation between BPMN and BPEL: Conceptual Mismatch between Process Modeling Languages — Research Paper | ScholarLens