Data Models
Commentary
This Model dates from 2001 and shows how Inheritance helps us to model both Commercial and Personal Customers.
However it doesn't show any details of other things that we are interested in, like Payment Methods.
So we look for another Model which is a more suitable starting-point for a Customer who is going to make a Purchase.
This Model dates from 2006 and shows a general solution for Customers and Addresses.
We will have to add more Customer-related items to the Customer Entity but it is fine for a starting-point.
However it doesn't show any details of other things that we are interested in, like Payment Methods.
So we look for another Model which is a more suitable starting-point for a Customer who is going to make a Purchase.
This Model dates from 2010 and was part of a Master Data Management (MDM) approach.
It includes Payment Methods and the MDM approach is good for this current work so we decide to includ it in our Top-Level Model.
So we choose this Customers and Payments Model and will adapt it to suit our requirements. barry
This Customers and Orders Model dates from 2010.
It includes (Customer-related) Mailshots and (Promotion-related) Promotions. It is comprehensive so we decide to include it. barry
This Model for Public Transport dates from 2009
Step 6 : The Customer makes a reservation for a FlightThis Model dates from 2008
When we look at the Trains and Flight Reservations Models, we realise that we can replace them both by the "Trains and Boats and Planes" Model.
We prefer to have a smaller number of Models and have more powerful Models.
Step 7 : Replace two Models by one for Trains and Boats and PlanesThis Model dates from 2013
When we look at the Trains and Flight Reservations Models, we realise that we can replace them both by the "Trains and Boats and Planes" Model.
We prefer to have a smaller number of Models and have more powerful Models.
In the next Model, we replace Customers with Parties.
Logically, these are equivalent but the Parties approach is more general and professional.
You can choose the one which is more appropriate to your situation.
Reservations Subject Area
(which we prefer to Customers Purchases)
Our Data Warehouse is a Generic Third-Normal Form design.
Our Data Warehouse has a Third-Normal Form design and is the same As our final Top-Level Model with Customers.
This shows Data Mart Phase 3 for our specific Requirements.
Our Data Warehouse has a Third-Normal Form design and is the same As our final Top-Ledvel Model with Customers.