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

2012 ◽  
Vol 7 (3) ◽  
pp. 14-36
Author(s):  
Sikha Bagui ◽  
Richard Sweetman
Keyword(s):  
Conceptual Framework ◽  
Relational Model ◽  
Service Oriented Architectures ◽  
Service Oriented ◽  
Er Model ◽  
Entity Relationship ◽  
Data Objects ◽  
Service Data

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.

scholarly journals In the Name of the Name: RDF literals, ER attributes and the potential to rethink the structures and visualizations of catalogs

2016 ◽  
Vol 35 (2) ◽  
pp. 19 ◽  
Author(s):  
Manolis Peponakis
Keyword(s):  
Semantic Web ◽  
Conceptual Framework ◽  
Cultural Meanings ◽  
New Approach ◽  
Descriptive Information ◽  
Bibliographic Data ◽  
Er Model ◽  
Description Framework ◽  
Entity Relationship ◽  
Resource Description

<p>The aim of this study is to contribute to the field of machine-processable bibliographic data that is suitable for the Semantic Web. We examine the Entity Relationship (ER) model, which has been selected by IFLA as a “conceptual framework” in order to model the FR family (FRBR, FRAD and RDA), and the problems ER causes as we move towards the Semantic Web. Subsequently, while maintaining the semantics of the aforementioned standards but rejecting the ER as a conceptual framework for bibliographic data, this paper builds on the Resource Description Framework (RDF) potential and documents how both the RDF and Linked Data’s rationale can affect the way we model bibliographic data.</p>In this way, a new approach to bibliographic data emerges where the distinction between description and authorities is obsolete. Instead, the integration of the authorities with descriptive information becomes fundamental so that a network of correlations can be established between the entities and the names by which the entities are known. Naming is a vital issue for human cultures because names are not random sequences of characters or sounds which stand just as identifiers for the entities - they also have socio-cultural meanings and interpretations. Thus, instead of describing indivisible resources, we could describe entities that appear in a variety of names on various resources. In this study, a method is proposed to connect the names with the entities they represent and, in this way, to document the provenance of these names by connecting specific resources with specific names.

The Objects Model and the Class Diagram

2011 ◽  
pp. 13-56
Author(s):  
Peretz Shoval
Keyword(s):  
Information Needs ◽  
Relational Model ◽  
Verbal Description ◽  
Database Schema ◽  
Class Diagram ◽  
Data Types ◽  
Data Definition ◽  
Er Model ◽  
Entity Relationship ◽  
Entity Relationship Diagram

The objects model (or object oriented [OO] model) is a conceptual-application model that is used to define a database schema representing a certain reality. The model views the world as consisting of objects belonging to classes. The objects of these classes have attributes, behavior (i.e., functions), and various relationships with other objects. The objects model can be presented as a class diagram (also termed OO diagram or objects diagram). Like an entity relationship diagram (ERD), the class diagram has two main goals: 1. To serve as a communication medium between the developers (analysts/ designers) and the users or their representatives. The diagram is created as a result of the interactions between the two parties, during which they discover and define the users’ information needs; the diagram serves like a contract between these two sides which summarizes the users’ needs. 2. To be the basis for further development of the information system (IS). Based on the diagram, it should be possible to design the database schema of the application, and (partially) the functions that it will have to perform. For that, it is necessary to transform the class diagram into an equivalent verbal description—an objects schema. This is done using an object definition language (ODL), similar to data definition language (DDL) in the relational model. In principle, all components of the class diagram are mapped to the objects schema. However, the objects schema includes more details which are not included in the diagram. For example, in the diagram each attribute has a name, and some attributes may have specific constraint definitions (e.g., key, unique); in the objects schema there are more detailed definitions, including the attributes’ domains or data types (e.g., numeric, char., real, etc.) and lengths. Another example, in the class diagram, we only write the names of the classes’ functions, while in the objects schema we specify the parameters of the functions. As aforementioned, there is a great deal of similarity between the OO and ER models and diagrams, since the ER model is one of the sources from which the objects model originated. But there are differences between the two models, which we will review later on. One of these differences is that the ER model is “static,” that is, it only deals with the data structure, while the objects model also includes “behavior,” that is, the functions that operate on the data. The rest of this chapter is dedicated to describing the components of the objects model and the class diagram. The description is organized in four main categories: objects and classes, attributes, relationships, and functions.

A Two Phases Self-healing Framework for Service-oriented Systems

2021 ◽  
Vol 15 (2) ◽  
pp. 1-25
Author(s):  
Amal Alhosban ◽  
Zaki Malik ◽  
Khayyam Hashmi ◽  
Brahim Medjahed ◽  
Hassan Al-Ababneh
Keyword(s):  
Web Services ◽  
A Priori ◽  
Fault Management ◽  
Service Selection ◽  
Exception Handling ◽  
Self Healing ◽  
Service Oriented Architectures ◽  
Service Oriented ◽  
Improved Performance ◽  
High Level

Service-Oriented Architectures (SOA) enable the automatic creation of business applications from independently developed and deployed Web services. As Web services are inherently a priori unknown, how to deliver reliable Web services compositions is a significant and challenging problem. Services involved in an SOA often do not operate under a single processing environment and need to communicate using different protocols over a network. Under such conditions, designing a fault management system that is both efficient and extensible is a challenging task. In this article, we propose SFSS, a self-healing framework for SOA fault management. SFSS is predicting, identifying, and solving faults in SOAs. In SFSS, we identified a set of high-level exception handling strategies based on the QoS performances of different component services and the preferences articled by the service consumers. Multiple recovery plans are generated and evaluated according to the performance of the selected component services, and then we execute the best recovery plan. We assess the overall user dependence (i.e., the service is independent of other services) using the generated plan and the available invocation information of the component services. Due to the experiment results, the given technique enhances the service selection quality by choosing the services that have the highest score and betters the overall system performance. The experiment results indicate the applicability of SFSS and show improved performance in comparison to similar approaches.

DESIGN OF DECOUPLED CLINICAL DECISION SUPPORT FOR SERVICE-ORIENTED ARCHITECTURES

2009 ◽  
Vol 19 (02) ◽  
pp. 159-183 ◽  
Author(s):  
JENS WEBER-JAHNKE
Keyword(s):  
Decision Support ◽  
Clinical Decision Support ◽  
Service Oriented Architecture ◽  
Empirical Evaluation ◽  
Cost Savings ◽  
Clinical Decision ◽  
Service Oriented Architectures ◽  
Distributed Services ◽  
Service Oriented ◽  
Computer Based

Computer-based clinical decision support (CDS) contributes to cost savings, increased patient safety and quality of medical care. Most existing CDS systems are stand-alone products (first generation) or part of complete electronic medical record packages (second generation). Experience shows that creating and maintaining CDS systems is expensive and requires effort that should be economized by sharing them among multiple users. It makes good economic sense to share CDS service installations among a larger set of client systems. The paradigm of a service-oriented architecture (SOA) embraces this idea of sharing distributed services. Some attempts making CDS services available to distributed health information systems exist. However, these approaches have not gained much adoption. We argue that they do not provide a sufficient level of decoupling between client and CDS in order to be broadly reusable in SOAs. In this paper, we present a new CDS service component called EGADSS, which has been designed and implemented with the declared objective to minimize the coupling between client and CDS server. We present our key design decisions, which are guided by empirical research in SOA development. We evaluate our result theoretically by measuring the level of decoupling achieved compared to existing CDS approaches. Furthermore, we report on an empirical evaluation of the resulting design, integrating the EGADSS service with an example client system.

Sign in / Sign up

Export Citation Format

Share Document