From semantic to object-oriented data modeling

Kilov, Haim

doi:10.1109/icsi.1990.138704

Cited by 29 publications

(7 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We view this model as a common denominator of many popular data models that we surveyed [8] [9] including mainly the relational and object-oriented modeling of databases. We adapt the CRUD (Create-Read-Update-Delete) [10] model to include functional descriptions of the basic data operations. We implement our model as a generic class to facilitate its understanding by programmers of Web services.…”

Section: Research Hypotheses and Validationmentioning

confidence: 99%

Specification and Verification of Data-Centric Web Services

Saleh

2010

2010 6th World Congress on Services

View full text Add to dashboard Cite

Data-centric Web services are services whose behavior is determined by their interactions with a repository of stored data. The lack of data specification in current Web service standards potentially leads to erroneous use of these services by their consumers. In this work, we propose using formal data contracts to decrease ambiguity about a service behavior, to fully verify a composition of services, and to guarantee data integrity within a composition of services.

show abstract

Section: Research Hypotheses and Validationmentioning

confidence: 99%

Specification and Verification of Data-Centric Web Services

Saleh

2010

2010 6th World Congress on Services

View full text Add to dashboard Cite

show abstract

“…Research has been devoted to extensive matching algorithms that exploit demographic information to correctly link records from different databases in the absence of an overall patient identification system. Concerning semantic modeling, the object-orientation of database schemas is seen as an important step towards semantic modeling [18][19][20]. Although several commercial object-oriented DBMSs are available nowadays, their performance is still considered to be inadequate for routine use.…”

Section: The Data Integration Layermentioning

confidence: 99%

Trends in Integrated Clinical Workstations

Mulligen¹,

Timmers²

1996

Yearb Med Inform

View full text Add to dashboard Cite

During the last decade, several projects aiming at integrated clinical workstations have been described and several prototypes have been demonstrated. In most of these projects, the clinical workstation accesses information and functionality provided by the present proprietary legacy systems of health-care institutions. We discuss trends in integrated clinical workstations from the viewpoints of software engineering and integration, considering that the clinical workstation itself basically consists of three layers: a presentation layer, a data integration layer, and a communication layer. The software engineering view on clinical workstations focuses on the development of basic building blocks from which clinical workstations, specific to a particular medical domain, can be composed. The integration view on clinical workstations addresses methods and techniques to deal with the, in general, intrinsically closed information systems in health-care institutions.

show abstract

“…Next, inspired by the Create, Read, Update and Delete (CRUD) taxonomy of database manipulations [9], we define the specialization of the two latest introduced concepts.…”

Section: Ontology Of Domain Actions (Oda)mentioning

confidence: 99%

Using domain ontologies in a dynamic analysis for program comprehension

Belmonte

Dugerdil

2010

Ontology-Driven Software Engineering

View full text Add to dashboard Cite

The use of domain knowledge for program comprehension has been advocated by many authors. However, as far as we know, most of the analysis techniques using domain knowledge are static, it seems that dynamic analyses have not yet taken full advantage of any domain knowledge. This might be a consequence of ontologies, the most common technique for domain knowledge representation, being static by nature. In this article we present a new kind of dynamic analysis that attempts to use domain knowledge from two ontologies: that of the domain concepts and another one we called the "Ontology of Domain Actions". To take advantage of this later source of knowledge, we had to specify what actions were expected to be performed by the software at any moment in time. This has been done using a variant of the CRC cards formalism. As a result, we are able to match the actions actually performed by the software with expectations using dynamic analysis based on the action ontology.

show abstract

From semantic to object-oriented data modeling

Cited by 29 publications

References 9 publications

Specification and Verification of Data-Centric Web Services

Specification and Verification of Data-Centric Web Services

Trends in Integrated Clinical Workstations

Using domain ontologies in a dynamic analysis for program comprehension

Contact Info

Product

Resources

About