On the satisfiability of dependency constraints in entity-relationship schemata
Information Systems
Object-oriented analysis and design with applications (2nd ed.)
Object-oriented analysis and design with applications (2nd ed.)
Conceptual design of object-oriented database schemas using the binary-relationship model
Data & Knowledge Engineering
Entity-relationship and object-oriented data modeling—an experimental comparison of design quality
Data & Knowledge Engineering
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Patterns of self-stabilization in database consistency maintenance
Data & Knowledge Engineering - Special issue: next generation information technologies and systems
Description logics for conceptual data modeling
Logics for databases and information systems
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Enhancing the ER model with integrity methods
Journal of Database Management - Special issue on information modeling methods
Fundamentals of Database Systems
Fundamentals of Database Systems
Modeling Spatial and Temporal Set-Based Constraints During Conceptual Database Design
Information Systems Research
Hi-index | 0.00 |
Entity-Relationship (ER) schemas include cardinality constraints that restrict the dependencies among entities within a relationship type. The cardinality constraints have direct impact on application transactions, since insertions or deletions of entities or relationships might affect related entities. Application transactions can be strengthened to preserve the consistency of a database with respect to the cardinality constraints in a schema. Yet, once an ER schema is translated into a logical database schema, the direct correlation between the cardinality constraints and application transaction is lost, since the components of the ER schema might be decomposed among those of the logical database schema.We suggest extending the Enhanced-ER (EER) data model with integrity methods that can enforce the cardinality constraints. The integrity methods can be fully defined by the cardinality constraints, using a small number of primitive update methods, and are automatically created for a given EER diagram. A translation of an EER schema into a logical database schema can create integrity routines by translating the primitive update methods alone. These integrity routines may be implemented as database procedures, if a relational DBMS is utilized, or as class methods, if an object-oriented DBMS is utilized.