Build Decision Tree - Data Mining
Building and Developing a Decision Tree
for Premium Airlines Project
Build a Decision Tree, based on below information -
Start with “Mileage for each Leg”
Each leg (flight) will be under 500 miles or over 500 miles….
Then, Process 500 SkyMiles if leg is under 500 traveled miles and process actual miles if the leg is greater than 500 miles.
Was the ticket booked on the Web? If so, (process) add 100 (credit) miles to the actual miles.
Was the leg on a Saturday? If so, add 1.5 times plus 100 miles.
Is this the 5th leg of the month (or more)? If so, add triple mileage.
Store all customer’s data
See an example below on how to develop decision tree for the above assignment
Example for reference -
Example - Decision
tree.docx
Building and Developing a Decision Tree
for Premium Airlines
Example Only
Management said our slow travel days are on Tue, Wed, and Thur.
Our goal is to increase customers on our flights on those slow days.
Therefore, we will offer an increase in our promotional ‘SkyMiles’ program.
New Rules:
We will give a set amount of 500 SkyMiles on any flight less than 500 miles of distance (as the crow flies). Anything greater than 500 travel miles will be awarded 2 times SkyMiles on the travel distance – only on flights occurring Tuesday to Thursday.
Example: a typical one-way flight from Detroit to Houston is 639 travel miles. Therefore, we will award 639 miles X 2 to the customers’ SkyMiles account.
Note: On other travel days (Sun-Mon and Fri-Sat) our standard program applies; 1 travel mile = 1 SkyMiles. For every 25,000 SkyMiles the customer will receive a free ticket worth up to $500.00.
Below is an example of a decision tree on the above activity:
We will be using symbols to chart the processes.
Flow line / arrow marks the direction of the process flow
Decision /connector (Yes/No or T/F)
Processes block
Storage (a process block precedes storage)
Descriptive words are used inside or underneath each symbol. Note: Clear symbols are fine to use.
Steps:
1. Draft a chart based on the directions and/or scenario.
1. Use arrows to show the flow throughout.
1. Use Decision symbols when faced with a choice or when a decision must be made. They come before any process.
1. Use Processes.
1. Add names to all symbols
1. Is there clear logic on the flow?
1. Start to remove redundancy and compact the chart.
1. Come back to the chart the next day. The rest will allow you to see the chart differently and more clearly.
1. Reapply logic to the chart to make the chart clearer, shorter (to the point). There should No to very little redundancy of any processes / steps.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Yes / Over |
Miles X 2 |
|
|
|
|
|
|
|
Yes |
|
|
|
|
|
|
|
|
Customer |
|
|
|
Booked |
Is flight under /over 500 miles? |
No / under |
|
Info and Files are saved |
||
|
|
|
|
|
|
|
|
500 SkyMiles |
|
||
|
Buy's airline ticket |
|
Is Purchase on T-TH? |
|
|
|
|
|
|
|
|
|
|
|
|
No |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Standard SkyMiles program apply |
|
Info and Files are saved |
|
|