iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
ER diagram (ERD) cardinality states how many instances of one entity may be related to a single instance of another. Read the relationship at each endpoint separately: the maximum marker says one or many, while the minimum marker says whether participation may be zero or is required. Because ERD symbols differ among notations and tools, check the diagram’s legend before interpreting a line.
What cardinality means in an ER diagram
Cardinality describes the permitted count of related entity instances. For a relationship between Book and LibraryCopy, it answers questions such as “How many copies can belong to one book?” and, in the reverse direction, “How many books can one copy belong to?”
The answer is directional. The mark beside LibraryCopy describes how many copies may be associated with one Book. The mark beside Book describes how many books may be associated with one LibraryCopy. Those two rules can be different.
Cardinality versus participation (optionality)
These terms are related but not interchangeable:
- Cardinality or maximum multiplicity is the largest allowed number of related instances: one or many.
- Participation, optionality, or modality is the smallest allowed number: zero or one.
Combining the minimum and maximum gives a range such as 0..1 (zero or one) or 1..many (one or more). Thus “one-to-many” normally describes maximum counts; it does not by itself say whether either side is optional.
How to read crow’s foot notation
In the crow’s foot convention documented by Microsoft, a circle means zero, a bar means one, and a crow’s foot means many. The inner symbol indicates the minimum; the symbol nearest the entity indicates the maximum.
| Endpoint marks | Min–max | Plain-language meaning |
|---|---|---|
| Circle + bar | 0..1 | Zero or one; optional single |
| Bar + bar | 1..1 | Exactly one; mandatory single |
| Circle + crow’s foot | 0..many | Zero or more; optional many |
| Bar + crow’s foot | 1..many | One or more; mandatory many |
To translate a line, start at one entity, say the relationship as a verb, and read the symbols next to the other entity. Then perform the same exercise in reverse.
Example: a one-to-many relationship
Suppose a crow’s foot appears at the LibraryCopy end and a single bar at the Book end. From a Book, the rule is “one or more LibraryCopy records” if the copy endpoint is bar plus crow’s foot. From a LibraryCopy, the rule is “exactly one Book” if the Book endpoint is bar plus bar. This is a one-to-many relationship, but the minimum on each side is a separate fact.
Rank #2
- Used Book in Good Condition
Example: optional borrowing
A registered User may exist before borrowing anything. A circle plus crow’s foot at the Loan end expresses zero or more loans for one user. If every Loan must identify exactly one User, the User end uses bar plus bar. Reading both directions prevents the common mistake of assuming that “many” also means “at least one.”
Read both directions independently
- Choose an occurrence of entity A.
- Follow the relationship toward entity B.
- Use the endpoint beside B to state B’s minimum and maximum count for that one A.
- Reverse the sentence: choose one B and read the endpoint beside A.
- Write both rules in plain language and check them against the business requirement.
Salesforce illustrates this approach with an account-contact relationship: each Contact must primarily belong to one and only one Account, while an Account may be primarily represented by one or more Contacts. The two directions are not redundant; together they define the relationship.
Common relationship patterns
One-to-one
Each instance on either side can relate to at most one instance on the other side. Whether the relationship is exactly one or optional one depends on the minimum marks: 1..1 on both ends requires participation; 0..1 permits an unpaired instance.
One-to-many
One side permits at most one related instance, while the other permits many. Specify both minimums as well: a parent may have 0..many children or 1..many children, and each child may require exactly one parent or allow zero or one.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsMany-to-many
Both ends permit many related instances. Minimums still matter: 0..many on both sides allows isolated instances, while 1..many requires every instance to participate. In a relational implementation, this usually becomes an associative or junction entity, but the ERD’s business rule remains bidirectional.
Cardinality examples that need careful wording
Book and library copy
A library copy can belong to exactly one book. That statement constrains each copy’s relationship to Book; it does not establish how many copies every book must have. The book-side rule could be zero or more, one or more, or an exact business limit if the organization specifies one.
Exact limits are additional constraints
An ERD endpoint showing “many” does not communicate a cap such as “no more than five copies per book.” An exact upper limit, conditional rule, date dependency, or other business restriction must be documented separately and implemented with appropriate database logic. Cardinality is not a guarantee that a database product will enforce every rule automatically.
Not all ER diagrams use crow’s feet
Notation is not universal. Chen diagrams commonly label relationships with 1, M, or N. Other styles include Bachman, IDEF1X, and Barker notation. Educational and vendor documents may place symbols differently or use different terms for minimum participation.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use the legend for the specific diagram or tool. Without it, a circle, bar, line, or number can be misread. The IIM Ahmedabad teaching material and IBM’s ERD overview both emphasize that no single notation standard governs every ER diagram.
Best Value
Conceptual ERD rules versus software settings
A modeling tool may expose its own interpretation. For example, Power BI’s relationship-cardinality setting is tied to whether columns contain unique or duplicate values in that model. That product-specific setting is not a replacement for documenting conceptual minimum participation and business meaning in the ERD.
A practical checklist for interpreting any relationship
- Identify the two entity types and the relationship verb.
- Confirm the notation and read its legend.
- At each endpoint, record the minimum: zero or one.
- At each endpoint, record the maximum: one or many.
- Translate the marks into two directional sentences.
- Check whether optionality matches real business operations.
- Look for separate caps, conditional rules, or temporal constraints that the endpoint symbols cannot express.
- Distinguish a conceptual ERD rule from a particular database or modeling product’s implementation setting.
What cardinality tells you—and what it does not
Cardinality tells you the allowed range of related entity instances at each end of a relationship. It does not, by itself, name the relationship’s business meaning, enforce every rule in a database, specify an exact finite cap, or determine which notation a different diagramming tool will use. A reliable interpretation always combines the endpoint marks, their direction, the diagram legend, and the written business requirements.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →

