ScienceDirect® Home Skip Main Navigation Links
You have guest access to ScienceDirect. Find out more.
 
Home
Browse
My Settings
Alerts
Help
 Quick Search
 Search tips (Opens new window)
    Clear all fields    
advertisementadvertisement
Information and Software Technology
Volume 50, Issue 3, February 2008, Pages 131-159
 
Font Size: Decrease Font Size  Increase Font Size
 Abstract - selected
Article
Purchase PDF (1542 K)

 
 
 
Related Articles in ScienceDirect
View More Related Articles
 
View Record in Scopus
 
doi:10.1016/j.infsof.2006.11.004    How to Cite or Link Using DOI (Opens New Window)
Copyright © 2006 Elsevier B.V. All rights reserved.

Translating unstructured workflow processes to readable BPEL: Theory and implementation

Wil M.P. van der Aalsta, b, E-mail The Corresponding Author and Kristian Bisgaard Lassenb, Corresponding Author Contact Information, E-mail The Corresponding Author

aDepartment of Computer Science, Eindhoven University of Technology, P.O. Box 513, NL-5600 MB, Eindhoven, The Netherlands bDepartment of Computer Science, University of Aarhus, IT-parken, Aabogade 34, DK-8200 Aarhus N, Denmark

Received 30 May 2006; 
revised 12 October 2006; 
accepted 5 November 2006. 
Available online 13 December 2006.

Purchase the full-text article



References and further reading may be available for this article. To view references and further reading you must purchase this article.

Abstract

The Business Process Execution Language for Web Services (BPEL) has emerged as the de facto standard for implementing processes. Although intended as a language for connecting web services, its application is not limited to cross-organizational processes. It is expected that in the near future a wide variety of process-aware information systems will be realized using BPEL. While being a powerful language, BPEL is difficult to use. Its XML representation is very verbose and only readable for the trained eye. It offers many constructs and typically things can be implemented in many ways, e.g., using links and the flow construct or using sequences and switches. As a result only experienced users are able to select the right construct. Several vendors offer a graphical interface that generates BPEL code. However, the graphical representations are a direct reflection of the BPEL code and not easy to use by end-users. Therefore, we provide a mapping from Workflow Nets (WF-nets) to BPEL. This mapping builds on the rich theory of Petri nets and can also be used to map other languages (e.g., UML, EPC, BPMN, etc.) onto BPEL. In addition to this we have implemented the algorithm in a tool called WorkflowNet2BPEL4WS.

Keywords: BPEL4WS; Petri nets; Workflow management; Business process management

Article Outline

1. Introduction
2. Related work
3. Preliminaries
3.1. Business Process Execution Language for Web Services (BPEL)
3.2. Petri nets
3.3. WF-nets
3.4. Soundness
4. Decomposing a WF-net into components
5. Mapping WF-nets onto BPEL
5.1. Annotating WF-nets
5.2. Algorithm
6. Implementation: WorkflowNet2BPEL4WS
7. Case study: generating BPEL template code for a bank system
8. Conclusion
Appendix A. Example to illustrate the algorithm
References


















 
Home
Browse
My Settings
Alerts
Help
Elsevier.com (Opens new window)
About ScienceDirect  |  Contact Us  |  Information for Advertisers  |  Terms & Conditions  |  Privacy Policy
Copyright © 2008 Elsevier B.V. All rights reserved. ScienceDirect® is a registered trademark of Elsevier B.V.