ER Diagram Symbols: Crow's Foot, Chen and Cardinality

November 11, 2026 · 12 min read

ER Diagram Symbols: Crow's Foot, Chen Notation and Cardinality

ER diagram symbols come in two main families. Chen notation draws entities as rectangles, relationships as diamonds and attributes as ovals. Crow's foot notation draws entities as boxes and puts the cardinality on the line ends: a ring for zero, a bar for one and a three-pronged crow's foot for many. This reference covers both, symbol by symbol.

What Do ER Diagram Symbols Mean?

Every entity relationship diagram is built from three ideas: entities (the things you store), attributes (facts about each thing) and relationships (how the things connect). On top of those sit cardinality symbols, which say how many of one thing can link to another. The two notations draw the same ideas very differently.

ConceptChen notationCrow's foot notation
EntityRectangleBox with the name as a header
AttributeOval joined to its entityA row inside the box
RelationshipDiamond with a verb insidePlain line with a verb label
Cardinality1, N or M written on the linesSymbols on each line end
KeyUnderlined attribute namePK label or a key marker on the row

Both sets of ER diagram symbols describe the same model. Chen suits conceptual models, where you're still deciding what exists. Crow's foot suits logical and physical designs that will turn into tables. If you want to keep a legend like this in your own docs, the Markdown cheat sheet covers the table syntax.

Chen Notation Symbols: Rectangles, Diamonds and Ovals

Chen notation is named after Peter Chen, whose 1976 paper in ACM Transactions on Database Systems set out the entity relationship model. Rectangles for entities and diamonds for relationships come straight from that paper. Ovals for attributes, and several of the other shapes below, are later Chen-style conventions that most database courses and textbooks now teach.

SymbolShapeMeaningExample
Strong entityRectangleA thing with its own identitySTUDENT
Weak entityDouble rectangleCan't be identified without an owner entityDEPENDENT of an EMPLOYEE
RelationshipDiamondHow entities connectENROLLS
Identifying relationshipDouble diamondLinks a weak entity to its ownerHAS (EMPLOYEE to DEPENDENT)
AttributeOvalA propertyemail
Key attributeOval, name underlinedUniquely identifies the entitystudent_id
Multivalued attributeDouble ovalCan hold several valuesphone_numbers
Derived attributeDashed ovalCalculated from other dataage (from birth_date)
Composite attributeOval with child ovalsSplits into partsname (first, last)
Total participationDouble lineEvery instance must take partEvery COURSE has a teacher

Most textbooks write Chen cardinality as text on the connecting lines. Here's the classic many-to-many case sketched in plain text, with square brackets for rectangles and angle brackets for the diamond:

[STUDENT] ---M--- <ENROLLS> ---N--- [COURSE]
                      |
                   (grade)

That reads as: a student enrolls in many courses, and a course enrolls many students. The grade oval hangs off the diamond because it belongs to the enrollment, not to either entity. Chen lets a relationship carry attributes like this.

One honest limitation: Mermaid's ER diagrams only use crow's foot notation, so this section uses tables and a text sketch instead of a live diagram. If your course requires Chen shapes, you'll need a drawing tool for those.

Crow's Foot Notation: The Line-End Symbols

A crow's foot ER diagram uses three marks. A ring means zero, a bar means one and the crow's foot (three prongs) means many. Each end of a relationship line pairs two of these marks. The mark nearest the entity is the maximum. The mark further along the line, toward the middle, is the minimum.

Line end (middle, then entity side)MinimumMaximumRead asMermaid marker (left, right)
Ring, then bar01Zero or one|o, o|
Bar, then bar11Exactly one||, ||
Ring, then crow's foot0ManyZero or more}o, o{
Bar, then crow's foot1ManyOne or more}|, |{

The last column is how you type each symbol in Mermaid, where the left-side marker mirrors the right-side one. If you copy this legend into your own Markdown table, escape every literal pipe as \|, as our Markdown table guide explains.

Here are all four, drawn live from one entity:

Read each line from STUDENT outward. A student rents zero or one locker, carries exactly one ID card, takes zero or more library loans and lists one or more emergency contacts. In every case the bar pair at the STUDENT end says each locker, card, loan or contact belongs to exactly one student.

Line style can carry meaning too, though conventions vary. In Mermaid and many database design tools, a solid line marks an identifying relationship, where the child can't exist without the parent, and a dashed line marks a non-identifying one.

How Do You Read Cardinality in an ER Diagram?

To read cardinality in an ER diagram, start at one entity, follow the line and read the symbols at the far end, next to the other entity. Those far-end symbols answer "how many of them does one of these have?" Then reverse direction and read the symbols at the near end.

