Home > Research > Publications & Outputs > Interaction protocols as design abstractions fo...
View graph of relations

Interaction protocols as design abstractions for business processes

Research output: Contribution to journalJournal article

Published

Standard

Interaction protocols as design abstractions for business processes. / Desai, Nirmit; Mallya, Ashok U.; Chopra, Amit K.; Singh, Munindar P.

In: IEEE Transactions on Software Engineering, Vol. 31, No. 12, 01.12.2005, p. 1015-1027.

Research output: Contribution to journalJournal article

Harvard

Desai, N, Mallya, AU, Chopra, AK & Singh, MP 2005, 'Interaction protocols as design abstractions for business processes', IEEE Transactions on Software Engineering, vol. 31, no. 12, pp. 1015-1027. https://doi.org/10.1109/TSE.2005.140

APA

Desai, N., Mallya, A. U., Chopra, A. K., & Singh, M. P. (2005). Interaction protocols as design abstractions for business processes. IEEE Transactions on Software Engineering, 31(12), 1015-1027. https://doi.org/10.1109/TSE.2005.140

Vancouver

Desai N, Mallya AU, Chopra AK, Singh MP. Interaction protocols as design abstractions for business processes. IEEE Transactions on Software Engineering. 2005 Dec 1;31(12):1015-1027. https://doi.org/10.1109/TSE.2005.140

Author

Desai, Nirmit ; Mallya, Ashok U. ; Chopra, Amit K. ; Singh, Munindar P. / Interaction protocols as design abstractions for business processes. In: IEEE Transactions on Software Engineering. 2005 ; Vol. 31, No. 12. pp. 1015-1027.

Bibtex

@article{04149cc43f2b44699e28a43ac94d9934,
title = "Interaction protocols as design abstractions for business processes",
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 phi;-calculus.",
author = "Nirmit Desai and Mallya, {Ashok U.} and Chopra, {Amit K.} and Singh, {Munindar P.}",
year = "2005",
month = dec
day = "1",
doi = "10.1109/TSE.2005.140",
language = "English",
volume = "31",
pages = "1015--1027",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
number = "12",

}

RIS

TY - JOUR

T1 - Interaction protocols as design abstractions for business processes

AU - Desai, Nirmit

AU - Mallya, Ashok U.

AU - Chopra, Amit K.

AU - Singh, Munindar P.

PY - 2005/12/1

Y1 - 2005/12/1

N2 - 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 phi;-calculus.

AB - 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 phi;-calculus.

U2 - 10.1109/TSE.2005.140

DO - 10.1109/TSE.2005.140

M3 - Journal article

VL - 31

SP - 1015

EP - 1027

JO - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

IS - 12

ER -