Difference between revisions of "ANLY482 AY2016-17 T2 Group 2 Project Overview Methodology"

From Analytics Practicum
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<!--Header Start-->
 
<!--Header Start-->
 
{|style="background-color:#6A8D9D; color: #F5F5F5; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
{|style="background-color:#6A8D9D; color: #F5F5F5; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color: #F5F5F5" width="10%" |
+
| style="padding:0.3em; font-size:100%; background-color:#466675; text-align:center; color: #F5F5F5" width="10%" |
[[ANLY482 AY2016-17 T2 Group 2|  
+
[[ANLY482_AY2016-17_T2_Group_2|  
 
<font color="#F5F5F5" size=2><b>HOME</b></font>]]
 
<font color="#F5F5F5" size=2><b>HOME</b></font>]]
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#466675; text-align:center; color:#F5F5F5" width="10%" |
 
[[ANLY482 AY2016-17 T2 Group 2 Project Overview|
 
<font color="#F5F5F5" size=2><b>PROJECT OVERVIEW</b></font>]]
 
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Findings|
+
[[ANLY482_AY2016-17_T2_Group_2 Findings|
 
<font color="#F5F5F5" size=2><b>FINDINGS</b></font>]]
 
<font color="#F5F5F5" size=2><b>FINDINGS</b></font>]]
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Project Documentation|
+
[[ANLY482_AY2016-17_T2_Group_2 Project Documentation|
 
<font color="#F5F5F5" size=2><b>PROJECT DOCUMENTATION</b></font>]]
 
<font color="#F5F5F5" size=2><b>PROJECT DOCUMENTATION</b></font>]]
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Project Management|
+
[[ANLY482_AY2016-17_T2_Group_2 Project Management|
 
<font color="#F5F5F5" size=2><b>PROJECT MANAGEMENT</b></font>]]
 
<font color="#F5F5F5" size=2><b>PROJECT MANAGEMENT</b></font>]]
 +
 +
| style="background:none;" width="1%" | &nbsp;
 +
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |
 +
[[ANLY482_AY2016-17_T2_Group_2 About Us|
 +
<font color="#F5F5F5" size=2><b>ABOUT US</b></font>]]
 +
 +
| style="background:none;" width="1%" | &nbsp;
 +
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |
 +
[[Main_Page|
 +
<font color="#F5F5F5" size=2><b>ANLY482 HOMEPAGE</b></font>]]
 
|}  
 
|}  
 
<!--Header End-->
 
<!--Header End-->
Line 47: Line 52:
 
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Tools Used</strong></font></div></div>==
 
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Tools Used</strong></font></div></div>==
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
<p>Based on the client requirements for the project, the programming language that we will be using is Python. Python has a mature and growing ecosystem of open-source tools for mathematics and data analysis. Jupyter Notebook is the best IDE for Python and data analytics. Some of the libraries that we will be venturing to are:
+
<p>For data preparation and EDA, the team chose to use JMP software as they are familiar with the usage of this software. To facilitate future extension of the project, the client requested for us to use R programming language for the final outcome. R has a mature and growing ecosystem of open-source tools for mathematics and data analysis.
* Python Natural Language Toolkit (NLTK)
 
* Scikit-learn
 
* TensorFlow
 
* pandas
 
 
</p>
 
</p>
 
</div>
 
</div>
Line 63: Line 64:
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Data Collection</strong><br></font>
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Data Collection</strong><br></font>
 
|}
 
|}
Kaisou will provide us with 3 datasets: musical data, concert data and customer profile data. The datasets consists of transaction records from both phone booking and internet booking channels as well as customer details records. Apart from the data provided, we will also look into collecting external data that may affect our analysis such as the dates of public holidays.
+
Kaiso provided us with transaction records on musical and concert data. These records consist of data from both phone booking and internet booking channels. Apart from these transaction datasets, Kaiso also provided us with customer demographics data and sports matches data. In total, we have obtained 9 datasets from them:
 +
