2009Unpublished venueRequires access

EPC to BPEL transformations

L. O. Meertens

Open publisher page 0 citations

Abstract

Companies looking to improve their business processes can choose from several approaches. Almost all of these include modeling the processes. Implementing the modeled processes is the next step. Usually, developers create the required software, based on the models. However, often the resulting code does not meet the demands of the business. In order to improve the transition from business process models to code, Model-Driven Engineering (MDE) provides a promise by using model transformation. This promise consists of the ability to change business models into code automatically. This research investigates one of the possible model transformations. Namely, the transformation from Event-driven Process Chains (EPC) models to Business Process Execution Language (BPEL) specifications. Business modelers use EPC to create process models of the control flow. IT developers can use the resulting BPEL specifications as executable code, which contains the control flow

About this research paper

What this paper is about

Companies looking to improve their business processes can choose from several approaches. Almost all of these include modeling the processes. Implementing the modeled processes is the next step. Usually, developers create the required software, based on the models. However, often the resulting code does not meet the demands of the business. In order to improve the transition from business process models to code, Model-Driven Engineering (MDE) provides a promise by using model transformation. This promise consists of the ability to change business models into code automatically. This research investigates one of the possible model transformations. Namely, the transformation from Event-driven Process Chains (EPC) models to Business Process Execution Language (BPEL) specifications. Business modelers use EPC to create process models of the control flow. IT developers can use the resulting BPEL specifications as executable code, which contains the control flow

Why it matters

A significance statement is not available in the OpenAlex record.

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

Companies looking to improve their business processes can choose from several approaches. Almost all of these include modeling the processes. Implementing the modeled processes is the next step. Usually, developers create the required software, based on the models. However, often the resulting code does not meet the demands of the business. In order to improve the transition from business process models to code, Model-Driven Engineering (MDE) provides a promise by using model transformation. This promise consists of the ability to change business models into code automatically. This research investigates one of the possible model transformations. Namely, the transformation from Event-driven Process Chains (EPC) models to Business Process Execution Language (BPEL) specifications. Business modelers use EPC to create process models of the control flow. IT developers can use the resulting BPEL specifications as executable code, which contains the control flow

Key concepts: Business Process Execution Language, Executable, Computer science, Business Process Model and Notation, Business process modeling, Software engineering, Control flow, Model transformation

Related papers

Back to paper searchBrowse research topicsOriginal source
EPC to BPEL transformations — Research Paper | ScholarLens