A data model is a map of reality, but it is never the territory.
In short: Data models organize information and define how elements relate to real-world entities. They act as the blueprint for information systems, yet they are inherently abstract. Like a map, they must simplify the messiness of the world without distorting the truth, balancing mathematical elegance with the practical needs of business.
At its core, a data model is an abstract formalization of objects and their relationships within a specific domain. Whether tracking customers in a manufacturing firm or defining the structure of a banking application, these models standardize how data is stored and accessed. By establishing consistent definitions, organizations can achieve data compatibility, allowing different applications to share information seamlessly. Without this standardization, complex interfaces between systems can account for 25% to 70% of total system costs.
The ANSI framework, established in 1975, categorizes data models into three distinct layers: conceptual, logical, and physical. The conceptual model captures the semantics of a domain, such as entity classes and their associations. The logical model translates these into specific technologies, like tables or XML tags, while the physical model addresses the actual storage hardware, such as CPUs and partitions. This layered approach ensures that changes in storage technology do not necessarily force a redesign of the entire conceptual framework.
The history of data modeling reflects a shift from hardware-dependent designs to abstract, machine-independent specifications. Early pioneers like Young and Kent in 1958 sought to define data processing problems independently of hardware. By the late 1960s, Edgar F. Codd introduced the relational model based on first-order predicate logic, while Peter Chen formalized entity–relationship modeling in 1976. Later, the object-oriented paradigm changed the landscape by combining data with the procedures that operate on it.
Despite their utility, data models are often criticized for being poorly implemented, leading to rigid systems that struggle to adapt to changing business rules. Bill Kent, in his 1978 work Data and Reality, cautioned that models are not the world itself; they are interpretations. Effective modeling requires a delicate balance: creating enough order to support efficient computation while remaining flexible enough to avoid constraining the very business processes they are meant to serve.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Data model
- Also: cedar.princeton.edu — What is a Data Model?
To cite this card, link to https://intellectplus.co.uk/app/science-data-model.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?