#Lottery transaction data (lottery15.csv, lotteryAug-Oct.csv, lotteryRB.csv)
 +
#Sports transaction data (sports15.csv, sportsAug-Oct.csv, sportsRB.csv)
 +
#Sports matches data (Matches_Master.csv, League name.xlsx)
 +
#Customer demographics data (data_cst.xlsx)
 
</div>
 
</div>
  
<!--EDA Content-->
+
<!--Literature Review Content-->
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
 
{| color:#E6CCFF padding: 1px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
{| color:#E6CCFF padding: 1px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Exploratory Data Analysis (EDA)</strong><br></font>
+
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Literature Review</strong><br></font>
 
|}
 
|}
In the initial stage of this project, we will examine the dataset to have a better understanding of the various aspects of the dataset. This will also help us in the next stage of data preparation by identifying outliers and anomalies. Furthermore, we can perform normalization and transformation on the data if they are not consistent. We will also use EDA to help us identify important variables for subsequent steps such as correlation analysis.<br>
+
To gain more domain knowledge, we will seek to read up on research papers, articles and news related to our area of topic which is ticketing analytics. Furthermore, we aim to focus our reading on online ticketing because we will be using it as our basis when we perform our analysis. In addition, this will provide us with sufficient theoretical knowledge to conduct these analyses. <br>
Some of the analysis which we will look at are the frequencies of transactions for account holders in relation to the different bet types and the popular time of transaction, type of transaction and amount of transaction.
+
In this project, we will be conducting comparison analysis on the datasets. Thus, we will also be exploring on papers related to “cross-sectional analysis” and “longitudinal analysis” to aid us in our understanding of this two subjects.
 
</div>
 
</div>
  
Line 83: Line 89:
 
For outliers, we will first determine if the values are due to human or system error. If it is due to human or system error, we can safely remove that transaction from our analysis. Otherwise, we will conduct separate analysis of these outliers values.<br>
 
For outliers, we will first determine if the values are due to human or system error. If it is due to human or system error, we can safely remove that transaction from our analysis. Otherwise, we will conduct separate analysis of these outliers values.<br>
 
For missing values, we will determine the number of missing values. If the number is significant, we will use prediction techniques to predict these values based on the data set. Otherwise, we will remove these transactions from our analysis so that it will not affect our findings.<br>
 
For missing values, we will determine the number of missing values. If the number is significant, we will use prediction techniques to predict these values based on the data set. Otherwise, we will remove these transactions from our analysis so that it will not affect our findings.<br>
Lastly, we will perform data normalization and transformation. Some fields in the phone purchasing dataset and internet purchasing dataset have different scales and values even though they represent the same information. Also, due to system changes in Kaisou's IT infrastructure, there are some differences in the way the data is stored and named. Therefore, we will perform data normalization and transformation to ensure that values throughout both dataset are consistent before we can perform any analysis.  
+
Lastly, we will perform data normalization and transformation. Some fields in the phone purchasing dataset and internet purchasing dataset have different scales and values even though they represent the same information. Also, due to system changes in Kaiso's IT infrastructure, there are some differences in the way the data is stored and named. Therefore, we will perform data normalization and transformation to ensure that values throughout both dataset are consistent before we can perform any analysis.  
 
</div>
 
</div>
  
<!--Association Rule Content-->
+
<!--EDA Content-->
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 
{| color:#E6CCFF padding: 1px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
{| color:#E6CCFF padding: 1px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Association Rule Mining</strong><br></font>
+
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Exploratory Data Analysis (EDA)</strong><br></font>
 
|}
 
|}
Association rule mining is a rule-based method to discover interesting relations in the dataset. We will conduct analysis on the betting transactions to determine betting patterns, which are known as rules, between customers and the different betting channels. These rules can then be used by Singapore Pools as the basis for marketing strategies for their products.
+
In the initial stage of this project, we will examine the dataset to have a better understanding of the various aspects of the dataset. We will then proceed to perform comparison studies between the datasets. The purpose of the comparison studies is to identify any behavioral differences among the customers. There are two studies which we will be doing - cross-sectional analysis and longitudinal analysis. Some of the comparisons which we will be looking at for both analyses are the frequencies of transactions for account holders in relation to the different ticketing types, the popular time of transaction, type of transaction and amount per transaction.<br>
</div>
+
<br>
 
