Nature of Computation and Communication. Second International Conference, ICTCC 2016, Rach Gia, Vietnam, March 17-18, 2016, Revised Selected Papers

Research Article

Architectural Pattern for Inter-Organizational Middleware Systems

Download
199 downloads
  • @INPROCEEDINGS{10.1007/978-3-319-46909-6_35,
        author={Radhouane Jrad and David Sundaram},
        title={Architectural Pattern for Inter-Organizational Middleware Systems},
        proceedings={Nature of Computation and Communication. Second International Conference, ICTCC 2016, Rach Gia, Vietnam, March 17-18, 2016, Revised Selected Papers},
        proceedings_a={ICTCC},
        year={2017},
        month={1},
        keywords={MAPIS IOMS IOIS IOS Framework EA SOA EDA Adaptive Middleware Architecture Pattern IADR Action Research Design Science},
        doi={10.1007/978-3-319-46909-6_35}
    }
    
  • Radhouane Jrad
    David Sundaram
    Year: 2017
    Architectural Pattern for Inter-Organizational Middleware Systems
    ICTCC
    Springer
    DOI: 10.1007/978-3-319-46909-6_35
Radhouane Jrad1,*, David Sundaram2,*
  • 1: OJI Fibre Solutions
  • 2: University of Auckland
*Contact email: Rad.Jrad@OJIFS.co.nz, D.Sundaram@Auckland.ac.nz

Abstract

Effective Business-to-Business (B2B) relationships typically rely on seamless integration of partner’s processes. Inter-Organizational Information Systems (IOIS) have largely been endorsed as B2B enablers. They are defined as automated Information Systems crossing organizational frontiers and aiming to synergize partners’ efforts in increasing competitiveness and cost management (Eom 2005). The components in IOIS responsible for the actual bridging between partners’ heterogonous systems are referred to as Inter-Organizational Middleware Systems (IOMS). While IOMS critically hold business information, they lack both research and standardization. Instead, chaotic and costly efforts to architect and manage IOMS have dominated the market. As a remedy, we propose an IOMS-specific architectural pattern that could be used to develop its architecture(s). First, the notions of frameworks and architectures are presented. Then, approaches to IOIS architecture and process management are discussed, before IOMS’s need for its specific architectures is presented. The MAPIS architectural design is then proposed and its merits and limitations are discussed.