Entities rarely exist in isolation. A student enrolls in a course, an order contains products, an employee reports to another employee — each of these is a relationship, an association between entity types that the data model must capture. This topic examines how those associations are described precisely enough to become part of a database design.
Three ideas do most of the work here. Cardinality states how many instances of one entity may be associated with instances of another (one-to-one, one-to-many, many-to-many). Participation constraints state whether that association is mandatory (total) or optional (partial) for each side. Degree describes how many entity types take part in the relationship — most are binary, but ternary and recursive (self-referencing) relationships also appear, as when an employee supervises other employees. Getting these details right matters because they determine how the model is later translated into tables, keys, and foreign keys; a many-to-many relationship, for example, cannot be implemented directly and requires a bridge (associative) table.
As you watch the videos, pay attention to notation. Chen notation draws relationships as diamonds with labels, while Crow's Foot notation encodes cardinality and participation in the line endings themselves. Watch for how each notation shows "one" versus "many" and "optional" versus "mandatory," and try to restate each diagram in a plain English sentence — for example, "each order must be placed by exactly one customer, and a customer may place zero or more orders." If you can move between the sentence and the diagram in both directions, you understand the relationship.
An introductory walkthrough of building an ER diagram from the ground up, covering entities, attributes, and the cardinalities that connect them. Based on its description, it works through the basics of identifying what belongs in a diagram and how to read the connections between entity types.
Lucid Software produces the widely used Lucidchart diagramming tool, so the notation shown is conventional and clean, and this first part gives you the vocabulary of entities and cardinality that the rest of the topic builds on.
The follow-up tutorial moves into more advanced ERD concepts, specifically primary keys, foreign keys, and bridge tables. Its stated focus on bridge tables is directly relevant to many-to-many relationships, which cannot be implemented without an intermediate associative entity.
It connects relationship cardinality to its practical consequence in a design, showing why distinguishing one-to-many from many-to-many actually changes the structure of the resulting database.
A short, focused comparison of the two most common ER diagram notations: Chen notation, which uses diamonds and labeled connections, and Crow's Foot notation, which encodes cardinality in the symbols at the ends of relationship lines. Expect a side-by-side look at how the same model appears in each style.
Textbooks and tools use both notations interchangeably, so this brief video helps you read whichever one you encounter and understand how participation and cardinality are represented in each.
Together these videos support MO3 and MO4 most directly: the Lucid Software tutorials build from basic entities and cardinality toward keys and bridge tables, giving you the reasoning needed to interpret cardinality types and translate business requirements into a correctly drawn diagram. The notation comparison strengthens MO4 and MO5, since evaluating a drafted diagram for errors or missing constraints first requires fluency in reading the symbols that express cardinality and participation. The second Lucid video also touches MO1 by showing how a conceptual relationship becomes a logical structure of keys and tables, while the attribute discussion in the first video reinforces MO2.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.