scholarly journals Using the REA Data Model in Order to Reduce Design Complexity in an Inventory Management Relational Database, and the Need for a Relational Database Complexity Metric.

2021 ◽  
Vol 9 (7) ◽  
pp. 71-78
Author(s):  
Ian Adamson

With the extensive use of relational databases in the business environment there is a need to reduce database complexity in order to avoid data inconsistency and redundancy, which can provide a company with unreliable and/or meaningless data and information. The use of the REA Data Model in database design can significantly help with this problem.  The model can eliminate the need for unnecessary data artifacts which should only be generated by the system when needed. This paper also addresses the need for a Relational Database Complexity Metric. A simple and easy to understand metric is presented.

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.


1995 ◽  
Vol 11 (1) ◽  
Author(s):  
Edward Gould

<span>The teaching of relational database design to business students poses many problems. This paper looks at these problems and outlines an integrated approach which addresses the piecemeal and disjointed procedures common in many textbooks. A number of strategies for dealing with other problem areas of the topic are also described from the perspective of the prevailing business environment.</span>


2019 ◽  
pp. 453-460
Author(s):  
Vitalii I. Yesin ◽  
Mikolaj Karpinski ◽  
Maryna V. Yesina ◽  
Vladyslav V. Vilihura

The goal of the article is to develop a universal (standard) data model that allows you to get rid of the need for a costly policy of doing extra work when developing new ones or transforming existing relational databases (RDBs) caused by dynamic changes in the subject domain (SD). The requirements for the developed data model were formulated. In accordance with the formulated requirements, the data model was synthesized. To simplify the process of creating relational database schemas an algorithm for transforming the description of the subject domain into the relations of the universal basis of the developed model was proposed. The scientific novelty of the obtained results is: a data model that, unlike known ones, allows us to simplify the creation of RDB schemas at the stage of logical design of relational databases, under the conditions of dynamic changes in subject domains, due to the introduced universal basis of relations, as a means of describing structures and the presentation of data for various SDs has been developed.


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):  
Sapiahon Khaidarova ◽  

The article outlines the methods for creating SQL queries in relational databases. The use of the structured query language SQL in relational databases is substantiated. It provides information about the SQL standard and the three-tier database organization system. The author describes the choice of a data model based on the conceptual level using to that end an example of the Kokand Pedagogical Institute as the relational database model. A relational conceptual diagram of the information model of a pedagogical institute is compiled. Such a conceptual diagram is depicted using a cluster. Objects of the subject area are depicted in the form of tables, which differ from each other in geometric shapes or colors. The relationships between tables in Microsoft Access are presented. The basic rules for creating and filling tables in SQL using the instructions CREATE TABLE and INSERT INTO are considered. The syntax of the SELECT statement is given. All offers of the SELECT statement and their order are listed. Examples are given for compiling simple queries and subqueries in SQL using the SELECT statement for the database of the Kokand Pedagogical Institute. Information about the order of execution of internal and external requests is given. The article considers the ORDER BY offer of a SELECT statement for sorting query results.


The chapter presents how relational databases answer to typical NoSQL features, and, vice versa, how NoSQL databases answer to typical relational features. Open issues related to the integration of relational and NoSQL databases, as well as next database generation features are discussed. The big relational database vendors have continuously worked to incorporate NoSQL features into their databases, as well as NoSQL vendors are trying to make their products more like relational databases. The convergence of these two groups of databases has been a driving force in the evolution of database market, in establishing a new level of focus to resolving big data requirements, and in enabling users to fully use data potential, wherever data is stored, in relational or NoSQL databases. In turn, the database of choice in the future will likely be one that provides the best of both worlds: flexible data model, high availability, and enterprise reliability.


Author(s):  
Mirella M. Moro ◽  
Lipyeow Lim ◽  
Yuan-Chi Chang

It is well known that XML has been widely adopted for its flexible and self-describing nature. However, relational data will continue to co-exist with XML for several different reasons one of which is the high cost of transferring everything to XML. In this context, data designers face the problem of modeling both relational and XML data within an integrated environment. This chapter highlights important questions on hybrid XML-relational database design and discusses use cases, requirements, and deficiencies in existing design methodologies especially in the light of data and schema evolution. The authors’ analysis results in several design guidelines and a series of challenges to be addressed by future research.


Sign in / Sign up

Export Citation Format

Share Document