• DocumentCode
    2139915
  • Title

    SOI (Service Oriented Integration) and SIMM (Service Integration Maturity Model An Analysis

  • Author

    Sivakumar, Gandhi ; Abrahams, Faried ; Hogg, Kerard ; Hartley, John

  • Author_Institution
    IBM Australia, SA, Australia
  • fYear
    2010
  • fDate
    5-10 July 2010
  • Firstpage
    178
  • Lastpage
    182
  • Abstract
    The constellation of SOA entities encompasses a triplet of Service consumer/provider and an optional registry. In the normal style, the service provider (“Service”) is instantiated and the details are stored in a registry. Service consumers seeking the required service explore the registry, locate the Service end points, receive the service contracts (normally as WSDLs), comply with the established contracts in order to consume the service. While this is an ideal scenario, in integration based environments the style differs where integration enablers as services are required to be built to aid integration. Thus Service Oriented integration (SOI) would mean the following depending on the type of players in the IT industry: To an ISV (Independent Software Vendor) who develops products, SOI would mean exposing loosely coupled interfaces to be consumed easily by abstracting the implementation; To a systems integrator, this would mean creating and hosting integration enablers as services( most of the times in the middleware layer) to be consumed by applications which in turn might fulfill the intended functionality by interacting with one or more back end applications. SIMM (Service Integration Maturity Model) defines a maturity model of such SOI based environments. This maturity model in turn will serve as an index to measure the level of flexibility and agility of an industry´s IT Environment to the changing needs of the business which is the key goal of SOA. Though there are many factors affecting SIMM, standards and modularity play a key role. In this paper we intend to analyze SIMM characteristics, benefits of standards combined with modularity, different enterprise environments and suggest the relevance of standards in each environment. In section I, we briefly discuss the functionality of integration enablers and various patterns. In Section II, we discuss the SIMM characteristics combined with modularity, explore in detail the various types of en- - terprises and requirements to comply with standards to achieve greater SIMM and finally conclude.
  • Keywords
    Capability Maturity Model; Web services; software architecture; SIMM; SOA; SOI based environments; independent software vendor; industry IT environment; service consumer; service contracts; service end points; service integration maturity model; service oriented integration; service provider; Business; Data models; Industries; Mediation; Service oriented architecture; Standards; Service Integration Maturity Model; Service oriented Integration;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Services (SERVICES-1), 2010 6th World Congress on
  • Conference_Location
    Miami, FL
  • Print_ISBN
    978-1-4244-8199-6
  • Electronic_ISBN
    978-0-7695-4129-7
  • Type

    conf

  • DOI
    10.1109/SERVICES.2010.55
  • Filename
    5575818