+
<u>Cross-sectional Analysis</u><br>
<!--Correlation Analysis Content-->
+
In this analysis, we will perform comparison study on customers in the same time period of 2015 and 2016. We have 2 months of data for 2016 and will be subsetting the 2015 dataset to contain records from the same time period only. <br>
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
+
The purpose of using the same time period for both years is to eliminate any seasonal fluctuations that exists in the datasets. <br>
{| color:#E6CCFF padding: 1px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
+
<br>
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Correlation Analysis </strong><br></font>
+
<u>Longitudinal Analysis</u><br>
|}
+
For this analysis, we will be examining the behavioral change of old customers that bought tickers before and after the launch of the online ticketing channel. This analysis aims to answer the question on whether customers purchasing behaviour changed after the launch. Hence, we will filter out data records to include only old customers (customers who registered before the launch). <br>
We will perform correlation analysis and observe the interactions of various variables, which we have identified from EDA, with the bet amount. From the correlation coefficient, we will be able to determine the strengths of these relationships and find out does these relationships correlate to the betting patterns for both betting channels.
+
We will be doing comparisons on data two months before and two months after the launch of the online ticketing site.
 
</div>
 
</div>
  
Line 107: Line 113:
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Dashboard</strong><br></font>
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Dashboard</strong><br></font>
 
|}
 
|}
Following the analysis that was carried out, a dashboard will be built to aid in the visualization of the findings. The dashboard will showcase the important variables and its interactions with customer purchasing behaviour. This will be an easy way for the customer engaging teams to use and understand specific behaviours of their customers.
+
Following the analysis, an analytical dashboard will be built to visualize our findings. The dashboard will display the key variables of the data and how they affect the customer purchasing behaviour. The customer engaging teams would be able to utilize the dashboard to display and better understand the differences between the customer behaviours before and after the launch of the new system.<br>
 +
The dashboard will use a framework that allows Kaiso to update their dashboard by uploading their dataset every time they have a new dataset. Design, statistics and visualization will be our main considerations when building the dashboard so that they can easily unveil the differences that they are looking for.
 +
 
 
</div>
 
</div>
  
Line 115: Line 123:
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Recommendations & Insights</strong><br></font>
 
| style="padding:0.3em; font-family:helvetica; font-size:100%; border-bottom:2px solid #626262; border-left:2px #66FF99; text-align:left;" width="20%" | <font color="#000000" size="3em"><strong>Recommendations & Insights</strong><br></font>
 
|}
 
|}
From our analysis and dashboard, we seek to assist Kaisou in understanding the characteristics of their customers. We will be proposing business strategies and recommendations to them based on the insights that we have uncovered.
+
From our analysis and dashboard, we seek to assist Kaiso in understanding the characteristics of their customers. We will be proposing business strategies and recommendations to them based on the insights that we have uncovered.
 
</div>
 
</div>

Latest revision as of 20:09, 19 February 2017


HOME

 

FINDINGS

 

PROJECT DOCUMENTATION

 

PROJECT MANAGEMENT

 

ABOUT US

 

ANLY482 HOMEPAGE

Background Data Source Methodology


Tools Used

For data preparation and EDA, the team chose to use JMP software as they are familiar with the usage of this software. To facilitate future extension of the project, the client requested for us to use R programming language for the final outcome. R has a mature and growing ecosystem of open-source tools for mathematics and data analysis.

