DsCWeaver: Synchronization-Constraint Aspect Extension to Procedural Process Specification Languages

DsCWeaver: Synchronization-Constraint Aspect Extension to Procedural Process Specification Languages

Qinyi Wu, Calton Pu, Akhil Sahai, Roger Barga
Copyright: © 2008 |Volume: 5 |Issue: 3 |Pages: 22
ISSN: 1545-7362|EISSN: 1546-5004|ISSN: 1545-7362|EISBN13: 9781615204489|EISSN: 1546-5004|DOI: 10.4018/jwsr.2008070105
Cite Article Cite Article

MLA

Wu, Qinyi, et al. "DsCWeaver: Synchronization-Constraint Aspect Extension to Procedural Process Specification Languages." IJWSR vol.5, no.3 2008: pp.96-117. http://doi.org/10.4018/jwsr.2008070105

APA

Wu, Q., Pu, C., Sahai, A., & Barga, R. (2008). DsCWeaver: Synchronization-Constraint Aspect Extension to Procedural Process Specification Languages. International Journal of Web Services Research (IJWSR), 5(3), 96-117. http://doi.org/10.4018/jwsr.2008070105

Chicago

Wu, Qinyi, et al. "DsCWeaver: Synchronization-Constraint Aspect Extension to Procedural Process Specification Languages," International Journal of Web Services Research (IJWSR) 5, no.3: 96-117. http://doi.org/10.4018/jwsr.2008070105

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

Correct synchronization among activities is critical in a business process. Current process languages such as BPEL specify the control flow of processes procedurally, which can lead to inflexible and tangled code for managing a crosscutting aspect—synchronization constraints that define permissible sequences of execution for activities. In this article, we present DSCWeaver, a tool that enables a synchronization-aspect extension to procedural languages. It uses DSCL (directed-acyclic-graph synchronization constraint language) to achieve three desirable properties for synchronization modeling: fine granularity, declarative syntax, and validation support. DSCWeaver then automatically generates executable code for synchronization. We demonstrate the advantages of our approach in a service deployment process written in BPEL and evaluate its performance using two metrics: lines of code (LoC) and places to visit (PtV). Evaluation results show that our approach can effectively reduce the development effort of process programmers while providing performance competitive to unwoven BPEL code.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.