Data Warehousing and Data Mining Data Warehouse Design

Prof. Dr. M. H. B ohlen Fall 2008

Order Management

Consider a company that manages orders. The partial fact table for a dimensional model that models each line item on an order is shown in Table 1. OrderTransactionFact OrderDateKey RequestedShipDateKey ProductKey CustomerShipToKey SalesRepKey DealKey ... Table 1: Dimensional Schema for a Data Warehouse for Order Management Answer the following questions for this dimensional model: 1. Should there be a ShipDateKey in the fact table? 2. Give a possible schema of the CustomerShipTo dimension. 3. Estimate the size of the dimension tables. Describe where from you get the information for populating the dimension tables. 4. Can/should OrderDateKey and RequestedShipDateKey be foreign keys to the same dimension table? 5. Include the order number and the order line number into you data warehouse design. 6. How do you support the possibility that the person who receives the good and the person who pays for the good may be dierent? How do you deal with the case that multiple ship to addresses can have the same billing address. 7. Design the measures for OrderTransaction fact table. 8. Assume all amount measures shall collapsed into a single amount and a dimension shall be used to describe if it is a gross amount, discount amount, etc. Provide the corresponding dimensional schema. Discuss pros and cons of such a schema. 1

Invoice Management

Instead of a data warehouse that manages order transactions we want to have a data warehouse based on invoices ` a la Amazon.com. 1. Design a schema for a data warehouse that models orders in terms of invoices. 2. Assume you want to capture customer satisfaction information such as on time, complete, and damage free. How would you do this? 3. Assess the business value of your data warehouse. 4. Assess how dicult it is to deploy such a data warehouse.