Loading content
A logical data model is crucial for understanding data and its relationships within an organization. It enables a clear representation of entities, attributes, and their interactions, enhancing data management and usage.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A logical data model describes business data objects, their properties, and relationships independently of a particular database technology.
The approach comes from data modeling and was formalized by Chen's 1976 Entity-Relationship Model. Later standards such as ISO/IEC 11179 organize terms and metadata, while a logical model mediates between business understanding and physical storage.
First draw the things in the domain and their connections: a customer orders a product, and an order contains lines. Only then choose whether tables, documents, or another structure stores them.
A distinguishable business thing is described through its properties.
A relationship shows how data objects connect in the domain.
The model initially stays separate from tables, columns, or storage products.
A logical data model builds shared domain understanding and makes later database decisions traceable.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.