Service Interaction Pattern
by
Benedikt Liegener
—
last modified
Apr 26, 2012 12:18
—
filed under:
KnowledgeModel
Definitions
| Term: Service Interaction Pattern |
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) |
||||
| Service Composition and
Coordination (KM-SC) |
A Service Interaction Pattern is a set of the most
frequent interaction scenarios between Web services, used
for assessment of choreography languages. The patterns include
bilateral, multilateral, competing, atomic and causally related
interactions. [Barros et al. 2005] {SYN: Interaction Pattern} The Service Interaction Patterns website [ServiceInteractionSite] is dedicated to documenting common problems and approaches (i.e. patterns) related to the design and implementation of web services, with a special emphasis on situations that arise when services engage in concurrent and interrelated interactions. In addition to providing reusable knowledge, these patterns allow emerging web services design and implementation solutions to be benchmarked against abstracted forms of representative scenarios. For example, the collected patterns can be used to evaluate languages and platforms supporting contract-based service development and service composition such as WSDL, WS-BPEL, JBI, Indigo, etc. |
||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
|||||
Competencies
- N/A
References
- [Barros et al. 2005] Barros, Alistair P., Dumas, Marlon, & ter Hofstede, Arthur H.M., " Service Interaction Patterns: Towards a Reference Framework for Service-based Business Process Interconnection". QUT Technical report, FIT-TR-2005-02, Queensland University of Technology, Brisbane, 2005.
- [ServiceInteractionSite] Website for Service Interaction Patterns,
http://math.ut.ee/~dumas/ServiceInteractionPatterns/index.html
