Data Model¶
A formal information-system structure that declares data types, attributes, relationships, integrity rules, and permitted operations at a stated conceptual, logical, or physical level.
Core Idea¶
A data model is a formal system for describing what data an information system can represent and how that data may be organized, related, constrained, and manipulated. The term operates at two linked levels: a modeling formalism, such as the relational or entity–relationship model, and a particular application model expressed with that formalism, such as Customers, Orders, and Products. A valid entry must declare which level it means.
Data models mediate between a domain and stored or exchanged representations. Codd's relational model introduced relations, operations, and integrity concerns while separating logical representation from machine organization. Chen's entity–relationship model made entities, relationships, and attributes explicit for conceptual design.
Scope of Application¶
Data models are used in database design, enterprise architecture, application integration, APIs, data warehouses, metadata registries, scientific information systems, and interchange standards. Conceptual models capture domain commitments independently of technology. Logical models translate those commitments into a formalism such as relations and keys. Physical models add storage, indexing, partitioning, or platform choices.
The ANSI/SPARC framework's external, conceptual, and internal levels remain a canonical articulation of viewpoint separation. ISO/IEC 11179 standards further demonstrate that entities, relationships, attributes, data elements, and datasets require explicit metadata definitions and registration structures in interoperable environments.
Clarity¶
The abstraction makes disagreements diagnosable. Two teams may use the same words but disagree about entity identity; agree on entities but disagree on relationship cardinality; or agree logically while using different physical storage. Labeling the model level prevents a physical optimization from masquerading as a conceptual truth.
Manages Complexity¶
The model compresses many individual records into reusable commitments. Instead of reasoning separately about every customer-order pair, designers state entity, key, cardinality, and integrity rules once. Query and update operations can then rely on those invariants. Codd's relational closure is a strong example: relation-to-relation operations preserve the logical kind of result.
Abstract Reasoning¶
Suppose Customer has key customer_id, Order has key order_id, and each Order references one Customer. The model licenses checks: duplicate customer keys are invalid; an order with a nonexistent customer violates referential integrity; multiple orders may map to one customer if the declared cardinality permits it. These deductions follow without inspecting application code.
Knowledge Transfer¶
Literal transfer occurs across databases, APIs, messages, and metadata registries when domain types, relations, constraints, and mappings remain explicit. A relational model and a graph model can express overlapping domains while licensing different primitive operations; translation must preserve declared semantics rather than just field names.
The broad lesson “map a domain into a constrained formal medium” belongs to Representation. Calling a rhetorical sketch a data model imports technical authority unless it defines data-bearing constructs, integrity, and manipulation at a stated level.
Relationships to Other Abstractions¶
Current abstraction Data Model Domain-specific
Parents (1) — more general patterns this builds on
-
Data Model is a kind of Representation Prime
Data Model instantiates Representation by mapping selected domain entities, relations, and constraints into a formal information-system medium that supports operational use.
Children (1) — more specific cases that build on this
-
Measure (Data Warehouse) Domain-specific is a kind of Data Model
Data Model is the proposed immediate parent.
Hierarchy path (1) — routes to 1 parentless root
- Data Model → Representation → Abstraction
Neighborhood in Abstraction Space¶
Data Model sits in a sparse region of the domain-specific corpus (61st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Document Models, Mapping & Maintenance (20 abstractions)
Nearest neighbors
- Specification language — 0.87
- Knowledge organization system — 0.87
- Data Class — 0.86
- Primitive Obsession — 0.86
- Data Extraction Through Prompting — 0.86
Computed from structural-signature embeddings · 2026-09-08