In UX architecture, cardinality describes how many records of one object type can relate to a record of another type. It helps designers support the number of related records users may encounter, from an empty list to a collection they need to search.
What are the types of cardinality?
Ask the relationship question in both directions. These examples describe the rules of an illustrative travel operations tool.
| Relationship | Example | What the interface needs to support |
|---|---|---|
| One-to-one | A traveler has at most one preferences profile, and each profile belongs to exactly one traveler. | Show preferences when a profile exists and offer a way to create one when it is missing. |
| One-to-many | A trip can have zero or more bookings, and each booking belongs to exactly one trip. | Provide a way to view and manage multiple bookings from the trip. |
| Many-to-many | A trip can include multiple travelers, and each traveler can take multiple trips. | Let agents associate an existing traveler with another trip and find the traveler’s trips when needed. |
Why do minimum and maximum counts matter?
“One-to-many” leaves open whether a trip can exist before its first booking. In the example, the minimum is zero bookings per trip and one trip per booking. A new trip needs a useful empty state, and the booking creation flow needs a trip selection when it starts outside a trip.
Distinguish the maximum the product allows from what people usually see. If most trips have two bookings but group trips can have dozens, test both sizes. Typical volume, tasks, and access rules help determine whether a simple list or a searchable table makes sense.
How does cardinality affect ORCA design decisions?
ORCA teams can first record that Trips and Bookings are related using a Nested Object Matrix, then use cardinality and ORCA Relationship Requirements (MCSFD) to clarify the relationship during the Requirements round. Where a many-to-many relationship carries its own attributes, such as reservation status, teams define a Junction Object. Use the object map to find rules that need more detail.
- Can an agent add the first booking directly from the empty Bookings section?
- Can an agent move a booking to another trip, and what would need to be checked?
- Can an agent link a traveler who already appears on another trip, and how should the interface prevent duplicate records?
A relationship can exist in the model even when one role cannot see it or has no reason to navigate in both directions. Decide what each role needs to see and do before turning the relationship into a link.