Conceptual Schema

UX & Product Architecture • AI & Agentic Systems

A conceptual schema describes the information a system represents: its entities, their properties, relationships, and constraints, independently of physical storage. It gives teams a shared definition of what the data means and which business rules it must satisfy.

In product design, this helps teams agree on concepts such as Customer, Reservation, or Payment before designing their screens and behavior. The schema describes information structure; individual records are instances of that structure.

What does a conceptual schema contain?

An entity-relationship diagram can show the structure. Written definitions and rules supply details that a diagram alone may leave ambiguous.

A conceptual schema example: hotel reservations

Consider a simplified hotel system that sells one room per reservation. Room assignment may happen after booking. These are example requirements, not universal hotel rules.

Entity Meaning Example attributes
Guest The person making the reservation Name, contact details
Reservation A booking for one room over a date range Arrival date, departure date, status
Room A physical room in the hotel Room number

The relationships and constraints are explicit:

This model reveals a UI requirement: the reservation view needs an unassigned-room state. Here, Guest means the booker. Tracking everyone who stays would require extending the model to represent occupants separately.

Conceptual, logical, and physical models

In a common data-modeling workflow, the levels differ in detail:

Level Typical decision
Conceptual What entities exist, what they mean, and how they relate.
Logical Detailed attributes, identifiers, and relationship rules.
Physical Database-specific tables, column types, indexes, and storage choices.

Terminology varies. In the ANSI/SPARC three-schema architecture, the conceptual schema is the shared logical description of the database, between external user views and internal storage. It is not necessarily a lightweight early-stage diagram.

How does this help UX work?

Use the schema to discuss labels, record relationships, empty states, and rules with users and domain experts. In the hotel example, ask what happens when a reservation changes rooms or includes multiple rooms; the answers may change the model.

Object-Oriented UX can bring related domain questions into interface design, alongside users’ tasks and available actions. Validate the shared information model against real workflows, and update it as requirements change.

Sources