Service composition and interaction in a SOC middleware supporting separation of concerns with flows and views

D.K.W. Chiu, Qing Li, P.C.K. Hung, Z. Shan, S.C. Cheung, Y. Yang, M. Farwick

Research output: Journal article publicationLiterature reviewAcademic researchpeer-review

3 Citations (Scopus)

Abstract

Service-Oriented Computing (SOC) has recently gained attention both within industry and academia; however, its characteristics cannot be easily solved using existing distributed computing technologies. Composition and interaction issues have been the central concerns, because SOC applications are composed of heterogeneous and distributed processes. To tackle the complexity of inter-organizational service integration, the authors propose a methodology to decompose complex process requirements into different types of flows, such as control, data, exception, and security. The subset of each type of flow necessary for the interactions with each partner can be determined in each service. These subsets collectively constitute a process view, based on which interactions can be systematically designed and managed for system integration through service composition. The authors illustrate how the proposed SOC middleware, named FlowEngine, implements and manages these flows with contemporary Web services technologies. An experimental case study in an e-governmental environment further demonstrates how the methodology can facilitate the design of complex inter-organizational processes. Copyright © 2011, IGI Global.
Original languageEnglish
Pages (from-to)32-63
Number of pages32
JournalJournal of Database Management
Volume22
Issue number2
DOIs
Publication statusPublished - 1 Apr 2011
Externally publishedYes

Keywords

  • Cross-organizational process view
  • Decomposition methodology
  • E-government
  • Exceptions
  • Flows
  • Web services

ASJC Scopus subject areas

  • Software
  • Information Systems
  • Hardware and Architecture

Fingerprint

Dive into the research topics of 'Service composition and interaction in a SOC middleware supporting separation of concerns with flows and views'. Together they form a unique fingerprint.

Cite this