4chap4 BM

Data Mining:
Concepts and
Techniques
Chapter 4
May 5, 2015
Chapter 4: Data Mining Primitives,

Languages, and System
Architectures
Data mining primitives: What defines a
data mining task?
A data mining query language
Design graphical user interfaces based on

a data mining query language
Architecture of data mining systems
Summary
May 5, 2015
Why Data Mining Primitives

and Languages?
Finding all the patterns autonomously in a database?

unrealistic because the patterns could be too
many but uninteresting
Data mining should be an interactive process
User directs what to be mined
Users must be provided with a set of primitives to be
used to communicate with the data mining system
Incorporating these primitives in a data mining
query language
More flexible user interaction
Foundation for design of graphical user interface
Standardization of data mining industry and
practice
May 5, 2015
What Defines a Data Mining Task

?
Task-relevant data
Type of knowledge to be mined
Background knowledge
Pattern interestingness measurements
Visualization of discovered patterns
May 5, 2015
Task-Relevant Data (Minable

View)
Database or data warehouse name
Database tables or data warehouse cubes
Condition for data selection
Relevant attributes or dimensions
Data grouping criteria
May 5, 2015
Types of knowledge to be mined
Characterization
Discrimination
Association
Classification/prediction
Clustering
Outlier analysis
Other data mining tasks
May 5, 2015
Background Knowledge:
Concept Hierarchies
Schema hierarchy
E.g., street < city < province_or_state <
country
Set-grouping hierarchy
E.g., {20-39} = young, {40-59} =
middle_aged
Operation-derived hierarchy
email address: login-name < department
< university < country
Rule-based hierarchy
low_profit_margin (X) <= price(X, P1)
and cost (X, P2) and (P1 - P2) < $50
May 5, 2015
Measurements of
Pattern Interestingness
Simplicity
e.g., (association) rule length, (decision) tree size
Certainty
e.g., confidence, P(A|B) = n(A and B)/ n (B),
classification reliability or accuracy, certainty
factor, rule strength, rule quality, discriminating
weight, etc.
Utility
potential usefulness, e.g., support (association),
noise threshold (description)
Novelty
not previously known, surprising (used to remove
redundant rules, e.g., Canada vs. Vancouver rule
implication support ratio
May 5, 2015
Visualization of Discovered
Patterns
Different backgrounds/usages may require different
forms of representation
E.g., rules, tables, crosstabs, pie/bar chart etc.
Concept hierarchy is also important
Discovered knowledge might be more understandable

when represented at high level of abstraction
Interactive drill up/down, pivoting, slicing and dicing

provide different perspective to data
Different kinds of knowledge require different

representation: association, classification, clustering,
etc.
May 5, 2015
A Data Mining Query

Language (DMQL)
Motivation
A DMQL can provide the ability to support ad-hoc

and interactive data mining
By providing a standardized language like SQL
Hope to achieve a similar effect like that SQL has on

relational database
Foundation for system development and evolution
Facilitate information exchange, technology transfer,
commercialization and wide acceptance
Design
DMQL is designed with the primitives described

earlier
May 5, 2015
10
Syntax for DMQL
Syntax for specification of
task-relevant data
the kind of knowledge to be mined
concept hierarchy specification
interestingness measure
pattern presentation and visualization
Putting it all together a DMQL query
May 5, 2015
11
Syntax for task-relevant data

specification
use database database_name, or use

data warehouse data_warehouse_name
from relation(s)/cube(s)[where condition]
in relevance to att_or_dim_list
order by order_list
group by grouping_list
having condition
May 5, 2015
12
Specification of task-relevant
data
May 5, 2015
13
Syntax for specifying the kind of

knowledge
to
be
mined
Characterization
Mine_Knowledge_Specification ::=
mine characteristics [as pattern_name]
analyze measure(s)
Discrimination
mine comparison [as pattern_name]
for target_classwhere target_condition
{versus contrast_class_iwhere
contrast_condition_i}
analyze measure(s)
Association
mine associations [as pattern_name]
May 5, 2015
14
Syntax for specifying the kind of

knowledge to be mined (cont.)
Classification
mine classification [as pattern_name]
analyze classifying_attribute_or_dimension
Prediction
mine prediction [as pattern_name]
analyze
prediction_attribute_or_dimension
{set {attribute_or_dimension_i=
value_i}}
May 5, 2015
15
Syntax for concept hierarchy

specification
To specify what concept hierarchies to use

use hierarchy <hierarchy>for
<attribute_or_dimension>
We use different syntax to define different type of hierarchies
schema hierarchies
define hierarchy time_hierarchy on date as
[date,month quarter,year]
set-grouping hierarchies
define hierarchy age_hierarchy for age on customer as
level1: {young, middle_aged, senior} < level0: all
level2: {20, ..., 39} < level1: young
level2: {40, ..., 59} < level1: middle_aged
level2: {60, ..., 89} < level1: senior
May 5, 2015
16
Syntax for concept hierarchy

specification
(Cont.)
operation-derived hierarchies
define hierarchy age_hierarchy for age on customer as

{age_category(1), ..., age_category(5)} :=
cluster(default, age, 5) < all(age)
rule-based hierarchies
define hierarchy profit_margin_hierarchy on item as
level_1: low_profit_margin < level_0: all
if (price - cost)< $50
level_1: medium-profit_margin < level_0: all
if ((price - cost) > $50) and ((price - cost) <=
$250))
level_1: high_profit_margin < level_0: all
if (price - cost) > $250
May 5, 2015
17
Syntax for interestingness

