Borrowed Patterns & Source Notes
The Northstar reference system was reviewed as a design source. Meridian Commerce Group remains a separate fictional enterprise so the CDMP system can evolve independently and remain DMBOK-centered.
Patterns intentionally borrowed
| Pattern | How Meridian adapts it |
|---|---|
| One-company continuity | One fictional enterprise persists across all chapters so later work reuses earlier data, decisions, and defects. |
| Business first | Every dataset is tied to a business process and use, preventing table-first thinking. |
| Technology supports learning | Tools are selected because they make a Data Management concept observable, not because they are fashionable. |
| Stable identifiers | Systems, datasets, defects, incidents, and decisions use stable IDs so lineage/evidence can cross labs. |
| Synthetic data by default | Safe fictional data supports repeatable defects and prevents privacy/security problems. |
| Defect injection | Specific known defects create diagnostic labs and before/after evidence. |
| Evidence discipline | Learners produce inspectable artifacts rather than merely claiming a task was performed. |
| Defined target depth | Each technology has a learn-this / stop-here boundary. |
| Block structure | Purpose → what to learn → do → save/prove → done when. |
| Independent completion | Mastery requires explaining/rebuilding without line-by-line tutorial dependence. |
| Scope boundaries | Explicit exclusions prevent an unrelated DBA/Data Engineering/cloud bootcamp. |
What is deliberately different
- The controlling content authority is the DMBOK chapter being studied, not a career roadmap.
- The applied curriculum follows DMBOK Chapters 1–17 and CDMP learning needs rather than Northstar phase numbering.
- Meridian begins intentionally imperfect so the DMBOK Knowledge Areas can progressively improve one estate.
- Technology prerequisites are explicit rather than hidden as unexplained commands inside labs.
- Every chapter lab ends with a DMBOK Debrief and retrieval/transfer check.
- Detailed chapter labs are finalized only after reading the full controlling chapter source.
External technology-source policy
Current official vendor/project documentation may control installation, syntax, and software feature behavior because those details change over time. Those sources support the technology layer only. They do not define DAMA concepts or CDMP exam meaning.
When software behavior changes, recheck current official documentation before changing the lab.