The Entity Relationship Model — Toward a Unified View of Data
Published 1 January 2002
Peter Pin-Shan Chen
Citations5,769
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
A data model, called the entity-relationship model, is proposed that incorporates some of the important semantic information about the real world and can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model.
Abstract
A data model, called the entity-relationship model, is proposed. This model incorporates some of the important semantic information about the real world. A special diagrammatic technique is introduced as a tool for database design. An example of database design and description using the model and the diagrammatic technique is given. Some implications for data integrity, information retrieval, and data manipulation are discussed.
Keywords
Computer ScienceDecision Sciences
Communications of the ACMA relational model of data for large shared data banks
5,238 Citations1970E. F. Codd
A model based on n-ary relations, a normal form for data base relations, and the concept of a universal data sublanguage are introduced and certain operations on relations are discussed and applied to the problems of redundancy and consistency in the user's model.
A Relational Model of Data for Large Shared Data Banks
1,177 Citations2002E. F. Codd
SEQUEL
576 Citations1976Donald D. Chamberlin, Raymond F. Boyce
The data manipulation facility for a structured English query language (SEQUEL) which can be used for accessing data in an integrated relational data base.
Implementation of integrity constraints and views by query modification
435 Citations1975Michael Stonebraker
The mechanism being implemented in one relational system to prevent integrity violations which can result from improper updates by a process is indicated.
A data base sublanguage founded on the relational calculus
372 Citations1971E. F. Codd
Three principal types of language for data base manipulation are identified: the low-level, procedure-oriented, intermediate level, algebraic, and the high level, relational calculus-based data sublanguage, an example of which is described in this paper.
ACM SIGMIS Database the DATABASE for Advances in Information SystemsData structure diagrams
199 Citations1969Charles W. Bachman
The invention of algebra, essentially a graphic technique for communicating truths with respect to classes of arithmetic statements, broke the bond that slowed the development of mathematics.
Normalized data base structure
172 Citations1971E. F. Codd
This paper illustrates the removal of repeating groups, hierarchic and plex structures, and cross-referencing structures and the simplification of data base relations by normalization is discussed.
IBM Systems JournalData structures and accessing in data-base systems, I: Evolution of information systems
171 Citations1973Michael E. Senko, Eitan Altman +2 more
In this paper, aspects of information systems that are of importance to systems analysts, systems designers, and implementors are emphasized.
On the semantics of the relational data model
144 Citations1975Hans Albrecht Schmid, J. R. Swenson
A data model is discussed that takes into account basic semantic properties that object types and relationships among them apparently have in the real world, and permits us to analyze the ideas behind the relational theory more precisely, in particular the meaning of functional dependency and normalization.
Semantic integrity in a relational data base system
141 Citations1975Michael Hammer, Dennis McLeod
High-level nonprocedural languages to facilitate the expression of two types of semantic integrity information that are important in the context of a relational data base system are introduced and examples are presented.
Another look at data
126 Citations1967George H. Mealy
This paper sketches a theory of data which may serve to clarify questions about data, based on a number of old ideas which may, as a result, seem obvious.
Using semantic networks for data base management
85 Citations1975N. Roussopoulos, John Mylopoulos
This paper presents a semantic model of data bases that assumes the availability of a semantic network storing knowledge about a data base and a set of attributes for the data base.
Implementation of integrity constraints and views by query modification
47 Citations1975Michael Stonebraker
Communications of the ACMA large semaphore based operating system
25 Citations1975Søren Lauesen
The design principle is an alternative to Dijkstra's hierarchical structuring of operating systems and is proved to be free of “deadly embrace” (deadlock).
Data base standardization
23 Citations1975Thomas B. Steel
An important by-product of the work of the Study Group on Data Base Management Systems in the United States has been the development of a set of requirements for effective data base management systems.
Trends in database management
19 Citations1975Charles W. Bachman
It appears to this author that a major step in the evolution of computerized information systems has been accomplished and Integrated database systems are here to stay.
IFIP CongressCurrent and Future Trends in Data Base Management Systems.
16 Citations1974T. William Olle
An energy-efficient, high throughput stereo-matching solution capable of real-time stereo matching for temporal statistical pattern projector systems that was developed using a high-level synthesis approach, matching cost simplification, and FPGA-specific design optimizations.
An Extensible Semantic Model of Data Base and Its Data language.
10 Citations1974Jean-Luc Hainaut, Baudouin Le Charlier
ACM SIGMOD RecordAnother look at data-bases
9 Citations1974Naftaly H. Minsky
In an attempt to clarify the concept of database, the definition is an oversimplification, as any definition of such a fuzzy concept must be; it will emphasize certain characteristics of databases, at the expense of other, equally important, properties.