entity-relationship model

(redirected from ER diagram)

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 ?
According to this ER diagram, tables are created for the following entities (Longley et al.
To its credit, this ER diagram portrays the domain in a way that is independent of the target software platform.
Conversion of the ER diagram to a star schema is a step-by-step process and usually begins with a conversation between end users and IT professionals to discover a list of burning questions.
The ER diagram is constructed using the workspace integrated into KERMIT's interface.
Build data tables (relations) from the ER diagram constructed in steps 1 to 5.
The function tree and ER diagram are then correlated by means of an entity-function table that shows the use that each business process makes of business data.
For example, the schema of the personnel database may be initially described using the entity-relationship data model in the form of an ER diagram.
For example, as soon as the database requirement specification is available, an ER diagram for the target database could be easily developed.
The practice of systems analysis was characterized 10 years ago by a mixed bag of isolated modeling techniques (data flow diagrams, ER diagrams, state transition diagrams) that were used to capture the rich information that needs to be modeled, analyzed and understood before a software system is actually built.