Methodology

Data Collection

Kaiso provided us with transaction records on musical and concert data. These records consist of data from both phone booking and internet booking channels. Apart from these transaction datasets, Kaiso also provided us with customer demographics data and sports matches data. In total, we have obtained 9 datasets from them:

  1. Lottery transaction data (lottery15.csv, lotteryAug-Oct.csv, lotteryRB.csv)
  2. Sports transaction data (sports15.csv, sportsAug-Oct.csv, sportsRB.csv)
  3. Sports matches data (Matches_Master.csv, League name.xlsx)
  4. Customer demographics data (data_cst.xlsx)
Literature Review

To gain more domain knowledge, we will seek to read up on research papers, articles and news related to our area of topic which is ticketing analytics. Furthermore, we aim to focus our reading on online ticketing because we will be using it as our basis when we perform our analysis. In addition, this will provide us with sufficient theoretical knowledge to conduct these analyses.
In this project, we will be conducting comparison analysis on the datasets. Thus, we will also be exploring on papers related to “cross-sectional analysis” and “longitudinal analysis” to aid us in our understanding of this two subjects.

Data Preparation

Before performing any further data analysis, the first step is to prepare the data. We will clean the data to handle outliers and missing values. In addition, we will perform data normalization and transformation on the given dataset.
For outliers, we will first determine if the values are due to human or system error. If it is due to human or system error, we can safely remove that transaction from our analysis. Otherwise, we will conduct separate analysis of these outliers values.
For missing values, we will determine the number of missing values. If the number is significant, we will use prediction techniques to predict these values based on the data set. Otherwise, we will remove these transactions from our analysis so that it will not affect our findings.
Lastly, we will perform data normalization and transformation. Some fields in the phone purchasing dataset and internet purchasing dataset have different scales and values even though they represent the same information. Also, due to system changes in Kaiso's IT infrastructure, there are some differences in the way the data is stored and named. Therefore, we will perform data normalization and transformation to ensure that values throughout both dataset are consistent before we can perform any analysis.

Exploratory Data Analysis (EDA)

In the initial stage of this project, we will examine the dataset to have a better understanding of the various aspects of the dataset. We will then proceed to perform comparison studies between the datasets. The purpose of the comparison studies is to identify any behavioral differences among the customers. There are two studies which we will be doing - cross-sectional analysis and longitudinal analysis. Some of the comparisons which we will be looking at for both analyses are the frequencies of transactions for account holders in relation to the different ticketing types, the popular time of transaction, type of transaction and amount per transaction.

Cross-sectional Analysis
In this analysis, we will perform comparison study on customers in the same time period of 2015 and 2016. We have 2 months of data for 2016 and will be subsetting the 2015 dataset to contain records from the same time period only.
The purpose of using the same time period for both years is to eliminate any seasonal fluctuations that exists in the datasets.

Longitudinal Analysis
For this analysis, we will be examining the behavioral change of old customers that bought tickers before and after the launch of the online ticketing channel. This analysis aims to answer the question on whether customers purchasing behaviour changed after the launch. Hence, we will filter out data records to include only old customers (customers who registered before the launch).
We will be doing comparisons on data two months before and two months after the launch of the online ticketing site.

Dashboard

Following the analysis, an analytical dashboard will be built to visualize our findings. The dashboard will display the key variables of the data and how they affect the customer purchasing behaviour. The customer engaging teams would be able to utilize the dashboard to display and better understand the differences between the customer behaviours before and after the launch of the new system.
The dashboard will use a framework that allows Kaiso to update their dashboard by uploading their dataset every time they have a new dataset. Design, statistics and visualization will be our main considerations when building the dashboard so that they can easily unveil the differences that they are looking for.

Recommendations & Insights

From our analysis and dashboard, we seek to assist Kaiso in understanding the characteristics of their customers. We will be proposing business strategies and recommendations to them based on the insights that we have uncovered.