measure specification
Interestingness measures and thresholds can be

specified by the user with the statement:
with <interest_measure_name> threshold =
threshold_value
Example:
with support threshold = 0.05
with confidence threshold = 0.7
May 5, 2015
18
Syntax for pattern presentation

and visualization specification
We have syntax which allows users to specify the

display of discovered patterns in one or more forms
display as <result_form>
To facilitate interactive viewing at different concept
level, the following syntax is defined:
Multilevel_Manipulation ::= roll up on
attribute_or_dimension
| drill down on attribute_or_dimension
| add attribute_or_dimension | drop
attribute_or_dimension
May 5, 2015
19
Putting it all together: the full

specification of a DMQL query
use database AllElectronics_db

use hierarchy location_hierarchy for B.address
mine characteristics as customerPurchasing
analyze count%
in relevance to C.age, I.type, I.place_made
from customer C, item I, purchases P, items_sold S,
works_at W, branch
where I.item_ID = S.item_ID and S.trans_ID = P.trans_ID
and P.cust_ID = C.cust_ID and P.method_paid =
``AmEx''
and P.empl_ID = W.empl_ID and W.branch_ID =
B.branch_ID and B.address = ``Canada" and
I.price >= 100
with noise threshold = 0.05
display as table
May 5, 2015
20
Other Data Mining

Languages &
Standardization Efforts
Association rule language specifications
MSQL (Imielinski & Virmani99)
MineRule (Meo Psaila and Ceri96)
Query flocks based on Datalog syntax (Tsur et al98)
OLEDB for DM (Microsoft2000)
Based on OLE, OLE DB, OLE DB for OLAP
Integrating DBMS, data warehouse and data mining
CRISP-DM (CRoss-Industry Standard Process for Data Mining)
Providing a platform and process structure for effective

data mining
Emphasizing on deploying data mining technology to

solve business problems
May 5, 2015
21
Designing Graphical User Interfaces

based on a data mining query
language
What tasks should be considered in the design GUIs

based on a data mining query language?
Data collection and data mining query

composition
Presentation of discovered patterns
Hierarchy specification and manipulation
Manipulation of data mining primitives
Interactive multilevel mining
Other miscellaneous information
May 5, 2015
22
Data Mining System

Architectures
Coupling data mining system with DB/DW system

No couplingflat file processing, not recommended
Loose coupling
Semi-tight couplingenhanced DM performance
Fetching data from DB/DW

Provide efficient implement a few data mining primitives in
a DB/DW system, e.g., sorting, indexing, aggregation,
histogram analysis, multiway join, precomputation of some
stat functions
Tight couplingA uniform information processing

environment
DM is smoothly integrated into a DB/DW system, mining

query is optimized based on mining query, indexing, query
processing methods, etc.
May 5, 2015
23
Summary
Five primitives for specification of a data mining task

task-relevant data
kind of knowledge to be mined
background knowledge
interestingness measures
knowledge presentation and visualization techniques
to be used for displaying the discovered patterns
Data mining query languages
DMQL, MS/OLEDB for DM, etc.
Data mining system architecture
No coupling, loose coupling, semi-tight coupling,
tight coupling
May 5, 2015
24

4chap4 BM

Uploaded by

Copyright:

Available Formats

4chap4 BM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4chap4 BM

Uploaded by

Copyright:

Available Formats

Data Mining:

Chapter 4: Data Mining Primitives,

A data mining query language

Design graphical user interfaces based on

Architecture of data mining systems

Why Data Mining Primitives

Finding all the patterns autonomously in a database?

What Defines a Data Mining Task

Type of knowledge to be mined

Pattern interestingness measurements

Visualization of discovered patterns

Task-Relevant Data (Minable

Database or data warehouse name

Database tables or data warehouse cubes

Condition for data selection

Relevant attributes or dimensions

Data grouping criteria

Types of knowledge to be mined

Other data mining tasks

E.g., rules, tables, crosstabs, pie/bar chart etc.

Concept hierarchy is also important

Discovered knowledge might be more understandable

Interactive drill up/down, pivoting, slicing and dicing

Different kinds of knowledge require different

A Data Mining Query

A DMQL can provide the ability to support ad-hoc

By providing a standardized language like SQL

Hope to achieve a similar effect like that SQL has on

DMQL is designed with the primitives described

Syntax for DMQL

Syntax for specification of

the kind of knowledge to be mined

concept hierarchy specification

pattern presentation and visualization

Putting it all together a DMQL query

Syntax for task-relevant data

use database database_name, or use

from relation(s)/cube(s)[where condition]

Syntax for specifying the kind of

Syntax for specifying the kind of

Syntax for concept hierarchy

To specify what concept hierarchies to use

Syntax for concept hierarchy

define hierarchy age_hierarchy for age on customer as

Syntax for interestingness

Interestingness measures and thresholds can be

Syntax for pattern presentation

We have syntax which allows users to specify the

Putting it all together: the full

use database AllElectronics_db

Other Data Mining

MSQL (Imielinski & Virmani99)

MineRule (Meo Psaila and Ceri96)

Query flocks based on Datalog syntax (Tsur et al98)

OLEDB for DM (Microsoft2000)

Based on OLE, OLE DB, OLE DB for OLAP

Integrating DBMS, data warehouse and data mining

CRISP-DM (CRoss-Industry Standard Process for Data Mining)

Providing a platform and process structure for effective