Entity-Relationship (ER) Modeling Methodology

An Entity-Relationship (ER) Modeling Methodology is a software modeling methodology that emphasizes the relationships between different entities in a domain.

• Context:
  • It can be referenced by an ER Diagram.
  • …
• See: OO Modeling, Domain Driven Design.

---

---

References

2023

• chat
  • Q: what is an Entity-Relationship (ER) software Modeling Methodology?
  • A: Entity-Relationship (ER) modeling software is a tool that is used to create and manipulate Entity-Relationship diagrams. These diagrams are used to represent the relationships between entities in a database or information system.

    ER modeling software typically allows you to create a diagram by dragging and dropping shapes that represent entities and relationships onto a canvas. You can then label the entities and relationships and add attributes to the entities. The software may also allow you to edit the diagram by adding or deleting entities and relationships, as well as modifying attributes.

    Some ER modeling software may also include features such as automatic layout, which arranges the shapes in the diagram in a logical and visually appealing way. Some software may also allow you to generate SQL code or other types of database schema from the diagram.

    ER modeling software can be useful for database designers, information systems analysts, and other professionals who need to design and document database systems. It can help to clarify the structure and relationships of the data, and to communicate those design decisions to others.

2021

• (Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/Entity–relationship_model Retrieved:2021-11-11.
  • An entity–relationship model (or ER model) describes interrelated things of interest in a specific domain of knowledge. A basic ER model is composed of entity types (which classify the things of interest) and specifies relationships that can exist between entities (instances of those entity types).

    In software engineering, an ER model is commonly formed to represent things a business needs to remember in order to perform business processes. Consequently, the ER model becomes an abstract data model, that defines a data or information structure which can be implemented in a database, typically a relational database.

    Entity–relationship modeling was developed for database and design by Peter Chen and published in a 1976 paper, with variants of the idea existing previously. Some ER models show super and subtype entities connected by generalization-specialization relationships, and an ER model can be used also in the specification of domain-specific ontologies.

2005

• (Brandon, 2005) ⇒ Daniel Brandon. (2005). “Recursive Database Structures.” In: Journal of Computing Sciences in Colleges, 21(2).
  • QUOTE: Recursive database structures, like binary relations, can appear in three ways as shown in the E-R diagrams of Figure 1.

1976

• (Chen, 1976) ⇒ Peter Pin-Shan Chen. (1976). “The Entity-relationship Model—toward a Unified View of Data.” In: ACM Transactions on Database Systems (TODS) Journal, 1(1). doi:10.1145/320434.320440
  • QUOTE: 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.

    The entity-relationship model can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model. Semantic ambiguities in these models are analyzed. Possible ways to derive their views of data from the entity-relationship model are presented.

---