Business process modeling and enactment are notoriously complex, especially in open settings, where business partners are autonomous, requirements must be continually finessed, and exceptions frequently arise because of real-world or organizational problems. Traditional approaches, which attempt to capture processes as monolithic flows, have proven inadequate in addressing these challenges. We propose (business) protocols as components for developing business processes. A protocol is an abstract, modular, publishable specification of an interaction among different roles to be played by different participants. When instantiated with the participants' internal policies, protocols yield concrete business processes. Protocols are reusable and refinable, thus simplifying business process design. We show how protocols and their composition are theoretically founded in the pi-calculus.
%0 Journal Article
%1 desai05
%A Desai, N.
%A Mallya, A. U.
%A Chopra, A. K.
%A Singh, M. P.
%D 2005
%J IEEE Transactions on Software Engineering
%K policy process software business
%N 12
%P 1015--1027
%T Interaction Protocols as Design Abstractions for Business Processes
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1566604
%V 31
%X Business process modeling and enactment are notoriously complex, especially in open settings, where business partners are autonomous, requirements must be continually finessed, and exceptions frequently arise because of real-world or organizational problems. Traditional approaches, which attempt to capture processes as monolithic flows, have proven inadequate in addressing these challenges. We propose (business) protocols as components for developing business processes. A protocol is an abstract, modular, publishable specification of an interaction among different roles to be played by different participants. When instantiated with the participants' internal policies, protocols yield concrete business processes. Protocols are reusable and refinable, thus simplifying business process design. We show how protocols and their composition are theoretically founded in the pi-calculus.
@article{desai05,
abstract = {Business process modeling and enactment are notoriously complex, especially in open settings, where business partners are autonomous, requirements must be continually finessed, and exceptions frequently arise because of real-world or organizational problems. Traditional approaches, which attempt to capture processes as monolithic flows, have proven inadequate in addressing these challenges. We propose (business) protocols as components for developing business processes. A protocol is an abstract, modular, publishable specification of an interaction among different roles to be played by different participants. When instantiated with the participants' internal policies, protocols yield concrete business processes. Protocols are reusable and refinable, thus simplifying business process design. We show how protocols and their composition are theoretically founded in the pi-calculus.},
added-at = {2006-03-24T16:34:33.000+0100},
author = {Desai, N. and Mallya, A. U. and Chopra, A. K. and Singh, M. P.},
biburl = {https://www.bibsonomy.org/bibtex/2dc97f3c58529f5c51eb09fa6658b5c50/neilernst},
citeulike-article-id = {461354},
comment = {- interesting, but perhaps overly complex.
- not clear what the real difference with BPEL is.
-},
description = {sdasda},
interhash = {18193dc27a356acfccf5f54d12ae03db},
intrahash = {dc97f3c58529f5c51eb09fa6658b5c50},
journal = {IEEE Transactions on Software Engineering},
keywords = {policy process software business},
number = 12,
pages = {1015--1027},
priority = {0},
timestamp = {2006-03-24T16:34:33.000+0100},
title = {Interaction Protocols as Design Abstractions for Business Processes},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1566604},
volume = 31,
year = 2005
}