Business Protocol
by
Benedikt Liegener
—
last modified
Mar 26, 2012 14:56
—
filed under:
KnowledgeModel
Definitions
Term: Business Protocol |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
A Business Protocol specifies the possible message exchange sequences (conversations) that are supported by a business process, either from a local or global point of view, respectively referred to as orchestration- and choreography business protocols [Mancioppi et al, 2008]. Business protocols can be specified using notations such as BPELlight [Nitzsche et al, 2007], [Nitzsche et al, 2008], and more generally any formalism that describes timed languages between and among participants made of message exchanges. | |||
Service Composition and
Coordination (KM-SC) |
|||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
Competencies
- Tilburg: Business Process Management; http://www.tilburguniversity.nl/eriss/research/;
Willem-Jan van den Heuvel, Michele Mancioppi, Mike Papazoglou
- USTUTT: Business Process Management; http://www.iaas.uni-stuttgart.de/indexE.php; Frank Leymann, Dimka Karastoyanova
- UCBL: Business protocols; http://liris.cnrs.fr/bd/; Salima
Benbernou, Emmanuel Coquery, Francois Hantry, Mohand Said-Hacid, Karima
Mokhtari
- UPM: Multi-Party Business Protocols;http://clip.dia.fi.upm.es; Manuel Carro
Scenarios
- Original Equipment Automotive Supply Chain (Case Study Solution)
References
- [Mancioppi et al, 2008] Michele Mancioppi, Manuel Carro, Willem-Jan van den Heuvel, Mike P. Papazoglou: Sound Multi-party Business Protocols for Service Networks. ICSOC 2008:302-316
- [Nitzsche et al, 2007] Jörg Nitzsche, Tammo van Lessen, Dimka
Karastoyanova, Frank Leymann: BPEL^light. BPM 2007:214-229
- [Nitzsche et al, 2008] Jörg Nitzsche, Tammo van Lessen, Frank
Leymann: Extending BPEL^light for Expressing Multi-Partner Message
Exchange Patterns. EDOC 2008:245-254