scholarly journals Onto2DB: towards an eclipse plugin for automated database design from an ontology

Author(s):  
Morad Hajji ◽  
Mohammed Qbadou ◽  
Khalifa Mansouri

Ontologies are spreading more and more in the field of information technologies as a privileged solution allowing the formalization of knowledge. The theoretical model of ontologies is most promising. They are increasingly ubiquitous given the benefits they present. Despite the proliferation of research proposing approaches dedicated to the design of a database from an ontology, the tools to design a database from an ontology are rare or inaccessible. Thus, in this contribution, we present our approach for the development of an Eclipse Plug-in, in order to automatically generate a conceptual model of a relational database from an ontology. To evaluate the usefulness of our approach, we used our resulting Eclipse Plug-in to automatically generate a conceptual model of a relational database from an ontology, customize it, and automatically generate the corresponding SQL script for Data Definition. The results of this experiment showed that our Plug-in constitutes a concretization of our approach and a means of automatic translation from the ontological model to the relational model.

10.28945/3199 ◽  
2008 ◽  
Author(s):  
Milos Bogdanovic ◽  
Aleksandar Stanimirovic ◽  
Nikola Davidovic ◽  
Leonid Stoimenov

Most universities where students study informational technologies and computer science have an introductory course dealing with the development and design of databases. These courses often include usage of database design tools. In this paper, the #EER tool is presented, the task of which is to make the process of relational databases design easier for the students and partially automatize it. The tool evolved due to the experience in using similar tools for educational purposes. It enables fast and efficient development of the relational database conceptual model and its automatized compilation into a relational model and further to data definition language (DDL) commands. #EER tool is based on the extended entity-relationship (EER) model for conceptual modeling of relational databases. Modular architecture of the tool, the development of which is based on the usage of the design patterns, along with the benefits that its usage brings, is also presented.


Author(s):  
Jean-Marc Petit ◽  
Mohand-Saïd Hacid

This chapter revisits conceptual database design and focuses on the so-called “logical database tuning”. We first recall fundamental differences between constructor-oriented models (like extended Entity-Relationship models) and attribute-oriented models (like the relational model). Then, we introduce an integrated algorithm for translating ER-like conceptual database schemas to relational database schemas. To consider the tuning of such logical databases, we highlight two extreme cases: null-free databases and efficient — though non redundant — databases. Finally, we point out how SQL workloads could be used a posteriori as a help for the designers and/or the database administrators to reach a compromise between these extreme cases. While a lot of papers and books have been devoted for many years to database design, we hope that this chapter will clarify the understanding of database designers when implementing their databases and database administrators when maintaining their databases.


2009 ◽  
pp. 2360-2383
Author(s):  
Guntis Barzdins ◽  
Janis Barzdins ◽  
Karlis Cerans

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.


Author(s):  
Guntis Barzdins

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.


Sign in / Sign up

Export Citation Format

Share Document