ER diagram cardinality has two parts, and each has a name. Cardinality is the maximum: one or many. Ordinality, also called optionality, modality or participation, is the minimum: zero (optional) or one (mandatory). Every crow's foot line end shows both, the minimum on the inside and the maximum on the outside. The Mermaid ER diagram docs describe their two-character markers the same way.

Left to right, look at the symbols touching EMPLOYEE: a bar then a crow's foot, so each department employs one or more employees. Right to left, look at the symbols touching DEPARTMENT: two bars, so each employee works in exactly one department.

The most common misread is reading the symbols next to the entity you start from. If you read the DEPARTMENT end and say "a department has exactly one employee", you've flipped the relationship. Always read across the line.

One-to-One, One-to-Many and Many-to-Many Relationship Symbols

ER diagram relationship symbols combine two line ends, and the maximum on each end names the relationship type. Bars on both maximums make it one-to-one, a bar on one end and a crow's foot on the other make it one-to-many, and crow's feet on both make it many-to-many.

One-to-one

Each employee wears exactly one badge, and each badge belongs to exactly one employee. The second line is an optional one-to-one: an employee drives zero or one company car, and each car is assigned to exactly one employee.

One-to-many

A one-to-many relationship in an ER diagram has a bar as the maximum at the "one" end and a crow's foot as the maximum at the "many" end.

Each teacher teaches zero or more courses, and each course has exactly one teacher. In a database, the foreign key lives on the "many" side, so COURSE would store a teacher ID. Our ER diagram SQL guide covers how keys and constraints translate into these line ends.

Many-to-many

Relational tables can't store a many-to-many relationship directly, so crow's foot diagrams usually resolve it through a junction entity.

A student has zero or more enrollments, and so does a course, while each enrollment points to exactly one student and one course. Together the two lines say "students take many courses, and courses have many students". The grade from the Chen sketch above becomes a column on ENROLLMENT, because crow's foot relationships can't carry attributes. For an early conceptual sketch you can still draw a direct }o--o{ line between STUDENT and COURSE.

Chen vs Crow's Foot: Which Notation of ER Diagram Should You Use?

The two notations of ER diagram you'll meet most often answer different questions. Chen shows meaning, while crow's foot shows structure that maps straight onto tables.

ChenCrow's foot
Best levelConceptual modelLogical and physical model
AttributesOvals around the entityRows listed inside the box
RelationshipsDiamonds that can hold attributes and join 3+ entitiesBinary lines between two boxes
Cardinality1, N, M text on the linesRing, bar and crow's foot symbols
Primary keyUnderlined attributePK label next to the row
Space on the pageLarge, grows fastCompact
Where you see itTextbooks and DBMS coursesDatabase tools, schema docs, Mermaid

We prefer crow's foot for anything that will become tables, and Chen for whiteboard sessions where you're still deciding what the entities are. Crow's foot keeps a large schema compact, while the same schema in Chen sprawls across the page.

A few other notations show up in older tools and courses. Bachman diagrams use arrows between record types. Barker notation is the crow's foot variant used in Oracle's modeling tools, with dashed lines for optional ends. IDEF1X, once a US federal standard (FIPS 184), marks the many end with a dot. UML class diagrams write multiplicity as numbers like 0..*, and (min, max) notation writes pairs like (0, N) next to each entity.

Drawing Crow's Foot Symbols as Text in Markdown

You don't need a drawing app to produce these ER diagram symbols. Mermaid turns a few lines of text into a crow's foot diagram, and GitHub renders Mermaid code blocks in Markdown files, issues and pull requests. Each line end becomes the two-character marker from the line-end table above, so ||--o{ reads as exactly one on the left and zero or more on the right.

Two hyphens between the markers draw a solid identifying line, and two dots draw a dashed one. Attributes, keys and quoted labels have their own erDiagram syntax, which the Mermaid ER diagram docs linked above cover in full. For Mermaid basics and other diagram types, see our guide to Mermaid diagrams in Markdown.

Try it below. The preview draws the diagram from the mermaid block, so change one marker and watch its line end redraw.

Crow's foot symbols

Change one marker and watch the line end redraw.

erDiagram
DEPARTMENT ||--|{ EMPLOYEE : employs
EMPLOYEE ||--o| PARKING_SPOT : uses
EMPLOYEE ||--o{ TIMESHEET : submits
EMPLOYEE }o--o{ PROJECT : joins
36 words238 characters11 lines
Markdown

When the diagram looks right, the Mermaid editor exports it as PNG or SVG for slides and wikis. Or keep the text version in your schema docs, as our guide to Markdown for documentation suggests, so the diagram changes in the same commit as the database.

Once you can read a ring, a bar and a crow's foot from the far end of a line, most ER diagram symbols stop being a puzzle. Chen's shapes help when you're shaping ideas, and crow's foot markers take over when the design becomes tables. Paste any of the mermaid blocks above into the editor and the live preview draws the diagram next to your text, free and without an account.