scholarly journals Pattern-Based Translation of BPMN Process Models to BPEL Web Services

Author(s):  
Chun Ouyang ◽  
Marlon Dumas ◽  
Arthur H.M. ter Hofstede ◽  
Wil M.P. van der Aalst

The business process modeling notation (BPMN) is a graph-oriented language primarily targeted at domain analysts and supported by many modeling tools. The business process execution language for Web services (BPEL) on the other hand is a mainly block-structured language targeted at software developers and supported by several execution platforms. Translating BPMN models into BPEL code is a necessary step towards standards-based business process development environments. This translation is challenging since BPMN and BPEL represent two fundamentally different classes of languages. Existing BPMN-to-BPEL translations rely on the identification of block-structured patterns in BPMN models that are mapped onto structured BPEL constructs. This article advances the state of the art in BPMN-to-BPEL translation by defining methods for identifying not only perfectly block-structured fragments in BPMN models, but quasi-structured fragments that can be turned into perfectly structured ones and flow-based acyclic fragments that can be mapped onto a combination of structured constructs and control links. Beyond its direct relevance in the context of BPMN and BPEL, this article addresses issues that arise generally when translating between graph-oriented and block-structured flow definition languages.

Author(s):  
Terje Wahl ◽  
Guttorm Sindre

Evaluation of modelling languages is important both to be able to select the most suitable languages according to the needs and to improve existing languages. In this chapter, business process modeling notation (BPMN) is presented and analytically evaluated according to the semiotic quality framework. BPMN is a functionally oriented language well suited for modeling within the domain of business processes, and probably general processes outside of the business domain. The evaluation indicates that BPMN is easily learned for simple use, and business process diagrams (BPDs) are relatively easy to understand. Tools can fairly easily map BPDs into the Web Services Business Process Execution Language (WS-BPEL) (formerly known as BPEL4WS) format, but executable systems then require creation of Web services representing the activities in BPDs. An evaluation according to the Bunge-Wand-Weber (BWW) ontology is useful for finding ontological discrepancies, and the semiotic framework is useful for evaluating quality on a relatively general level. Thus, these methods complement each other.


2016 ◽  
Vol 22 (3) ◽  
pp. 566-593 ◽  
Author(s):  
Julio Cesar Sampaio do Prado Leite ◽  
Flavia Maria Santoro ◽  
Claudia Cappelli ◽  
Thais Vasconcelos Batista ◽  
Fabiana Jack Nogueira Santos

Purpose – The purpose of this paper is to propose a representation scheme based on the i* strategic actor model to represent the process owner information and show how to incorporate this approach into the event driven process chain and Business Process Modeling Notation-BPMN meta-models and also into the aspect-oriented business process modeling (BPM) context. Design/methodology/approach – The authors use a case study in a real setting to evaluate the proposal and a controlled experiment to get more evidence about its relevance. Findings – The authors presented evidence both from a case study in a real-world library showing the importance of representing – previously unavailable – process owner information, and from an experiment which involved participants analyzing the same models of the case study, confirming the preliminary evidences. It is important to stress the recognition that the proposed representation provided more transparency, in terms of ownership, than the usual BPM models. These benefits are due to the combination of the aspect-oriented approach and the strategic actor model, providing ownership information in a more transparent way. Originality/value – The authors not only argue the importance of clearly established process ownership, both of the core process and the aspectual process, but also the authors presented an approach to represent the actor involved in process and aspect ownership as an instantiation of the i* strategic actor. Using this approach, the process owner can be defined in terms of actors instead of the activities performed. It is also possible to define the aspect owner and to include the aspectual process concept in the business process model.


2019 ◽  
Vol 4 (2) ◽  
pp. 116
Author(s):  
Hilman Nuril Hadi ◽  
Tri Astoto Kurniawan ◽  
Ismiarta Aknuranda

BPMN has become the standard of business process modeling indescribing the existing series of business process. By engaging BPMN, an analystwould possibly able to model the whole business process activities in whichhe/she may analyze business process upon design time. It can be done byanalyzing the structure, behavior, or semantic of process model. In certaincondition one may ask a question what would the effects of the process be if itwere to be executed up to this point?. However, it cannot be solved with onlygraphical notation, but with its semantics. In practice, several modeling tools stilldo not provide a feature for managing information regarding the effects/resultsin the business process model. In fact, analysts should be supported with a toolin order to semantically enrich a process model with its effects. This articledescribes effect annotation semantically towards activity in the BPMN modelincluding the rules in representing its effects. The effect annotation will be suitedtowards activity type (atomic and compound activities). The outcomes of plugin development of eclipse BPMN2 modeler for representing semantic effect arealso described in this paper.


Author(s):  
Matthias Kloppmann ◽  
Dieter Koenig ◽  
Simon Moser

