It is built around the entity-relationship (E-R) model and this book presents a number of corresponding diagrams.
What does E-R stand for?
E-R stands for Entity-Relationship
This definition appears very frequently and is found in the following Acronym Finder categories:
- Science, medicine, engineering, etc.
Other Resources:
We have 64 other meanings of E-R in our Acronym Attic
- Abbreviation Database Surfer
- « Previous
- Next »
- Estimate Pilot-Only Receiver
- Electronic Provincial Offence Notices
- Enterprise Point of Presence (network platform)
- Electronic People (UK)
- Esophoria at Near (read 'e-prime' or E')
- Electronically Programmable Read-Only Memory
- Enhanced Physical Uplink Channel (computer networking)
- Electronic Questionnaire for Investigations Processing (US OPM)
- Electronic Questionnaires for Investigations Processing (US OPM)
- Electronic Questionnaire for Investigation Processing (US FEMA)
- Enhanced Radio Access Bearer
- Extended-Range Electric Vehicle
- Erythrocyte Rosette Forming Cell
- E-Research for Marketing
- E-DCH (Enhanced Dedicated Channel) Random-Access Uplink Control Channel (computer networking)
- Electronic Student Academic Portfolio
- Electronic School on Aquatic Resources Management
- Electronic Scanning
- Electronic Selected Current Aerospace Notices
- Electronically Scanned Antennas
Samples in periodicals archive:
Entity-Relationship Diagram An Entity-Relationship diagram, commonly referred to as an E-R diagram, shows the main things (or entities) that have a collection of related data elements (fields) we want to store and the relationships between these entities.
In Section 2 we first present an algebra for higher-order Entity-Relationship schemata [18], which permits the representation of very large schemata as algebraic expressions involving smaller and thus easier tractable schemata.
Maxwell begins by describing the entity-relationship model, which is the basis for FRBR.
The entity-relationship method is a method of conceptual and logical data modeling (Pavlic, 1996).
This is illustrated with an entity-relationship model, one of the two principal approaches used in this book.
The presentation will highlight the best practices for architecting XML Schemas that have their roots in proven object-oriented analysis, entity-relationship, and database design principles.
The entity-relationship diagrams have been converted to today's standard practice format that is compatible with MS Visio, among other software tools.