Data Models and Their Levels
Introduces what a data model captures and how conceptual, logical, and physical models differ in purpose and detail.
From business meaning to database implementation
A model is a task-focused abstraction
A describes what information a system needs to store, the properties of that information, how the information is related, and rules that help keep it meaningful. It abstracts a real-world domain: it includes facts relevant to the task, not every detail of reality. The model therefore helps organize information around what the system needs to represent.
Three levels, from meaning to implementation
The levels describe the same domain with increasing detail; they are not competing accounts of it.
Conceptual: identifies important business ideas and their relationships. For example, Customer places Order names two concepts and states how they are connected. It communicates business meaning without describing database structures.
Logical: develops that meaning into entities, attributes, identifiers, and rules. It specifies the information structure, but does not commit to a particular database product.
Physical: describes how a chosen database will implement the design, using details such as tables, columns, keys, indexes, and storage.
The progression is useful because it separates decisions about what the information means from decisions about how to build it. The conceptual level makes the business relationship clear; the logical level specifies the data structure and rules; the physical level maps that design to a particular database. Each level adds a different kind of detail while remaining focused on the same information and relationships.
: The level of a focused on business meaning.
: The level of a that describes information structure without committing to a particular implementation.
: The level of a focused on how a design is implemented in a particular database.