This chapter introduces a set of languages intended to model and run business processes. The Business Process Modeling Notation 1.1 (BPMN) is a notation used to graphically depict business processes. BPMN is able to express choreographies, i.e. the cooperation of separate, autonomous business processes to jointly achieve a larger scenario. Since BPMN is only a notation, there is no specification for a meta-model that allows rendering BPMN choreographies into an executable form. This chapter describes how the Service Component Architecture (SCA) and the Web Services Business Process Execution Language (WS-BPEL) help to close that gap. BPMN, SCA and WS-BPEL can jointly be used and combined to model, deploy and execute business process choreographies. We will also integrate the related BPEL4People specification, since BPMN allows human ‘user tasks’, but WS-BPEL focuses only on automated business process. The authors argue that, based on these specifications, the dichotomy between modeling and execution can be addressed efficiently. In this chapter, we will show that a key aspect of the future of Business Process Management is to combine graphical modeling (via BPMN) with a precise specification of an executable business process (via WS-BPEL and related standards).


2011 ◽  
pp. 155-190 ◽  
Author(s):  
C. Ouyang ◽  
W. Van der Aalst ◽  
M. Dumas

The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to address these limitations. The chapter also considers the possibility of applying formal methods and Semantic Web technology to support the rigorous development of service-oriented processes using BPEL.


Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


2020 ◽  
Vol 7 (2) ◽  
pp. 71-76
Author(s):  
Salma Fatia ◽  
Muhammad Ainul Yaqin ◽  
Adi Heru Utomo

Abstract— In an organizational environment, there are various business process models with the same procedures. If an organization builds a system with the same procedure repeatedly, it will undoubtedly incur a lot of effort and money. Therefore, it is necessary to extract common fragments to save effort. This research uses four scenarios of business process models: sequence, branching, nested branching, and looping. This study uses Business Process Modeling Notation (BPMN) notation so that the process model consists of activities, connectors, and gateways. Structural similarity is measured using the Jaccard similarity formula by comparing the process model. The similarity of behavior is measured using the Transition Adjacency Relations (TARs) method to obtain common fragments. The results show that the sequence process model will produce a common fragment that tends to be sequential too. The branching will produce a common fragment that tends to branch, and nested branching will produce a common fragment that tends to be branched and nested, as well as looping will produce a common fragment contains looping too. The experimental results show that the proposed method can extract common fragments based on the available business process models. Keywords—BPMN; common fragment; behavioral similarity; TARs   Abstrak— Dalam lingkungan organisasi, terdapat berbagai model proses bisnis dengan prosedur yang sama. Jika suatu organisasi membangun sistem dengan prosedur yang sama secara berulang-ulang, niscaya akan mengeluarkan banyak tenaga dan biaya. Oleh karena itu, perlu mengekstrak fragmen umum untuk menghemat tenaga. Penelitian ini menggunakan empat skenario model proses bisnis yaitu sequence, branching, nested branching, dan looping. Penelitian ini menggunakan notasi Business Process Modeling Notation (BPMN) sehingga model proses terdiri dari aktivitas, konektor, dan gateway. Kemiripan struktural diukur menggunakan rumus kemiripan Jaccard dengan membandingkan model proses. Kesamaan perilaku diukur menggunakan metode Transition Adjacency Relations (TARs) untuk mendapatkan fragmen yang sama. Hasil penelitian menunjukkan bahwa model sequence process akan menghasilkan common fragment yang cenderung berurutan juga. Percabangan akan menghasilkan fragmen umum yang cenderung bercabang, dan percabangan bersarang akan menghasilkan fragmen umum yang cenderung bercabang dan bersarang, serta perulangan akan menghasilkan fragmen umum yang berisi perulangan juga. Hasil eksperimen menunjukkan bahwa metode yang diusulkan dapat mengekstrak fragmen umum berdasarkan model proses bisnis yang tersedia. Keywords—BPMN; common fragment; kemiripan perilaku; TARs


Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


Author(s):  
Donald R. Chand ◽  
Alina M. Chircu

This chapter presents a variety of business process modeling notations that range from programming logic flowcharts to the new standard, BPMN (Business Process Modeling Notation), as put forth by the Business Process Management Initiative (BPMI) (http://www.bpmi.org). Specifically, it discusses (1) the use of unstructured programming flowcharts in modeling business processes and their adaptation in process flow diagramming notation, (2) the UML activity diagram, and (3) BPMN, a comprehensive notation for documenting and modeling complex business processes. Using simple examples, this chapter brings out the inherent complexity of modeling business processes and the need for modeling tools that synchronize and align the mental models of business users, process analyst and information technology (IT) systems developers in order to correctly represent the intended process.


Author(s):  
Jens Kolb ◽  
Benjamin Rudner ◽  
Manfred Reichert

Contemporary business process modeling tools provide menu-based user interfaces for defining and visualizing process models. Such menu-based interactions have been optimized for applications running on desktop computers, but are limited regarding their use on multi-touch devices. At the same time, the widespread use of mobile devices in daily business life as well as their multi-touch capabilities offer promising perspectives for intuitively defining and changing business process models. Additionally, multi-touch tables will foster collaborative business process modeling based on natural as well as intuitive gestures and interactions. This paper presents the results of an experiment that investigated the way users define and change business process models using multi-touch devices. Based on experiment results, a core gesture set is designed enabling the easy definition and change of business process models with multi-touch devices. Finally, a proof-of-concept implementation of this core gesture set is presented. Overall, gesture-based process modeling and multi-touch devices will foster new ways of (collaborative) business process modeling.


Sign in / Sign up

Export Citation Format

Share Document