entity-relationship model

(redirected from Entity-relationship)
Also found in: Acronyms.

entity-relationship model

(database, specification)
An approach to data modelling proposed by P. Chen in 1976. The model says that you divide your database in two logical parts, entities (e.g. "customer", "product") and relations ("buys", "pays for").

Entity-relationship diagrams can be used to represent a model.

["The entity-relationship model: toward a unified view of data", P.P. Chen, ACM Transactions on Database Systems 1:1 pp 9-36, 1976].
References in periodicals archive ?
26) Robert Maxwell has provided a much more detailed discussion, which treats diagramming methods for entity-relationship models, comparing Chen's system and those used in FRBR and FRAD, and then moves to a consideration of the FRBR entities, relationships, and user tasks, ending with a comparison between the FRBR model and catalogue records produced under AACR2.
Let us briefly review the key definitions of Entity-Relationship schemata following [18].
The entity-relationship model--toward a unified view of data.
Fidel & Crandall (1988) described the Anglo-American cataloguing rules from a generalized database approach, using the entity-relationship model to suggest a problem-based typology of rules that might underlie a theoretical framework of rules for bibliographic database design.
Chen: "The Entity-Relationship Model - Towards a Unified View of Data",ACM TODS Vol 1, No 1, March 1976.
This research investigated how the relationships can be implemented for more efficient urban land and building management using the entity-relationship model and relational database model.
The REA framework, first introduced by McCarthy in 1982, is based on accounting theory, including Sorter's (1969) work on events accounting, and on database theory, including Chen's (1976) work on entity-relationship databases.
Entity-relationship (E-R) design has a reputation as a useful but difficult to master tool for mapping clear database designs.
0, an entity-relationship diagramming tool; and oAzium Smart Card plug-in, which adds smart card technology to solutions built in FileMaker Pro (http://www.
Aqua Data Studio's popular Entity-Relationship Modeler has also been extended this time around, now with the ability to convert or translate an ER model from one database to another.
Specific topics include entity-relationship database modeling, user tasks, and a comparison of current cataloging practice with what it would look like if FRBR principles were used.