Curriculum Design and Instruction To Teach
Building A Data Warehouse For Decision
Support: Designing the Database for a
Data Warehouse:
Author: Charles Hayes:
A Data Warehouse is the main repository
of the organization's historical data,
its corporate memory. For example, an
organization would use the information
that's stored in its data warehouse to
find out what day of the week they sold
the most widgets in May 1992, or how
employee sick leave the week before the
winter break differed between California
and New York from 2001-2005. In other words,
the data warehouse contains the raw material
for management's decision support system. The
critical factor leading to the use of a data
warehouse is that a data analyst can perform
complex queries and analysis (such as
data mining) on the information without
slowing down the operational systems.
While operational systems are optimized for
simplicity and speed of modification (online
transaction processing, or OLTP) through heavy
use of database normalization and an entity-
relationship model, the data warehouse is
optimized for reporting and analysis
(on line analytical processing, or OLAP).
Frequently data in data warehouses is
heavily denormalised, summarised and/or
stored in a dimension-based model but this
is not always required to achieve acceptable
query response times.
More formally, Bill Inmon
(one of the earliest and most
influential practitioners)
defined a data warehouse as
follows:
1. Subject-oriented, meaning that the data
in the database is organized so that all
the data elements relating to the same
real-world event or object are linked
together;
2. Time-variant, meaning that the changes
to the data in the database are tracked
and recorded so that reports can be
produced showing changes over time;
3. Non-volatile, meaning that data in the
database is never over-written or deleted,
once committed, the data is static, read-only,
but retained for future reporting;
4. Integrated, meaning that the database contains
data from most or all of an organization's
operational applications, and that this data
is made consistent.
Special Features Include:
Phases For Conducting a Needs Assessment:
Curriculum Design Supplement:
|a|. Subject-Questions-Answers:
Curriculum Design Plan:
Curriculum Design Goals:
Curriculum Design Objectives:
Instructional Goals:
Instructional Objectives:
Instructional Activities:
Instructional Evaluation Techniques:
Lesson Plans:
Standard Vocabulary:
Learning Objectives:
Key Terms:
A Limited Glimpse:
Topics Include:
* Introduction:
@ Designing the Database for a Data
Warehouse:
A. Transaction-Processing Databases:
B. Decision Support Databases:
C. Star Schema Database Design:
1. The Benefits of Using a Star Schema:
2. Understanding Star Schema Design-Facts
and Dimensions:
D. Varieties of Star Schemas:
1. How to Read the Diagrams:
a. Tips from the Trenches: Understanding
Facts and Dimensions:
2. Simple Star Schemas:
3. Multiple Fact Tables:
4. Outboard Tables:
5. Variations of a Star Schema:
6. Multi-Star Schemas:
E. A Salad Dressing Example:
1. Understanding the Available Data,
Browsing the Dimension Tables:
2. Using Table Attributes:
3. Creating Attribute Hierarchies:
F. Aggregation:
G. Denormalization
H. Data Warehouse Database Design Examples:
1. Reservation Database:
2. Investment Database:
3. Health Insurance Database:
4. Putting It All together:
I. Summary:
* STATE OF THE ART CURRICULUM DESIGN:
* NEW:
* ILLUSTRATIONS:
* DIAGRAMS-CHARTS:
* COLOR PHOTOS:
* BIBLIOGRAPHICAL REFERENCES & INDEX:
* PAPERBACK:
* TRANSPARENT FRONT PAGE:
* BLACK-WHITE-RED OR BLUE BACK PAGE COVER:
* BINDED WIRE-0: BLACK-WHITE-RED OR BLUE:
* 50 WHITE PAGES: 8x11"
* ALLOW 10 TO 14 DAYS TO RECEIVE ITEM:
