A methodological approach for object-relational database design using UML

Marcos, Esperanza; Vela, Belén; Cavero, José María Martínez de Pisón

doi:10.1007/s00450-004-0158-4

Cited by 18 publications

(26 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Mapping conceptual schemas to relational databases is a well-studied field of research [19]. A few works also cover schemas that include (OCL) constraints.…”

Section: Related Workmentioning

confidence: 99%

UMLtoGraphDB: Mapping Conceptual Schemas to Graph Databases

Daniel

Sunyé

Cabot

2016

Conceptual Modeling

View full text Add to dashboard Cite

Abstract. The need to store and manipulate large volume of (unstructured) data has led to the development of several NoSQL databases for better scalability. Graph databases are a particular kind of NoSQL databases that have proven their efficiency to store and query highly interconnected data, and have become a promising solution for multiple applications. While the mapping of conceptual schemas to relational databases is a well-studied field of research, there are only few solutions that target conceptual modeling for NoSQL databases and even less focusing on graph databases. This is specially true when dealing with the mapping of business rules and constraints in the conceptual schema. In this article we describe a mapping from UML/OCL conceptual schemas to Blueprints, an abstraction layer on top of a variety of graph databases, and Gremlin, a graph traversal language, via an intermediate Graph metamodel. Tool support is fully available.

show abstract

“…Mapping conceptual schemas to relational databases is a well-studied field of research [19]. A few works also cover schemas that include (OCL) constraints.…”

Section: Related Workmentioning

confidence: 99%

UMLtoGraphDB: Mapping Conceptual Schemas to Graph Databases

Daniel

Sunyé

Cabot

2016

Conceptual Modeling

View full text Add to dashboard Cite

show abstract

“…Design-based proposals: Some works that have design characteristics can be used for DBRE [28,33]. A method based on a generic schema specification model and DBRE techniques has been proposed to deal with design and reengineering database applications [28].…”

Section: Database Reverse Engineering (Dbre)mentioning

confidence: 99%

“…A method based on a generic schema specification model and DBRE techniques has been proposed to deal with design and reengineering database applications [28]. Marcos et al presented rules to translate a UML class diagram into an ORDB schema in SQL3 and Oracle 8i [33].…”

Section: Database Reverse Engineering (Dbre)mentioning

confidence: 99%

Re-engineering relational databases

Maatuk

Ali

Rossiter

2011

Proceedings of the 2011 International Conference on Intelligent Semantic Web-Services and Applications

View full text Add to dashboard Cite

This paper surveys the recent literature about various research trends relevant to Relational DataBase (RDB) reengineering. The paper presents an analysis of approaches and techniques used in this context, including construction of object views on top of RDBs, database integration and database migration. A categorisation is presented of the selected work, concentrating on migrating an RDB as a source into object-based and XML databases as targets. Database migration from the source into each of the targets is discussed and critically evaluated, including the semantic enrichment, schema translation and data conversion. Based on a detailed analysis of the existing literature, it seems that the existing work does not provide a complete solution for more than one target database for either schema or data conversion. Besides, none of the existing proposals can be considered as a method for migrating an RDB into an objectrelational database. We propose such a method based on an intermediate canonical data model, which enriches the semantics of the source RDB and captures characteristics of the target databases.

show abstract

“…Several methodologies (e.g. [14]- [16]) have been proposed for relational database modeling with UML. In general, they extend UML with non-standard stereotypes to model to the various ER diagram components, thus providing a similar expressive power and suffering from the same criticisms, such as difficulty to express the business rules and ease of inserting non-syntactic errors.…”

Section: Related Workmentioning

confidence: 99%

Mapping between Alloy Specifications and Database Implementations

Cunha

Pacheco

2009

2009 Seventh IEEE International Conference on Software Engineering and Formal Methods

View full text Add to dashboard Cite

Abstract-The emergence of lightweight formal methods tools such as Alloy improves the software design process, by encouraging developers to model and verify their systems before engaging in hideous implementation details. However, an abstract Alloy specification is far from an actual implementation, and manually refining the former into the latter is unfortunately a non-trivial task. This paper identifies a subset of the Alloy language that is equivalent to a relational database schema with the most conventional integrity constraints, namely functional and inclusion dependencies. This semantic correspondence enables both the automatic translation of Alloy specifications into relational database schemas and the reengineering of legacy databases into Alloy. The paper also discusses how to derive an object-oriented application layer to serve as interface to the underlying database.

show abstract

A methodological approach for object-relational database design using UML

Cited by 18 publications

References 6 publications

UMLtoGraphDB: Mapping Conceptual Schemas to Graph Databases

UMLtoGraphDB: Mapping Conceptual Schemas to Graph Databases

Re-engineering relational databases

Mapping between Alloy Specifications and Database Implementations

Contact Info

Product

Resources

About