Вы находитесь на странице: 1из 3

Group Assignment 1 BUS Matrix Architecture and DW Design

Marks: 15
1. Choose a domain and at least three (3) business processes in that domain
2. Prepare BUS matrix architecture showing common dimensions for those business
processed
3. Design (Logical Design) for data mart (Fact Table and Dimension Tables) for those
business processes
4. Submit the assignment one per group in word file
5. Name of word file should be Asg1_Groupnn (nn is the group number assigned)
6. Request to one person for the batch: Please collect all the assignments, zip it, and send
it to Examination Department cc to me, i.e. sunil_lakdawala@hotmail.com
Typical example can be used as a template for submitting the assignment

1. Data Mart Matrix Showing the Data Warehouse Bus


Architecture

X
X

X
X

X
X

Real Estate Inventory

Service Call Status

Service Call Type

Employee

Organization

GL Account

Purchased Product

Destination Phone #

Origin Phone #

Usage Type

Vendor

Pricing Package

Product

Customer

Time

Resolution Date

Billing Date

Data Mart
**Customer
Usage
Billing
**Call
Detail
Tracking
**Vendor
Contracts
**Purchase
d Product
Tracking
**Materials
Inventory
**Service
Call
Tracking
**Repair
Items
General
Ledger
Purchase
Orders

Date

The data mart matrix shows the relationship between the possible data marts and dimensions. Any
dimension (column) with more than one X implies that this dimension must be conformed across
multiple data marts in order to fit into the Data Warehouse Bus Architecture. A brief description of
each data mart and dimension follows the matrix. ** Indicates data marts that are detailed in the
Dimensional Model Document.

Dimension
Name
Date
Time
Billing Date
End Date
Customer
Product
Pricing
Package
Usage
Type
Originating
Phone #
Destination
Phone #
Vendor
Purchased
Products
GL
Account
Organizatio
n / Location
Employee
Data Mart
Name
**Customer
Usage
Billing
**Call
Detail
Tracking
**Vendor
Contracts
**Purchase
d Product
Tracking
**Materials
Inventory
**Service
Call
Tracking
**Repair
Items
General
Ledger
Purchase
Orders
Account
Receivable
s

Dimension Description
Contains all of the attributes associated with the date that activity occurred.
Contains attributes about the time when an activity occurred.
Contains all of the attributes associated with the date that products and/or services
were billed to the customer.
Contains all of the attributes associated with an end pr resolutions date (contract end,
service call resolved).
Represents both commercial and consumer customers and all of the associated
attributes.
Contains information about products and services that we sell.
Describes the pricing used for customer billings.
Describes the type of usage by product.
Describes the telephone number where a call was made from.
Describes the telephone number where a call was made to.
Characteristics of companies that we purchase products and supplies from.
Describes the different items that we purchase as a company.
The general ledger account numbers for financial tracking and reporting.
The business group within the company and other organizational relationships.
Describes the individual employee of our company.

Data Mart Description

Represents monthly customer billing at the product and price package grain.

Detailed customer call activity that is included in customer usage billing.


Specifics about the relationship between Telco and suppliers of products and services.
This includes both parts and products sold to customers and items purchased for
internal use (office supplies etc.)

Contains invoice line details about Telco's purchases.


Tracks parts and product inventory in the field offices.
Contains details about customer calls that result in a service work order being
produced. This includes problems as well as new product/service requests.
Tracking of parts that are used during service calls and items that are returned to
Telco, that may be re-used or re-furbished and sold as used.
Information from the official financial records.
All purchases made by Telco.

Details about bills - both paid and unpaid.

2. Logical Design for Data Mart


DIM_Date
Date_Key
Date
Month
Quarter
Year
Total
DIM_Product
Product_Key
Product_ID
Product_Name
Type
Color
Packaging
Size

DIM_Store
Store_Key
Store Name
City
State
Region
Country
Fact_Sale
Date_Key
Store_Key
Product_Key
Quantity
Sale