Bringing it all together: business meaning, automation, collaboration, and universals
Summary
After exploring elephants, patterns, ontologies, and mappings, we’ve arrived at the full picture: a four-pillar methodology for business-centered data architecture. These pillars — Business-Oriented LDM, Model-Driven Engineering, Business-Friendly Mapping, and Universal Data Models — provide a framework for balancing agility, rigor, and business alignment.
Press enter or click to view image in full size
Why Four Pillars?
The metaphor of a temple with four pillars is deliberate:
- The roof represents the enterprise data platform — trusted, usable, and business-aligned.
- The pillars are the supporting capabilities.
- The foundation is business meaning — without it, nothing stands.
This vision echoes John Giles’ nimble elephant and Len Silverston’s universal models — but adapted into a pragmatic methodology for modern data engineering.
Pillar 1: Business-Oriented LDM
The starting point is the business-oriented logical data model (LDM):
- Defines business concepts and their relationships.
- Serves as the enterprise ontology.
- Shapes integration layers into business-shaped models, as I described in The Case for a Business-Shaped Integration Layer.
Pillar 2: Model-Driven Engineering
Next comes Model-Driven Engineering (MDE):
- Metadata and diagrams are treated as executable assets.
- Automation replaces manual coding.
- As I explained in From Coding to Modeling: The Rise of Model-Driven Data Engineering, this is about shifting effort from code to design.
Pillar 3: Business-Friendly Mapping
Mappings become the bridge between business and IT:
- Transparent, collaborative, and stored in metadata.
- Allow both business and technical users to validate meaning.
- This was the theme of Cooking with Data: How Business-Friendly Mapping Brings Clarity to ETL.
Pillar 4: Universal Data Models
Finally, Universal Data Models (UDMs) provide the accelerators:
- Reusable patterns from Len Silverston’s Data Model Resource Books.
- Ensure coverage of common domains (Party, Product, Agreement, Event).
- Let us build faster while staying aligned with proven designs.
👉 I explored this in How Universal Data Models Support Business-Oriented Data Modeling.
The Roof: A Business-Centered Data Platform
When the four pillars hold up the roof, the result is:
- Business-aligned integration layers (3NF, bi-temporal).
- Automation through metadata and models.
- Transparency and collaboration across business and IT.
- Scalability through universal patterns.
This creates a platform that is both robust and nimble — a true realization of the nimble elephant metaphor.
Key Takeaways
- The four pillars are: Business-Oriented LDM, Model-Driven Engineering, Business-Friendly Mapping, and Universal Data Models.
- Together, they support a business-centered data architecture.
- This framework balances agility and rigor, patterns and universals, business and IT.
- It builds on the legacies of John Giles, Len Silverston, and ensemble modeling, while being grounded in modern practice.
✍️ This article is Part 7 of the series “Why Elephants Matter in Data Modeling”, where I explore how John Giles’ ideas, Len Silverston’s Universal Data Models, and my own methodology come together in a business-first, model-driven approach.
Series overview
- Part 1: Why Elephants Matter in Data Modeling
- Part 2: Patterns + Universals: The Foundations of Reuse
- Part 3: From Ontology to Enterprise View
- Part 4: Borrowing from Data Vault Without Building One
- Part 5: Model-Driven Engineering in Practice
- Part 6: Business-Friendly Mapping as a Collaboration Tool
- Part 7: The Four Pillars of Business-Centered Data Architecture