|
 |
 |
These Enterprise Data Models all follow a Design Pattern which has a Top-Level Model with separate Models for specific Subject Areas.
Click here for a Data Architecture showing how an Enterprise Data Model can be created from a Canonical Data Model
and Subject Area Models.
We have three options when it comes to designing an Enterprise Data Model :-
1) Top-down - starting with a 'Mission Statement'
2) Bottom-up - starting with some original source documents, such as Bank Statements, Financial Reports, Invoices, Sales Receipts and so on
3) 'Middle-out' - starting with a Life Cycle analysis for Customers, Events or Products
Here's an interesting discussion on
LinkedIn.
|
|