Extracting entity-relationship schemas from relational databases: a form-driven approach

2002 ◽  
Author(s):  
N. Mfourga
Keyword(s):  
Relational Databases ◽  
Entity Relationship ◽  
Relationship Schemas

Object-Relational Modeling

2009 ◽  
pp. 162-170
Author(s):  
Jaroslav Zendulka
Keyword(s):  
Relational Database ◽  
Relational Databases ◽  
Conceptual Modeling ◽  
Object Oriented ◽  
Database Systems ◽  
Object Relational ◽  
The Difference ◽  
Object Oriented Approach ◽  
Entity Relationship ◽  
Oriented Approach

Modeling techniques play an important role in the development of database applications. Well-known entity-relationship modeling and its extensions have become a widely-accepted approach for relational database conceptual design. An object-oriented approach has brought a new view of conceptual modeling. A class as a fundamental concept of the object-oriented approach encapsulates both data and behavior, whereas traditional relational databases are able to store only data. In the early 1990s, the difference between the relational and object-oriented (OO) technologies, which were, and are still used together to build complex software systems, was labeled the object-relational impedance mismatch (Ambler, 2003). The object-oriented approach and the need of new application areas to store complex data have greatly influenced database technology since that time. Besides appearance of object-oriented database systems, which fully implement objectoriented paradigm in a database environment (Catell et al., 2003), traditional relational database management systems become object-relational (Stonebraker & Brown, 1999). The most recent versions of the SQL standard, SQL: 1999 (Melton & Simon (2001) and SQL: 2003 (Eisenberg et al., 2004), introduced object-relational features to the standard and leading database producers have already released packages which incorporate them.

scholarly journals Supervised Models for Measuring Performance At E-Learning Environmen

2019 ◽  
Vol 8 (11) ◽  
pp. 2792-2797
Keyword(s):  
Big Data ◽  
Student Performance ◽  
Relational Databases ◽  
Prediction Models ◽  
Data Modeling ◽  
Process Data ◽  
Design Data ◽  
Relationship Model ◽  
E Learning ◽  
Entity Relationship

E-learning data becomes ‘Big’ data as it describes a huge volume of both structured and unstructured data. And inherent limitations of relational databases maintained in this context makes difficult to apply and to extract outputs meaningful. Data modeling is also recommended to design data views at various levels either conceptual or physical here. Most of the educational organizations are keen in collecting, storing and analyzing the students’ data because it will add more significant value to the decision making process. Data modeling through entity relationship model or query views plays a important role in dealing with big data due to the fact around 85% of big data is semi structured data. Hence data modeling should be carried out as required by any learning institution needs. Making big data component to reside in the data model is challenging. This paper is to establish data modeling techniques applied to a reasonably ‘big’ data in e-learning. Prediction models generated from this data will be accurate if the training sets and testing sets are governed properly in spite of data size complexity. Student Performance by study credits (partitioned in three classes: low, medium, high ) are classified with respect to their engagement attributes (activity types, sum of clicks made, duration in days) and obtained maximum accuracy 90.923%.

Conceptual Modeling for XML

2011 ◽  
pp. 148-173
Author(s):  
Sriram Mohan ◽  
Arijit Sengupta
Keyword(s):  
Conceptual Design ◽  
Relational Databases ◽  
Conceptual Modeling ◽  
Future Trend ◽  
Major Influence ◽  
Design Phase ◽  
Application Development ◽  
Current Application ◽  
Development Processes ◽  
Entity Relationship

The process of conceptual design is independent of the final platform and the medium of implementation, and is usually in a form that is understandable and usable by managers and other personnel who may not be familiar with the low-level implementation details, but have a major influence in the development process. Although a strong design phase is involved in most current application development processes (e.g., Entity Relationship design for relational databases), conceptual design for XML has not been explored significantly in literature or in practice. Most XML design processes start by directly marking up data in XML, and the metadata is typically designed at the time of encoding the documents. In this chapter, the reader is introduced to existing methodologies for modeling XML. A discussion is then presented comparing and contrasting their capabilities and deficiencies, and delineating the future trend in conceptual design for XML applications.

Conceptual Modeling for XML

2009 ◽  
pp. 527-549
Author(s):  
Sriram Mohan ◽  
Arijit Sengupta
Keyword(s):  
Conceptual Design ◽  
Relational Databases ◽  
Conceptual Modeling ◽  
Future Trend ◽  
Major Influence ◽  
Design Phase ◽  
Application Development ◽  
Current Application ◽  
Development Processes ◽  
Entity Relationship

The process of conceptual design is independent of the final platform and the medium of implementation, and is usually in a form that is understandable and usable by managers and other personnel who may not be familiar with the low-level implementation details, but have a major influence in the development process. Although a strong design phase is involved in most current application development processes (e.g., Entity Relationship design for relational databases), conceptual design for XML has not been explored significantly in literature or in practice. Most XML design processes start by directly marking up data in XML, and the metadata is typically designed at the time of encoding the documents. In this chapter, the reader is introduced to existing methodologies for modeling XML. A discussion is then presented comparing and contrasting their capabilities and deficiencies, and delineating the future trend in conceptual design for XML applications.

Business Rules in Databases

2005 ◽  
pp. 47-53
Author(s):  
Antonio Badia
Keyword(s):  
Information Systems ◽  
Relational Databases ◽  
Database Systems ◽  
Business Rules ◽  
Business Rule ◽  
The Subject ◽  
Entity Relationship ◽  
Definition Of ◽  
Definition Of Information ◽  
Exact Definition

Though informal, the concept of business rule is very important to the modeling and definition of information systems. Business rules are used to express many different aspects of the representation, manipulation and processing of data (Paton, 1999). However, perhaps due to its informal nature, business rules have been the subject of a limited body of research in academia. There is little agreement on the exact definition of business rule, on how to capture business rules in requirements specification (the most common conceptual models, entity-relationship and UML, have no proviso for capturing business rules), and, if captured at all, on how to express rules in database systems. Usually, business rules are implemented as triggers in relational databases. However, the concept of business rule is more versatile and may require the use of other tools.

Transforming UML Class Diagrams into Relational Data Models

2011 ◽  
pp. 217-236 ◽  
Author(s):  
Devang Shah ◽  
Sandra Slaughter
Keyword(s):  
Relational Databases ◽  
Unified Modeling Language ◽  
Systems Design ◽  
Object Oriented ◽  
Relational Data ◽  
Unified Modeling ◽  
Software Designers ◽  
Mapping Process ◽  
Uml Class Diagram ◽  
Entity Relationship

The Entity-Relationship (ER) method is the most popular method for relational database design. On the other hand, the Unified Modeling Language (UML) is widely used in object- oriented analysis and design. Despite the increasing use of object-oriented techniques for software design and development, there is a large installed base of relational databases. Additionally, object-oriented databases are still not in widespread use. Thus, software designers and developers often turn to the relational databases to make their application objects persistent. Considering the fundamental differences between the two methods, the transformation from UML to a relational data model could be a non-trivial task. The purpose of this chapter is to describe a process that can be used to map a UML class diagram into an ER diagram, and to discuss the potential of using the UML notation to draw ER diagrams. An example of an actual systems design is used throughout to illustrate the mapping process, the associated problems encountered, and how they could be resolved.

Sign in / Sign up

Export Citation Format

Share Document