is documented and the results are analyzed.
2 BACKGROUND ON FUZZY
COMPARATORS
Classical comparison operators are "equal" (=),
"greater than" (>), "less than" (<), "greater than or
equal to" "less than or equal to" and "not
equal" These comparators are used to compare
numbers, texts and dates. Fuzzy comparators are an
extension of classical comparators, very useful for
fuzzy databases with fuzzy queries (Zadrozny et al.,
2008). The GEFRED model defines a type of
general comparator based on existing classical
comparators. The only requirement is that fuzzy
comparators should respect the results of classical
comparators when comparing crisp data. This
theoretical base was used by FSQL (Galindo et al.,
2008) to define a complete family of fuzzy
comparators (see Table 1).
Table 1: Fuzzy Comparators of FSQL.
Fuzzy
Comparator
Meaning
FEQ, NFEQ Possibly Equal, Necessarily Equal
FDIF, NFDIF
Possibly Fuzzy Different to,
Necessarily Fuzzy Different to
FGT, NFGT
Possibly Greater Than, Necessarily
Greater Than
FGEQ, NFGEQ
Possibly Greater or Equal, Necessarily
Greater or Equal
FLT, NFLT
Possibly Less Than, Necessarily Less
Than
FLEQ, NFLEQ
Possibly Less or Equal, Necessarily
Less or Equal
MGT, NMGT
Possibly Much Greater Than,
Necessarily Much Greater Than
MLT, NMLT
Possibly Much Less Than, Necessarily
Much Less Than
FSQL allows fuzzy comparators on unordered
underlying domains (of course, only FEQ, NFEQ,
INCL, and FINCL) for details.
Necessities comparators are more restrictive than
possibility ones, i.e. their fulfillment degree is
always lower than the fulfillment degree of their
corresponding possibility comparator. Note that
possibility comparators measure how possible it is
that the condition is satisfied, whereas necessity
comparators requires that the condition is satisfied in
some degree. Thus, necessity comparators do not
satisfy the reflexive property.
On the other hand, there are comparators whose
results include others. For example, in crisp mode,
the result of the comparator >= includes the result of
>. We can then say that the comparator > is more
restrictive than >=. This means that more restrictive
comparators will select a smaller or equal number of
tuples, and these selected tuples will never have a
greater fulfillment degree than with less restrictive
comparators.
3 PROPOSED LAYERS 1 AND 2
IN OUR APPLICATION
In order to validate our proposal, we used a case
study. The following describes the work done by
each layer proposal.
Layer 1: Our study database is Adventure Works
Cycles included in SQL Server 2008. In defining the
problem we used a partial data model data
warehouse. This was the input to the different
implementations of the Data Mining process. The
scenario selected was the Direct Mail, and three
algorithms were implemented: Decision Trees,
Clusters and Naive Bayes.
The indicator for this scenario is the best answer
from user’s point of view, i.e., how likely is that a
person with certain characteristics buys any offered
product. To be more specific: Which is the
probability that each customer buy a bicycle?. We
must analyze which of these three algorithms work
better. For this there is a tool called "Lift Chart"
which can be found under the tab "Data Mining
Accuracy Chart" from SQL Server.
Layer 2: For the Direct Mail Scenario and the
indicator as defined above, we apply the algorithm
that best fits our ideal model (perfect prediction). In
this case, we have chosen the Decision Tree
algorithm. We will make predictions with this
algorithm and, subsequent, classical and fuzzy
queries.
When using the Decision Trees algorithm to make
predictions, it generates a prediction query on a table
of cases. This query computes the probability that -
every person in the case table buy a product-. This
table of cases contains profiles of likely customers.
It stores the probability that each potential buyer
purchases a product (in this case a bicycle).
4 EXPERIMENTAL
ENVIRONMENT: LAYER 3
As a result of the Layer 2, the output data through
APPLYING FUZZY COMPARATORS ON DATA MINING
483