02 — Capability · BC-750.20
Data Architecture & Modeling
Decide how data is structured, where it lives and how it flows between stores, so analytical and operational uses share one understanding of what a customer, product or order is.
- Data Modeling
- Information Architecture
- Data Platform Design
In scope
- Enterprise and domain data models
- Data storage and platform design
- Data flow and integration design
- Data classification by sensitivity
Out of scope
- Enterprise architecture principles across all layers (see BC-170)
- Physical schema design inside one application (see BC-720)
Realized by · 1
Used in · 0
- Not yet placed on a value stream.
Build it · 13
- pattern Sharding via BC-750.20.20
- pattern Bounded Context via BC-750.20.10
- pattern Event Sourcing via BC-750.20.20
- pattern CQRS via BC-750.20.20
- pattern Data Mesh via BC-750.20.20
- pattern Medallion Lakehouse Layering via BC-750.20.20
- stack Open lakehouse analytics platform via BC-750.20.20
- book Software Architecture: The Hard Parts
- book Domain-Driven Design
- book Designing Data-Intensive Applications
- book Data Mesh
- book Fundamentals of Data Engineering
- book Database Internals
Decomposes into · 4
- BC-750.20.10Enterprise Data ModelingMaintain the conceptual and logical models of the enterprise's core entities and their relationships, independent of any one system.
- BC-750.20.20Data Platform DesignChoose and shape the warehouses, lakes and marts that hold analytical data, with the zones and standards each one follows.
- BC-750.20.30Data Flow DesignSpecify how data moves from source to consumer — frequency, transformation, ownership at each hop — before a pipeline is built.
- BC-750.20.40Data ClassificationLabel data by sensitivity and regulatory scope so storage, access and sharing decisions can be made by rule rather than by debate.