Modeling Service Data Objects (SDOs) to the Entity-Relationship (ER) Model

Modeling Service Data Objects (SDOs) to the Entity-Relationship (ER) Model

Sikha Bagui (University of West Florida, USA) and Richard Sweetman (University of West Florida, USA)
DOI: 10.4018/jitwe.2012070102


In this paper the authors present a conceptual framework for translating Service Data Objects (SDOs) and XML’s SDOs to the Entity Relational (ER) Model. With the increasing dependence on service oriented architectures and the increasing need for SDOs in service oriented architectures (SOA), it is important to have a good understanding of SDOs in terms of the ER model so that SDOs can be easily converted to the relational model. In this paper they show how common SDO constructs and XML’s SDO constructs conceptually map to the ER model.
Article Preview

1. Introduction

One of the major challenges facing businesses today is the need to respond quickly and efficiently in this global marketplace. To support flexible business collaboration, modern distributed applications are becoming component based and the concept of a service is becoming crucial. Recent years have witnessed a paradigm shift in distributed computing from middleware-oriented architectures (Baresi et al., 2003) and legacy systems (Li et al., 2007) to Web Services and Service Oriented Architectures (SOA) (Bouguettaya et al., 2006; Chen et al., 2006; Kim et al., 2007).

SOA provides fast, effective, inexpensive business process integration (Dan et al., 2007; Zimmerman et al., 2004), asset reuse and improved business agility (Anand et al., 2005; Chen & Huang, 2006; Gold et al., 2004; Malloy et al., 2006). SOA can be considered an architectural framework that supports integrating business tasks as linked services that can be accessed when needed (Chen & Huang, 2006). In an ideal SOA world, everything (Imen et al., 2007), including information (Dan et al., 2007), would be a service and all components and services would be loosely coupled, making SOA highly dynamic and flexible. All functions would be services (Chen & Huang, 2006), and services would be the building blocks of systems. Services would have well-defined interfaces allowing consumers to know how to interact with them without having knowledge of the underlying platform (Erl, 2005). Services could be grouped together to form complex integrated processes and applications. Additions or modifications to the applications would be by adding/modifying services, independent of the application. Services could be added or removed dynamically at runtime (Baresi et al., 2003; Cotroneo et al., 2004). SOA will provide the basis for the next generation of distributed software systems (Mukhi et al., 2004).

SOA has three parts: service providers, service requestors and service registry (Baresi et al., 2003; Champion et al., 2002; Mukhi et al., 2004; Nielsen et al., 2006). Service providers are the owners that offer a service. They provide machine readable descriptions of their services and publish them in a publicly available registry (Baresi et al., 2003; Champion et al., 2002; Mukhi et al., 2004), which the service requestors can access when looking for services. Services and components interact by exchanging messages. And, one of the most important components of any service is the data.

SOA inherently deals with different kinds of data from heterogeneous data sources. One of the major challenges facing SOA in the last few years has been the need for an efficient data integration mechanism (Chen et al., 2006; Chen & Huang, 2006; Mukhi, 2004; Zhang et al., 2004) to efficiently handle data. Data relevant to today’s enterprise applications lives in a variety of information sources – relational databases, packaged applications and various home grown applications, and external Web Services (Borkar et al., 2006; Carey et al., 2003). In this paper our aim is to look at how data can be handled in the SOA environment with respect to service data objects (SDOs).

Complete Article List

Search this Journal:
Open Access Articles: Forthcoming
Volume 14: 4 Issues (2019): 2 Released, 2 Forthcoming
Volume 13: 4 Issues (2018)
Volume 12: 4 Issues (2017)
Volume 11: 4 Issues (2016)
Volume 10: 4 Issues (2015)
Volume 9: 4 Issues (2014)
Volume 8: 4 Issues (2013)
Volume 7: 4 Issues (2012)
Volume 6: 4 Issues (2011)
Volume 5: 4 Issues (2010)
Volume 4: 4 Issues (2009)
Volume 3: 4 Issues (2008)
Volume 2: 4 Issues (2007)
Volume 1: 4 Issues (2006)
View Complete Journal Contents Listing