Data Warehousing and Mining

Mind Map by , created over 5 years ago

Revision mind map for Data Warehousing and Mining.

Created by i7752068 over 5 years ago
Machine Learning
Alberto Ochoa
Model Roles
Steve Hiscock
Data Mining Tasks
Steve Hiscock
3. The Bolshevik's Seizure of Power
Teaching students to be digitally literate
Micheal Heffernan
Chapter 19 Key Terms
Monica Holloway
Insurance Policy Advisor
Sufiah Takeisu
Data Mining Part 1
Kim Graff
Minería de Datos.
Marcos Soledispa
Data Warehousing and Mining
1 Data Warehousing
1.1 Increased corporate productivity.
1.2 Competitive advantage.
1.3 Potential for high ROI.
1.4 Extremely high initial costs (£50k+)
1.5 Long development time (3 years +/-)
1.6 High demand for memory.
1.7 High maintenance costs.
1.8 Problems with source data (extraction, cleaning, loading).
2 Building a Data Warehouse Database (Dimensionality Modelling)
2.1 Fact Tables
2.1.1 Contains facts generated by events in the past.
2.1.2 Data in tables should be regarded as read only.
2.1.3 Tables are often very large.
2.2 Dimension Tables
2.2.1 Contains descriptive textual data.
2.2.2 Simple primary keys.
2.2.3 Gives a characteristic star scheme or star join.
3 Star Schema
3.1 De-normalising reference data can speed up query performance.
3.2 Main aim is to avoid data redundancy.
3.3 This achieved in part via the process of normalisation.
4 OTLP System
4.1 Automating business saves money.
4.2 Data could be useful in organisations future operations.
4.3 Information too detailed.
4.4 May require information from more than one OTLP system.
4.5 Difficult to extract information.
5 Snowflake Schema
5.1 Variant of Star Schema where dimension tables do not contain de-normalised data.
5.2 Dimension tables have other dimension tables linked to them via foreign keys.
5.3 More than one dimension table can share these "dimension of a dimension" tables.
6 Starflake Schema
6.1 Hybrid structure that contains a mixture of star and snowflake schema's.
6.2 Contains both normalised and de-normalised data.
6.3 Some dimension tables may be present in both normalised and de-normalised forms.
7 OLAP Analytical Operations
7.1 Consolitation
7.1.1 Involves the aggregation of data, such as "roll ups" e.g. branches can be rolled up to cities, cities to countries etc.
7.2 Drill-down
7.2.1 Reverse of consolidation.
7.2.2 Involves displaying the detailed data that compromises the consolidated data.
7.3 Slicing and Dicing (aka pivoting)
7.3.1 Ability to view data from different viewpoints.
7.3.2 One slice may display revenue by type of property within cities.
7.3.3 Another slice may display revenue by branch office within city.
7.3.4 Often performed along a time axis to find patterns and trends.
8 Data Mining Operations and Techniques
8.1 Predictive Modelling
8.1.1 Reflect human experience using observations to form a model of the important characteristics of some phenomenon.
8.1.2 Model developed using a two-phase supervised learning approach. The training phase uses a large sample of historical data called a training set to build a model of the important characteristics. The testing phase tests the accuracy and performance of the model on new data.
8.1.3 Used in credit approval, customer retention management, direct marketing.
8.2 Database Segmentation
8.2.1 Partition database into an unknown number of segments or clusters of similar records.
8.2.2 Results can be displayed on scatterplot.
8.2.3 Used in customer profiling and direct marketing.
8.3 Link Analysis
8.3.1 Aims to discover links (called associations) between individual records or groups of records in a database.
8.4 Anomaly Detection
8.4.1 Identifies outliers (expressions of deviation from previously known expectations and norms).
8.4.2 Used in detection of credit card and insurance fraud, quality control and defects tracing.