Customer Relationship Management (CRM) System

By
Chew Zhen Yong

A REPORT
SUBMITTED TO
Universiti Tunku Abdul Rahman
In partial fulfillment of the requirements
For the degree of
BACHELOR OF INFORMATION TECHNOLOGY (HONS)
INFORMATION SYSTEM ENGINEERING
Faculty of Information and Communication Technology
(PERAK CAMPUS)

JANUARY 2014
 UNIVERSITI TUNKU ABDUL RAHMAN

REPORT STATUS DECLARATION FORM

Title: __________________________________________________________
__________________________________________________________

Academic Session: _____________

I __________________________________________________________
(CAPITAL LETTER)

declare that I allow this Final Year Project Report to be kept in

Universiti Tunku Abdul Rahman Library subject to the regulations as follows:
1. The dissertation is a property of the Library.
2. The Library is allowed to make copies of this dissertation for academic purposes.
Verified by,

_________________________ _________________________
(Author’s signature) (Supervisor’s signature)

Address:
__________________________
__________________________ _________________________
__________________________ Supervisor’s name

Date: _____________________ Date: ____________________

 Customer Relationship Management (CRM) System
By
Chew Zhen Yong

A REPORT
SUBMITTED TO
Universiti Tunku Abdul Rahman
In partial fulfillment of the requirements
For the degree of
BACHELOR OF INFORMATION TECHNOLOGY (HONS)
INFORMATION SYSTEM ENGINEERING
Faculty of Information and Communication Technology
(PERAK CAMPUS)

JANUARY 2014
 DECLARATION OF ORIGINALITY

I declare that this report entitled “Customer Relationship Management (CRM) System”
is my own work except as cited in the references. The report has not been accepted for
any degree and is not being submitted concurrently in candidature for any degree or other
award.

Signature : _________________________

Name : _________________________

Date : _________________________

BIS (Hons) Information System Engineering ii

Faculty of Information and Communication Technology (Perak Campus), UTAR
 Acknowledgement

First, I would like to convey thanks to supervisor, Mr Tan Teik Boon, through the
duration of completing this Project II would not be done perfectly without his guidance
and assistance. The project also helps me to understand more about the Customer
Relationship Management (CRM) system.

I would like to think my family for their support and encouragement as well as love that
helped me gets through UTAR. This project would not have been possible without them.

Finally, I would like to convey thanks to Faculty of Information Technology too, for
providing the facilities such as computer laboratory and Internet Services in UTAR to
facilitate the work.

BIS (Hons) Information System Engineering iii

Faculty of Information and Communication Technology (Perak Campus), UTAR
 Abstract
This is a project to develop a Customer Relationship Management (CRM) system. CRM
is one of the systems included in Enterprise Resource Planning (ERP) System. The main
purpose of CRM is to improve the relationship with the customers by using different
module like analysis, customer service and others. The objective to do this project is to
develop a system which can help the organizations to decrease their defection rate of
customers. Because the lower defection rate means the bigger customer base, which lead
to more profit for the organization.

CRM in this project is included few modules. The modules included are customer
filtering, customer profiling and promotion tools. Customer filtering allows the user filter
out a customer list from the customer database by using customer’s demographic
information. Customer profiling to makes each customer is having a profile; the user may
see the customer’s profile included analysis of customer. Promotion Tools allows the user
can create new promotion base on the product, and filter list of customer to promote the
promotion. After that, the user can see the analysis of the performance of the promotion.
The tools used to develop this CRM included PHP, Web server, Mysql, javascript,
HTML, CSS, jquery and jquery’s plugin.

BIS (Hons) Information System Engineering iv

Faculty of Information and Communication Technology (Perak Campus), UTAR
Table of Contents

Title...................................................................................................................................... i

DECLARATION OF ORIGINALITY ........................................................................... ii

Acknowledgement ............................................................................................................ iii

Abstract ............................................................................................................................. iv

Table of Contents .............................................................................................................. v

List of Tables .................................................................................................................... ix

List of Figures .................................................................................................................. xii

List of Abbreviations ..................................................................................................... xiv

Chapter 1 Introduction..................................................................................................... 1

1-1 Motivation and Problem Statement ............................................................ 1

1-2 Project Scope .............................................................................................. 2

1-3 Project Objectives ....................................................................................... 3

1-4 Impact, Significant and Contribution ......................................................... 4

1-5 Background Information............................................................................. 5

1-5-1 Customer ................................................................................. 5

1-5-2 Customer Relationship............................................................ 5

1-5-3 Customer Relationship Management (CRM) ......................... 6

1-5-4 Important of Customer Relationship Management (CRM) .... 6

BIS (Hons) Information System Engineering v

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review ........................................................................................... 8

2-1 Introduction ................................................................................................ 8

2-2 Customer Relationship Management (CRM) ............................................. 9

2-2-1 Definition of CRM .................................................................. 9

2-2-2 Types of CRM ...................................................................... 10

2-3 Customer Segmentation ............................................................................ 13

2-3-1 What is customer segmentation? .......................................... 13

2-3-2 How to segment the customers? ........................................... 13

2-4 Solution by others ..................................................................................... 16

2-5 Features benchmarking of existing systems ............................................. 17

Chapter 3 System Development ..................................................................................... 26

3-1 Methodology............................................................................................. 26

3-2 Tools ......................................................................................................... 27

3-3 Implementation Issues and Challenges..................................................... 29

3-4 Timeline .................................................................................................... 30

3-5 Requirement Specification ....................................................................... 31

3-5-1 Security Features .................................................................. 31

3-5-2 Analysis ................................................................................ 31

3-5-3 Promotion Tools ................................................................... 32

Chapter 4 System and Interface Design........................................................................ 34

BIS (Hons) Information System Engineering vi

Faculty of Information and Communication Technology (Perak Campus), UTAR
 4-1 System Design .......................................................................................... 34

4-2 Interface Design ........................................................................................ 36

4-3 Activity Diagram ...................................................................................... 38

4-4 Functional Page Design ............................................................................ 39

4-5 Entity Relationship Diagram .................................................................... 63

4-5-1 Customer Detail .................................................................... 64

4-5-2 User Account ........................................................................ 65

4-5-3 Transaction Detail ................................................................. 66

4-5-4 Product Detail ....................................................................... 67

4-5-5 Promotion ............................................................................. 68

4-6 Data Dictionary......................................................................................... 69

Chapter 5 System Testing .............................................................................................. 79

5-1 Unit Testing .............................................................................................. 79

5-2 Functional Testing .................................................................................... 92

Chapter 6 Discussion and Conclusion ......................................................................... 111

6-1 Project Review ........................................................................................ 111

6-2 Strength and Limitation .......................................................................... 111

6-3 Future Enhancement ............................................................................... 112

References ...................................................................................................................... 113

Bibliography .................................................................................................................. 114

BIS (Hons) Information System Engineering vii

Faculty of Information and Communication Technology (Perak Campus), UTAR
APPENDIX A Turnitin Report ....................................................................................... 1

BIS (Hons) Information System Engineering viii

Faculty of Information and Communication Technology (Perak Campus), UTAR
List of Tables
Table 1-5-4 T1 Customer Defection Rate and Customer Base........................................... 7
Table 2-5 T1 Benchmarking of different CRM systems .................................................. 25
Table 3-4 T1 Gantt Chart of System Development .......................................................... 30
Table 4-6 T1 customer_detail Entity ................................................................................ 69
Table 4-6 T2 list_race Entity ............................................................................................ 69
Table 4-6 T3 list_gender Entity ........................................................................................ 70
Table 4-6 T4 list_outlet Entity .......................................................................................... 70
Table 4-6 T5 list_city Entity ............................................................................................. 70
Table 4-6 T6 list_state Entity............................................................................................ 71
Table 4-6 T7 user_role Entity ........................................................................................... 71
Table 4-6 T8 user_account Entity ..................................................................................... 71
Table 4-6 T9 role_page Entity .......................................................................................... 72
Table 4-6 T10 system_page Entity ................................................................................... 72
Table 4-6 T11 system_page_type Entity .......................................................................... 72
Table 4-6 T12 transaction_detail Entity ........................................................................... 73
Table 4-6 T13 transaction_item Entity ............................................................................. 73
Table 4-6 T14 list_product_main Entity ........................................................................... 73
Table 4-6 T15 list_product_second Entity........................................................................ 74
Table 4-6 T16 list_product_third Entity ........................................................................... 74
Table 4-6 T17 list_company Entity .................................................................................. 74
Table 4-6 T18 list_product Entity ..................................................................................... 75
Table 4-6 T19 promotion Entity ....................................................................................... 75
Table 4-6 T20 promotion_outlet Entity ............................................................................ 76

BIS (Hons) Information System Engineering ix

Faculty of Information and Communication Technology (Perak Campus), UTAR
Table 4-6 T21 promotion_target Entity ............................................................................ 76
Table 4-6 T22 promotion_target_feedback Entity ............................................................ 76
Table 4-6 T23 promotion_target_action Entity ................................................................ 77
Table 4-6 T24 promotion_action Entity ........................................................................... 77
Table 4-6 T25 list_phone_call Entity ............................................................................... 77
Table 4-6 T26 list_email Entity ........................................................................................ 78
Table 4-6 T27 list_sms Entity ........................................................................................... 78
Table 5-1 T1Unit Test 1: Login as administrator or users ................................................ 81
Table 5-1 T2 Unit Test 2: Register Customer ................................................................... 82
Table 5-1 T3 Unit Test 3: Change User Password ........................................................... 84
Table 5-1 T4 Unit Test 4: Insert new role......................................................................... 84
Table 5-1 T5 Unit Test 5: Insert new page ....................................................................... 85
Table 5-1 T6 Unit Test 6: Add new user .......................................................................... 86
Table 5-1 T7 Unit Test 7: Add new Promotion ................................................................ 91
Table 5-2 T1 Functional Test 1: Login with different roles ............................................. 93
Table 5-2 T2 Functional Test 2: Create and Update User ............................................... 94
Table 5-2 T3 Functional Test 3: Create and Update Role in System ............................... 96
Table 5-2 T4 Functional Test 4: Create and Update System Page ................................... 97
Table 5-2 T5 Functional Test 5: Change user password................................................... 99
Table 5-2 T6 Functional Test 6: Customer Filtering and Profiling ................................ 100
Table 5-2 T7 Functional Test 7: Product Analysis Testing ............................................ 102
Table 5-2 T8 Functional Test 8: Create and Update Promotion ..................................... 105
Table 5-2 T9 Functional Test 9: Select Promotion Target Customer ............................ 107

BIS (Hons) Information System Engineering x

Faculty of Information and Communication Technology (Perak Campus), UTAR
Table 5-2 T10 Functional Test 10: Sending promotion to customer and Getting Respond
......................................................................................................................................... 110
Table 5-2 T11 Functional Testing 11: Promotion performance ..................................... 110

BIS (Hons) Information System Engineering xi

Faculty of Information and Communication Technology (Perak Campus), UTAR
List of Figures
Figure 2-2-2 F1 Types of Customer Relationship Management (CRM) .......................... 12
Figure 2-4 F1 Logo of SAS ERP system .......................................................................... 16
Figure 3-1 F1 Methodology of system development ........................................................ 26
Figure 3-2 F1 Development tools ..................................................................................... 28
Figure 4-1 F1 System Algorithm ...................................................................................... 35
Figure 4-2 F1 Interface Design ......................................................................................... 36
Figure 4-2 F2 Header design............................................................................................. 37
Figure 4-2 F3 Navigation Bar Design ............................................................................... 37
Figure 4-2 F4 Footer Design ............................................................................................. 37
Figure 4-3 F1 Activity Diagram of Promotion ................................................................. 38
Figure 4-4 F1 Customer Registration Page ....................................................................... 39
Figure 4-4 F2 Login Page ................................................................................................. 39
Figure 4-4 F 3 Change Password Page ............................................................................. 40
Figure 4-4 F4 Role List Page ............................................................................................ 40
Figure 4-4 F5 New Role Page ........................................................................................... 41
Figure 4-4 F6 New User Page ........................................................................................... 41
Figure 4-4 F7 Internal User List Page............................................................................... 42
Figure 4-4 F8 Page List..................................................................................................... 43
Figure 4-4 F9 New Page Form.......................................................................................... 44
Figure 4-4 F10 Customer Filter Page................................................................................ 45
Figure 4-4 F11 Customer Filter Result Page .................................................................... 46
Figure 4-4 F12 Customer Profile ...................................................................................... 47
Figure 4-4 F 13 Product Selection Page ........................................................................... 48

BIS (Hons) Information System Engineering xii

Faculty of Information and Communication Technology (Perak Campus), UTAR
Figure 4-4 F 14 Product Analysis Page ............................................................................ 49
Figure 4-4 F15 New Promotion Page ............................................................................... 50
Figure 4-4 F16 Customer Filter Page (Promotion) ........................................................... 51
Figure 4-4 F 17 Customer Filter Result (Promotion)........................................................ 52
Figure 4-4 F18 Promotion List Page ................................................................................. 53
Figure 4-4 F19 Promotion Detail Page (Manager) ........................................................... 54
Figure 4-4 F20 Promotion Performance Page .................................................................. 55
Figure 4-4 F 21 Assigned Task Page (Promoter).............................................................. 56
Figure 4-4 F22 Promotion Detail Page ............................................................................. 57
Figure 4-4 F23 Email Template ........................................................................................ 58
Figure 4-4 F24 Phone Call Template ................................................................................ 59
Figure 4-4 F25 SMS Template ......................................................................................... 59
Figure 4-4 F26 Offered Promotion Page .......................................................................... 60
Figure 4-4 F27 Promotino Detail Page (Customer) .......................................................... 61
Figure 4-4 F28 Transaction History Page ......................................................................... 62
Figure 4-5 F1 Entity Relationship Diagram (ERD) .......................................................... 63
Figure 4-5-1 F1 Customer Detail ERD ............................................................................. 64
Figure 4-5-2 F1 User Account ERD ................................................................................. 65
Figure 4-5-3 F1 Transaction Detail ERD.......................................................................... 66
Figure 4-5-4 F1 Product Detail ......................................................................................... 67
Figure 4-5-5 F1 Promotion ERD ...................................................................................... 68
Figure A-1-F1 Turnitin Report ....................................................................................... A-1

BIS (Hons) Information System Engineering xiii

Faculty of Information and Communication Technology (Perak Campus), UTAR
List of Abbreviations
CRM Customer Relationship Management

BIS (Hons) Information System Engineering xiv

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

Chapter 1 Introduction
1-1 Motivation and Problem Statement
“Top Indian telecoms carrier Bharti Airtel lost almost 1 million mobile customers
in September, data released by an industry body showed, as carriers in the world's
second-biggest wireless services market continue to disconnect inactive users in a
clean-up drive.” (Airtel, Vodafone Idea Lose Cell Users,2012)
Losing customer is a problem facing by every organization. Why customer was
turnover? There are many reasons for a customer to turnover such as wrong
product pricing, poor store atmosphere, lack of product knowledge, terrible
customer service and other. One of the fundamental reasons of customer to
turnover is weak relationship with the customer. A weak relationship with
customers is impossible to have high loyalty customers. Customer will always
like the company make them feel better, and they will be loyal to those company.
All of the companies having the customer defection rate, they must have a
solution to decrease their customer defection rate. The tool to decrease the
customer defection rate is customer relationship management (CRM). CRM can
help the company to identified, acquire, satisfy and retain profitable customers
from existing customer base.
Why the problem of losing customer is important? The losing of customer also
means that the profit of the company was decrease. In other words, decrease the
customer defection will increase company’s profit at all.

BIS (Hons) Information System Engineering 1

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

1-2 Project Scope

Scope of this project is to deliver a customer relationship management (CRM)
system to track the customers’ status. This CRM system will include the module
such as analysis, emailing, user control, promotion management. This CRM
system will be a web base application which the user can access through most of
the internet browser available in the market.
By using the analysis module, marketer is able to analyze the market easier. After
analyzed the market, the marketer was able to generate a list customers by
selecting parameters. For examples, the marketer user can generate a list of
customer who was continuous decreasing their monthly purchase amount.

BIS (Hons) Information System Engineering 2

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

1-3 Project Objectives

The project’s product will let user to create a simple analysis. For example, the
user should able to create an analysis of the ratio of male customers to females
customer or a bar graph to show that the differences of number of customers at
different states.
The CRM system shall provide the page permission control. The user only can
access to the pages which they are permitted. The permission control is based on
user group management.
The CRM system shall provide single customer profile. In the customer profile, it
should include the information such as customer’s demographic data, purchase
history, habit analysis and others. The habit analysis is included customer feature
product, average monthly purchase amount and others.
The CRM shall provide the promotion management. The promotion management
should include create, modify and deliver the promotion to customers. Beside this,
the promotion management also should be able to detect the respond of customer
based on the promotion and analyze the respond.

BIS (Hons) Information System Engineering 3

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

1-4 Impact, Significant and Contribution

By having this customer software, the organization will able to track the customers fulfill
their parameter. The organization can easily find out the customer by filtering their data.
For example, if the organization is promoting a new product and target the customer who
was female, single state and having income between RM3,000 and RM5,000, this system
would it to target the possible buyer even the best location which having the largest
number of possible buyer. With this customer filtering module, the marketer may also
find out the customer who was decreasing their monthly purchase month by month, then
they may carry out the strategy to increase the loyalty of these possible leave customer.

Beside the customer filtering system, this system may also let the user to see the
relationship between the customer and the organization. So the employee can respond the
customer as soon as possible because they can get the customer information in one page.

BIS (Hons) Information System Engineering 4

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

1-5 Background Information

1-5-1 Customer
A customer is a person or organization that a marketer believes will earn benefit from the
goods and service offered by the marketer’s organization. A customer is not necessary to
be currently buying something, and it may differentiate into 3 types. The 3 types of
customer are existing customer, former customer and potential customer. Existing
customer is the customer who purchasing the goods and services within a period till now.
Former customer is customer who purchased goods services before, but not continues for
a period time. Potential customer is the customer who hasn’t purchase, buy they may
purchase.

1-5-2 Customer Relationship

A relationship is composed of a series of interactive episodes between dyadic parties over
time. (Buttle 2008,p27)

What is an interactive episode? Episode is activity that having a start time and end time,
and it is nameable. There is possibility a series of episode in a sales representative and
customer relationship. For example, making a sales call, making a purchase, dealing with
a complaint and others. If there is only one-off transaction, such as buying a coffee from
the coffee shop, it will not call as a relationship. But, if a customer frequently going to
enjoy the coffee of the same coffee because the waitress’s service of the coffee shop is
nice, then it might a customer relation. A customer relationship should be in long period
interaction but not once transaction.

BIS (Hons) Information System Engineering 5

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

1-5-3 Customer Relationship Management (CRM)

Customer Relationship Management (CRM) is the core business strategy that integrates
internal processes and functions, and external networks, to create and deliver value to
targeted customers at a profit. It is grounded on high quality customer-related data and
enabled by information technology. (Buttle 2008,p15)

1-5-4 Important of Customer Relationship Management (CRM)

The fundamental reason for an organization wants to have relationship with customer is
economic. The main objectives of CRM are identified, acquire, satisfy and retain
profitable customers. Companies can do better when they achieved the objectives of
CRM. Improve customer retention rate or decrease customer defection rate will affect the
increasing of the size of customer base. Base on the Table 1-5-4 T1, company A with
lower defection rate will obtain bigger size of customer base in future.

BIS (Hons) Information System Engineering 6

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 1 Introduction

Company A (5% defection rate) Company B (10% defection rate)

Existing New Total Existing New Total

Year customer customers customer customer customer customer

base base

2001 1000 100 1100 1000 100 1100

2002 1045 100 1145 990 100 1090

2003 1088 100 1188 981 100 1081

2004 1129 100 1229 973 100 1073

2005 1168 100 1268 966 100 1066

Table 1-5-4 T1 Customer Defection Rate and Customer Base

BIS (Hons) Information System Engineering 7

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Chapter 2 Literature Review

2-1 Introduction
In this literature review, This project going to review on the article, book and internet
resources to study about the customer relationship management (CRM), customer
segmentation and also the solution provided by others.

BIS (Hons) Information System Engineering 8

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

2-2 Customer Relationship Management (CRM)

2-2-1 Definition of CRM
The expression of Customer Relationship Management (CRM) was being started to use
since early 1990s. According to Customer Relationship Management: Concepts and
Technologies (Buttle 2008), there are many attempts to define the domain of CRM:

CRM is an information industry term for methodologies, software and usually internet
capabilities that help an enterprise manage customer relationships in an organized way.

CRM also define as the process of managing all aspects of interaction a company has
with its customers, including prospecting, sales and service.

CRM is an integrated approach to identifying, acquiring and retaining customers. By

enabling organizations to manage and coordinate customer interactions across multiple
channels, departments, lines of business and geographies, CRM helps organizations
maximize the value of every customer interaction and drive superior corporate
performance.

CRM is an integrated information system that is used to plan, schedule and control the
pre-sales and post-sales activities in an organization. CRM embraces all aspects of
dealing with prospects and customers, including the call centre, sales-force, marketing,
technical support and field service. The primary goal of CRM is to improve long-term
growth and profitability through a better understanding of customer behavior. CRM aims
to provide more effective feedback and improved integration to better gauge the return on
investment (ROI) in these areas.

BIS (Hons) Information System Engineering 9

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

CRM is a business strategy that maximizes profitability, revenue and customer

satisfaction by organizing around customer segments, fostering behavior that satisfies
customers and implementing customer centric processes.

2-2-2 Types of CRM

There are 4 types of CRM implemented overall the business. There are Strategic CRM,
operational CRM, Analytical CRM, and Collaborative CRM.

Strategic CRM is use to development a business with customer centric culture. This
culture is dedicated to winning and keeping customers by creating and delivering better
value than the competitors. Customer centricity is compete with 3 others business logic,
which is product, production and sales. Product-oriented businesses believe that the
product with best quality, performance, design or features will be chosen by customer.
Production-oriented businesses believe that customer more likely to choose low cost
product. Sales-oriented businesses believe that customer will be persuaded to buy their
product if they do enough for advertising, selling and public relation. A customer or
market-oriented businesses share a set of belief putting the customer at first. Many
managers say that customer centric must be right. However, sometime other orientation
may stronger.

Operational CRM use to automate and improves customer-facing and customer-

supporting business process. CRM application can make the marketing, selling, and
service process to be automated and integrated. There are 3 types of automation, which
are Marketing automation, sales-force automation and service automation. Marketing

BIS (Hons) Information System Engineering 10

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

automation allow marketer to use customer data to develop, execute and evaluate targeted
communication and offers. Sales-force automation is use to managing selling activities,
product configuration in sales-force automation allow customer to design their product by
themselves, one of the example is the web-based laptop setting configuration and orders
features offer by the DELL. Service automation is used to automate the serving service of
the company, it was used widely by most of the company. For example, when customer
call to the customer support centre of the companies, they will first ask us to use voice or
keyboard to enter the option customer want, then lead us to the related service provider.

Analytical CRM is concerned with capturing, storing, extracting, integrating, processing,

interpreting, distributing, using and reporting customer-related data to enhance both
customer and company value. Analytical CRM normally can use to answer the marketing
question of the businesses such as who is our most profitable customer? Which customer
having the possibility of turnover to the competitor? Which customer have the high
possibility to accept our offer? Analytical can help to them to know which customer
should give which level of services, and this could increase the possibility of customer to
accept the offer.

Collaborative CRM is the term used to describe the strategic and tactical alignment of
normally separate enterprises in the supply chain for the more profitable identification,
attraction, retention and development of customers. (Buttle 2008,p11)

BIS (Hons) Information System Engineering 11

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Strategic Operational

CRM

Analytical Collarorative

Figure 2-2-2 F1 Types of Customer Relationship Management (CRM)

BIS (Hons) Information System Engineering 12

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

2-3 Customer Segmentation

2-3-1 What is customer segmentation?
What is customer segmentation? The purpose of segmentation is the concentration of
marketing energy and force on the subdivision (or the market segment) to gain a
competitive advantage within the segment (Jerry 2007). Marketer can make the company
to gain the competitive advantage through the customer segmentation progress. The
marketing segmentation is use to segment the customer who sharing something in
common which is similarity. There are few types of segmentation which included
geographic segmentation, distribution segmentation, media segmentation, price
segmentation, demographic segmentation, time segmentation, and psychographic or
lifestyle segmentation.

2-3-2 How to segment the customers?

The market segmentation is mentioned as being one of the key elements of modern
marketing and is, as mentioned, the process of dividing the market into several groups
and/or segment(s) based on factors such as demographic, geographic, psychological and
behavioral factors. By doing so the marketers will have a better understanding of their
target audience and thereby make their marketing more effective (Gunter and Furnham
1992, p1). Some of the variables used to segment customer will list and explain in
following.

Demographic Segmentation- The demographic segmentation divides customers into

segments based on demographic values such as age, gender, family size, family life cycle,

BIS (Hons) Information System Engineering 13

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

income, occupation, education, religion, race, generation, social class and nationality
(Armstrong and Kotler 2005, p187). Following is some of the example of segmentation
based on the demographic values.

1. Age and life-cycle segmentation.

2. Gender segmentation.
3. Income segmentation.
4. Generation segmentation.
5. Social class segmentation.

Geographic Segmentation- The geographic segmentation divides customers into

segments based on geographical areas such as nations, states, regions, counties, cities or
neighborhoods. A company can target one or more areas and must be aware of the fact
that data according to geographic segmentation may vary due to population shift (Pickton
and Broderick 2005, p376).

Psychographic Segmentation- The psychological variables derive from two principal

types of customer; personality profiles and lifestyle profiles (psychographics).
Psychological profiles are often used as a supplement to geographic and demographics
when these does not provide a sufficient view of the customer behaviour. While the
traditional geographical and demographical bases (sex, age, income etc.)provide the
marketer with accessibility to customer segments, the psychological variables provide
additional information about these and enhance the understanding of the behaviour of
present and potential target markets (Gunter and Furnham, 1992: 26).

BIS (Hons) Information System Engineering 14

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Behavioral Segmentation- Behavioural segmentation is based on the customers’ attitude

toward, use of, or response to a product. Many marketers believe that the behavioural
variables such as occasions, benefits, user status, usage rate, buyer-readiness stage,
loyalty status and attitude are the best starting points for constructing market segments
and thus these variables will be described further in the following (Kotler and Keller,
2009: 263).

BIS (Hons) Information System Engineering 15

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

2-4 Solution by others

To solve the problem of losing customer, the fundamental way is to increase the retention
rate of the customers. SAS Institutes had found some approach to increase the
profitability and lower the churn rates of the insurance product. SAS approaches the
problem by delivering customer software and service to gain a 360 degree view of the
customer, identify those customers likely to lapse or cancel policies and connect the right
products to the right customer segments through agents and direct channels. SAS also
provides a complete framework of capabilities to help insurer to predict customer lapse
and implement successful marketing campaign to increase profit. SAS offered market-
leading data management capabilities, analytical data model, advance analytics and
proven campaign management to its customer.

Figure 2-4 F1 Logo of SAS ERP system

BIS (Hons) Information System Engineering 16

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

2-5 Features benchmarking of existing systems

Feature Enable
Feature Disable

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Industrial Solution

Education

Financial

Hospitality

Media

Non-Profit

Professional Services

Retail

Other

BIS (Hons) Information System Engineering 17

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Consumer Packaged
Goods

Health and Social

Services

Manufacturing

Healthcare

CRM Functionality

Market Automation
Features

Email Marketing

Mailing List
Management

Social Media

Product Catalog

BIS (Hons) Information System Engineering 18

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Integration

Territory Management

Security Features

Data Encryption

Field-Level Security

Group Creation and

Management

Roles / Organizational
Hierarchy

Security Admin
Profiles

Analytics Features

Forecasting

BIS (Hons) Information System Engineering 19

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Dashboards

Reporting

Dashboard
Customization

Channel Management
Features

Customizable
Features

Customizable Forms
& Data Fields

Multi- Language

Template
Management

Sales Automation

BIS (Hons) Information System Engineering 20

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Features

Billing / Invoicing

Contact History

Contact Management

Contact Scheduler

Customer Database

Lead Management

Lead Tracking

Customer Service

Customer Service
Integration

Customer Support
Tracking

BIS (Hons) Information System Engineering 21

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

User Interface
Customization

Collaboration
Features

Mail Merge

Mobile Access

Remote Access

Remote Tracking

Workflow Rules and

Management

Integration

Data Import/ Export

Support Features

BIS (Hons) Information System Engineering 22

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Blog

Email

FAQ

Instructional Videos

Knowledge base

Live Chat

Normal business
hours

Phone

Tips and hints

Webinars

Request Form

BIS (Hons) Information System Engineering 23

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

On-site

Forums

Online Self Serve

Recorded Demos

Languages Supported

Chinese

Dutch

English

French

German

Italian

Japanese

BIS (Hons) Information System Engineering 24

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 2 Literature Review

Software Name Nimble SalesNet HubSpot Zoho CRM

CRM CRM Basic Professional
Software Software CRM Edition
Software CRM
Software

Other

Portuguese

Russian

Spanish

Swedish

Table 2-5 T1 Benchmarking of different CRM systems

BIS (Hons) Information System Engineering 25

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

Chapter 3 System Development

3-1 Methodology
After a lot of consideration and research, the incremental model is the best model
to be used to develop this system. In the incremental model, the steps was from
initial planning into the planning and specific requirement, after that will develop
and deployment, the testing will be conduct concurrently, at the end the collected
testing data will be used to enhance the system and start from the planning phase
again.

Figure 3-1 F1 Methodology of system development

BIS (Hons) Information System Engineering 26

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

3-2 Tools
The main tools or skill used to develop this project is Hyper Text Markup Language
(HTML), Cascading style sheets (CSS), Javascript, PHP: Hypertext Preprocessor (PHP)
and the Structured Query Language (SQL). HTML is a markup language and a markup
language is a set of markup tags.

HTML documents contain HTML tags and plain text and it also called as a web page.
CSS is use to define how to display HTML elements like font color, background color
and others. CSS was added to HTML 4.0 and newer version to solve the problem of too
many tags in HTML document. An external style sheet can help to save a lot of work and
it is stored in CSS files.

Javascript is programming code that can be inserted into HTML pages and can be
executed by modern web browser. Javascript is easy to learn and it’s performance was
powerful as JAVA and C++ language. PHP is a server side scripting language and
executed on server. PHP was supporting many databases like MySQL, Informix, Oracle,
Sybase, Generic ODBC and others. PHP can be run on different platform like Windows
and Linux, and it is also compatible with almost all servers used today like Apache and
IIS.

SQL is a standard language use to accessing and manipulating databases. SQL can use to
execute query against databases, retrieve data from databases, insert data to databases and
other useful features.

Beside the language, the important technology to develop web application is the web
server application. Web server application is application help to deliver the web content

BIS (Hons) Information System Engineering 27

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

that can be accessed through the internet. The most common use for web is to host
websites, but there are also other like enterprise application, databases, and gaming.
There are many different existing web servers. The top web server in the world is Apache
found by Apache, IIS found by Microsoft, nginx found by NGINX. Inc and GWS found
by Google.

Relational Database Management System (RDBMS) is also an important application in

develop a web system. Without a RDBMS, the system cannot store the data in good
security, sequence and structure. The famous RDBMS are MySQL, Oracle, DB2,
Teradata, SQL Server and Microsoft Office Access.

HTML

RDBMS CSS

System
Web Java
Server script

SQL PHP

Figure 3-2 F1 Development tools

BIS (Hons) Information System Engineering 28

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

3-3 Implementation Issues and Challenges

In the development of this CRM system, there are 2 issues will be faced. One of the
issues is the formula of the customer segmentation and analysis. It was difficult to ensure
that the formula of ratios is correct or wrong. Beside this, it is also difficult to figure
which type of analysis was helpful to the marketer.

The second issue is volume of testing data. A small amount of sample was difficult to
display the actual answer of question. For example, the correctness of 10 samples is very
weak, but if a sample of 10000 samples, the actual rate of the condition was more
correctly.

BIS (Hons) Information System Engineering 29

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

3-4 Timeline
This project was estimated to be complete in a period of around 1 year. The following
gantt chart will show the timeline for each phases of the project. There are seven phases
in this project and take different duration to complete. The initial planning will take
around 35 days to complete, planning will take 10 days. After planning, the prototyping
and design will carry out concurrently which prototyping is estimated to complete in 25
days and design is estimated to complete in 40 days. After design phase will be the
development phase which take the longest days estimated as 90days. When the
development was done, the testing and debugging will carry out, each of it will use
around 30days.

ID Task Name Duration Start

2013 Finish 2014
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun
1 Initial Planning 35 days Mon 5/ 27/13 Fri 7/ 12/13
2 Planning 10 days Mon 7/ 15/13 Fri 7/ 26/13
3 Prototyping 25 days Mon 7/ 29/13 Fri 8/ 30/13
4 Design 40 days Mon 7/ 29/13 Fri 9/ 20/13
5 Development 90 days Mon 9/ 23/13 Fri 1/ 24/14
6 Testing 30 days Mon 1/ 27/14 Fri 3/ 7/ 14
7 Debug and Enhancement 30 days Mon 3/ 10/14 Fri 4/ 18/14

Table 3-4 T1 Gantt Chart of System Development

BIS (Hons) Information System Engineering 30

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

3-5 Requirement Specification

3-5-1 Security Features
User Management: The user system should including add, modify and delete user. The
system admin should be able to manage the account of internal user such ask staff. The
customers will register the account in the system. Each customer will use a special access
code and their IC to bind their user account with their profile.

User Authentication: Users need to provide their login ID and password every time they
access the system.

Group Creation and Management: Each user shall be define and belong to one or more
group. Example of user groups is admin, manager, customer and others. The admin shall
able to create and maintain the group setting.

Pages permission: Different pages shall grant to different user group. For example,
admin user is only grant to control the user and system.

Change Password: Each of the users should allow updating their user’s account
password if they feel their password is not secure anymore.

3-5-2 Analysis
Customer Filtering: The system should allow the user to filter a list of customers base
on customers’ information like demographic information. After filtering, the system
should display a simple summary of the list of customer. For example, is should show

BIS (Hons) Information System Engineering 31

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

what is the total number of customer filtered, what is the ratio of customer from male to
female.

Customer profile: It shall include a page to view the customer’s profile. In the profile, it
should show all the customer demographic data, customer’s analysis, purchase history,
purchase behavior and others.

Product Analysis: The system should allow the user to select a product and analyze it.
The analysis should show which type of customer is buying the product, which outlet is
the hot selling and others.

3-5-3 Promotion Tools

Promotion Creator: The system should allow the user to create a new promotion. The
promotion should include the promoted product, promotion title, start date, end date and
the promotion detail. Beside these, the promotion should also available to select one or
more outlet to apply.

Select Promotion Target: The system should allow user to filter out a list of target
customer for the promotion. The example of filter is the customer information, the
customer who never but the promoted before and others.

Assign Promotion Target: The system should assign the list of targeted customer to the
employee of the outlet where the customer registers as task.

BIS (Hons) Information System Engineering 32

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 3 System Development

Send Promotion: The system should include the plugin to let the user send the
promotion detail to the customers. The system should include various methods to send
the promotion. The method should include email, phone calling, SMS and other methods
as well.

Detect Customer Respond: The system should use various methods to detect whether
the customer is responding to the sent promotion. The example of method is to detect is
the customer buying the product in promotion period.

Promotion Analysis: The system should allow the manager to check the promotion’s
performance. The analysis’s purpose is to show the relationship of the promotion effort
and the feedback of customer.

BIS (Hons) Information System Engineering 33

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Chapter 4 System and Interface Design

4-1 System Design
This CRM is using PHP language as main develop language, it is a web application,
therefore it will store in 1 folder and host by the web server application with Apache. The
folder is name as CRM and inside the CRM folder containing different files. The
different folder is containing the file with different function. The folder system is same as
below:

CRM: Root folder of the CRM system.

 CSS: This folder is containing the CSS file for the CRM.
 Images: This folder is containing the image used in the CRM.
 Js: This folder is used to store the entire javascript file to be use.
 Log: This folder is used to store the log file of the system.
 Page: This is used to store the PHP file which generating the content of each page
in the CRM.
 Src: This folder is used to store the PHP file containing the PHP function used by
the application.
 Template: This is used to store the template file of the system like header, footer
and menu.
 Widget: This is used to store the PHP file call by the content PHP file.
 index.php: This is the default page when the user visits the website.

BIS (Hons) Information System Engineering 34

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

This CRM system is using nested include generating the dynamic content web pages. The
system is using the index.php to include header, content, and footer. Beside this, the
system also using jquery ajax to display some data generated by the PHP inside the
Widget folder.

Figure 4-1 F1 System Algorithm

BIS (Hons) Information System Engineering 35

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-2 Interface Design

The output of the index.php is in HTML format. Each of the pages generated will having
the same layout but different content. The system interface’s layout is shown as below.

Figure 4-2 F1 Interface Design

BIS (Hons) Information System Engineering 36

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Header Design

Figure 4-2 F2 Header design

Navigation Design: Each user role will have different menu option.

Figure 4-2 F3 Navigation Bar Design

Footer Design

Figure 4-2 F4 Footer Design

BIS (Hons) Information System Engineering 37

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-3 Activity Diagram

Figure 4-3 F1 Activity Diagram of Promotion

BIS (Hons) Information System Engineering 38

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-4 Functional Page Design

Customer Registration Page: This page is containing a form to let customer fill in the
username and password to register a user to use the system.

Figure 4-4 F1 Customer Registration Page

Login Page: This page provides a form for user to login and access the system.

Figure 4-4 F2 Login Page

BIS (Hons) Information System Engineering 39

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Change Password Page: A form let user to update their account’s password.

Figure 4-4 F 3 Change Password Page

Role list Page: Display all of the role

Figure 4-4 F4 Role List Page

BIS (Hons) Information System Engineering 40

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

New Role Page: A form to create new role of users.

Figure 4-4 F5 New Role Page

New User Page: A form to create new staff user

Figure 4-4 F6 New User Page

BIS (Hons) Information System Engineering 41

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Internal User List Page: Display the entire staff user.

Figure 4-4 F7 Internal User List Page

BIS (Hons) Information System Engineering 42

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Page list: Display all of the system’s page

Figure 4-4 F8 Page List

BIS (Hons) Information System Engineering 43

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

New Page: A form to create new web page of system

Figure 4-4 F9 New Page Form

BIS (Hons) Information System Engineering 44

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Customer Filter Page: A form with options to filter out a list of customer.

Figure 4-4 F10 Customer Filter Page

BIS (Hons) Information System Engineering 45

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Customer Filter Result Page: List of filtered customer.

Figure 4-4 F11 Customer Filter Result Page

BIS (Hons) Information System Engineering 46

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Customer Profile Page: Display the customer’s profile

Figure 4-4 F12 Customer Profile

BIS (Hons) Information System Engineering 47

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Product Selection Page: A form to select products.

Figure 4-4 F 13 Product Selection Page

BIS (Hons) Information System Engineering 48

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Product Analysis Page: Display the analysis of the selected product

Figure 4-4 F 14 Product Analysis Page

BIS (Hons) Information System Engineering 49

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

New Promotion Page: A form to create new promotion

Figure 4-4 F15 New Promotion Page

BIS (Hons) Information System Engineering 50

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Customer Filter Page (Promotion): Select option to filter list of customer to promote.

Figure 4-4 F16 Customer Filter Page (Promotion)

BIS (Hons) Information System Engineering 51

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Customer Filter Result (Promotion): Display a list of filtered customer.

Figure 4-4 F 17 Customer Filter Result (Promotion)

BIS (Hons) Information System Engineering 52

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Promotion List Page: Display list of entire promotion created

Figure 4-4 F18 Promotion List Page

BIS (Hons) Information System Engineering 53

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Promotion Detail Page (Manager): Display all information of the selected promotion

Figure 4-4 F19 Promotion Detail Page (Manager)

BIS (Hons) Information System Engineering 54

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Promotion Performance Page: Display the analysis of the promotion

Figure 4-4 F20 Promotion Performance Page

BIS (Hons) Information System Engineering 55

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Assigned Task Page (Promoter): Display a list of promotion to promote.

Figure 4-4 F 21 Assigned Task Page (Promoter)

BIS (Hons) Information System Engineering 56

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Promotion Detail Page (Promoter): Display the work done for the promotion.

Figure 4-4 F22 Promotion Detail Page

BIS (Hons) Information System Engineering 57

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Email Template: A template to send email to user.

Figure 4-4 F23 Email Template

BIS (Hons) Information System Engineering 58

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Phone Call Template: Display the calling phone information.

Figure 4-4 F24 Phone Call Template

SMS Template: A template to send SMS to the phone number.

Figure 4-4 F25 SMS Template

BIS (Hons) Information System Engineering 59

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Offered Promotion Page (Customer): Display the promotion offer to the user.

Figure 4-4 F26 Offered Promotion Page

BIS (Hons) Information System Engineering 60

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Promotion Detail Page (Customer): Display the selected promotion.

Figure 4-4 F27 Promotino Detail Page (Customer)

BIS (Hons) Information System Engineering 61

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

Transaction History Page (Customer): Display the processed transaction of the user.

Figure 4-4 F28 Transaction History Page

BIS (Hons) Information System Engineering 62

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5 Entity Relationship Diagram

Figure 4-5 F1 Entity Relationship Diagram (ERD)

BIS (Hons) Information System Engineering 63

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5-1 Customer Detail

Figure 4-5-1 F1 Customer Detail ERD

BIS (Hons) Information System Engineering 64

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5-2 User Account

Figure 4-5-2 F1 User Account ERD

BIS (Hons) Information System Engineering 65

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5-3 Transaction Detail

Figure 4-5-3 F1 Transaction Detail ERD

BIS (Hons) Information System Engineering 66

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5-4 Product Detail

Figure 4-5-4 F1 Product Detail

BIS (Hons) Information System Engineering 67

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-5-5 Promotion

Figure 4-5-5 F1 Promotion ERD

BIS (Hons) Information System Engineering 68

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

4-6 Data Dictionary

customer_detail: Store all customer information.
Attributes Data Type Description Nulls
id INTEGER customer's identify number No
ic VARCHAR(45) customer's I/C number No
full_name VARCHAR(45) customer's name No
gender INTEGER customer's gender No
age INTEGER customer's age No
race INTEGER customer's race No
date_of_born DATETIME customer's birthday No
street VARCHAR(45) customer’s address(street no.) No
postcode VARCHAR(45) customer's address(postcode) No
city_code INTEGER customer's address(city) No
email VARCHAR(45) customer's email address No
register_outlet INTEGER outlet of customer register member No
access_code INTEGER unique code assigned to customer No
Table 4-6 T1 customer_detail Entity

list_race: Store the types of race.

Attributes Data Type Description Nulls
id INTEGER race's identify number No
race VARCHAR(45) type of race No
Table 4-6 T2 list_race Entity

BIS (Hons) Information System Engineering 69

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

list_gender: Store the types of gender.

Attributes Data Type Description Nulls
id INTEGER gender's identify number No
gender VARCHAR(45) type of gender No
Table 4-6 T3 list_gender Entity

list_outlet: Store information of all outlets.

Attributes Data Type Description Nulls
id INTEGER outlet's identify number No
name VARCHAR(45) outlet's name No
city_code INTEGER outlet's located city No
Table 4-6 T4 list_outlet Entity

list_city: Store list of cities

Attributes Data Type Description Nulls
id INTEGER city's identify number No
city_name VARCHAR(45) city's name No
state_id INTEGER city's located state No
Table 4-6 T5 list_city Entity

BIS (Hons) Information System Engineering 70

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

list_state: Store list of states

Attributes Data Type Description Nulls
id INTEGER state's identify number No
state_name VARCHAR(45) state's name No
Table 4-6 T6 list_state Entity

user_role: Store the types of role of users

Attributes Data Type Description Nulls
id INTEGER role's identify number No
role_name VARCHAR(45) role's name No
Table 4-6 T7 user_role Entity

user_account: Store the user account’s detail

Attributes Data Type Description Nulls
id INTEGER user's identify number No
username VARCHAR(45) user's username No
password VARCHAR(45) user's password No
role_id INTEGER user's role No
created DATETIME time created user account No
modified DATETIME time modified user account No
created_by VARCHAR(45) person created user No
modified_by VARCHAR(45) person modified user No
outlet_id INTEGER staff's outlet No
customer_id INTEGER customer's identify number No
Table 4-6 T8 user_account Entity

BIS (Hons) Information System Engineering 71

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

role_page: Store the pages accessible by different roles.

Attributes Data Type Description Nulls
id INTEGER Unique number for each role and page. No
role_id INTEGER role's identify number No
page_id INTEGER page's identify number No
Table 4-6 T9 role_page Entity

system_page: Store all of the pages used by the system

Attributes Data Type Description Nulls
id INTEGER Page's unique number No
file_name VARCHAR(45) the file name of the page. No
type_id INTEGER the type of the page No
Table 4-6 T10 system_page Entity

system_page_type: Store information of all types of pages

Attributes Data Type Description Nulls
id INTEGER Unique number for the type No
type_name VARCHAR(45) The name of the page's type No
Table 4-6 T11 system_page_type Entity

BIS (Hons) Information System Engineering 72

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

transaction_detail: Store the detail of all transactions.

Attributes Data Type Description Nulls
id INTEGER Unique id for each transaction No
t_time DATETIME the time of transaction occur No
t_count_item INTEGER the number of items in transaction No
t_amount DECIMAL(10,2) the total amount of transaction No
t_profit DECIMAL(10,2) the total amount of profit of the trasaction No
customer_id INTEGER the customer who transaction with No
outlet_id INTEGER the outlet of the transaction No
Table 4-6 T12 transaction_detail Entity

transaction_item: Store the items included in the transaction.

Attributes Data Type Description Nulls
id INTEGER Unique id for each item No
tranasction_id INTEGER The transaction id of the sold item No
product_code INTEGER the product sold. No
price DECIMAL(10,2) the price of the product No
profit DECIMAL(10,2) the profit get from the product No
Table 4-6 T13 transaction_item Entity

list_product_main: Store the main category of product.

Attributes Data Type Description Nulls
id INTEGER Unique id of the category No
category VARCHAR(45) the name of the category No
Table 4-6 T14 list_product_main Entity

BIS (Hons) Information System Engineering 73

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

list_product_second: Store the second level category of product.

Attributes Data Type Description Nulls
id INTEGER Unique id of the category No
category VARCHAR(45) the name of the category No
main_id INTEGER the id of the main category No
Table 4-6 T15 list_product_second Entity

list_product_third: Store the third level category of product.

Attributes Data Type Description Nulls
id INTEGER Unique id of the category No
category VARCHAR(45) the name of the category No
second_id INTEGER the id of the second level category No
Table 4-6 T16 list_product_third Entity

list_company: Store the information of producer of the product.

Attributes Data Type Description Nulls
id INTEGER Unique id of the company No
name VARCHAR(45) name of the company No
domain VARCHAR(45) the website of the company No
contact VARCHAR(45) the contact number of the company No
representative VARCHAR(45) the name of representative of company No
email VARCHAR(45) the email of the company No
short_name VARCHAR(45) the short name of the company No
Table 4-6 T17 list_company Entity

BIS (Hons) Information System Engineering 74

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

list_product: Store the information of the products.

Attributes Data Type Description Nulls
id INTEGER Unique id of the product No
name VARCHAR(45) name of the product No
price DECIMAL(10,2) price of the product No
third_id INTEGER third level category of the product No
company_id INTEGER producer company of the product No
profit DECIMAL(10,2) the profit from the product No
Table 4-6 T18 list_product Entity

promotion: Store the information of the promotions.

Attributes Data Type Description Nulls
id INTEGER Unique id of the promotion No
product_id INTEGER product for the promotion No
detail LONGTEXT the detail of the promotion No
start_date DATETIME the start date of promotion No
end_date DATETIME the end date of promotion No
title VARCHAR(45) the title of the promotion No
active INTEGER the active status of the promotion No
Table 4-6 T19 promotion Entity

BIS (Hons) Information System Engineering 75

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

promotion_outlet: Store the outlet promoted the promotions

Attributes Data Type Description Nulls
Unique id of for each of the outlet and
id INTEGER No
promotions
promotion_id INTEGER the id of the promotion No
outlet_id INTEGER the id of the outlet selected No
Table 4-6 T20 promotion_outlet Entity

promotion_target: Store the information of the customer targeted for the promotions.
Attributes Data Type Description Nulls
Unique id for each targeted customer with
id INTEGER No
different promotion
promotion INTEGER the id of the promotion No
customer_id INTEGER the id of the customer No
the staff assign to promote the promotion to
staff_id INTEGER No
the customer
Table 4-6 T21 promotion_target Entity

promotion_target_feedback: Store the feedback from customer.

Attributes Data Type Description Nulls
id INTEGER Unique id for each of the feedback No
target_id INTEGER the target id of the customer No
feedback_action VARCHAR(45) the action of feedback No
created DATETIME the time of feedback created No
Table 4-6 T22 promotion_target_feedback Entity

BIS (Hons) Information System Engineering 76

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

promotion_target_action: Store the promotion effort to the customers.

Attributes Data Type Description Nulls
id INTEGER Unique id for each of the promotion done No
target_id INTEGER the target id of the customer No
action_id INTEGER the method of sending promotion No
created DATETIME the time of promotion done No
email_id INTEGER the email id to check sent email Yes
phone_id INTEGER the phone call id to check called phone Yes
sms_id INTEGER the sms id to check sent SMS Yes
Table 4-6 T23 promotion_target_action Entity

promotion_action: Store the method to promote the promotion

Attributes Data Type Description Nulls
id INTEGER Unique id of the promotion method No
action_name VARCHAR(45) the method to promote the promotion No
Table 4-6 T24 promotion_action Entity

list_phone_call: Store the phone call record of the system

Attributes Data Type Description Nulls
id INTEGER Unique id of each phone called No
receiver VARCHAR(45) the person being called No
contact VARCHAR(45) the contact number of the call No
created DATETIME start time of the call No
modified DATETIME end time of the call No
Table 4-6 T25 list_phone_call Entity

BIS (Hons) Information System Engineering 77

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 4 System and Interface Design

list_email: Store the email sent or pending to send by the system

Attributes Data Type Description Nulls
id INTEGER Unique id for each email No
receiver VARCHAR(45) receiver of the email No
subject VARCHAR(45) Subject of the email No
content LONGTEXT Content of the email No
status VARCHAR(45) status of the email No
created DATETIME the time created the email No
modified DATETIME the time updated the email No
Table 4-6 T26 list_email Entity

list_sms: Store the sms sent or pending to send by the system

Attributes Data Type Description Nulls
id INTEGER Unique id of each SMS No
receiver VARCHAR(45) the number to be send No
content LONGTEXT the content of the SMS No
status VARCHAR(45) the status of the SMS No
created DATETIME the time created the sms No
modified DATETIME the time updated the sms status No
Table 4-6 T27 list_sms Entity

BIS (Hons) Information System Engineering 78

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Chapter 5 System Testing

After completion of project, testing is needed to confirm the system can handle most of
the situation. 2 types of testing were needed to test the system which is unit testing and
functional testing. The testing is completed by follow a series of instruction to test the
system ability. Before releasing the system, testing must be carried out carefully to
increase the quality of system and provides better user experience for the users.

5-1 Unit Testing

Unit testing is mainly to test the system’s individual part of function. The unit test is
require to input to the system with all of the possible input such as correct input, empty
input, wrong format and others possible input. This is to ensure the system can validate
the input as correct input or invalid input. The unit testing will be carrying out included
user login system.

BIS (Hons) Information System Engineering 79

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Unit Test 1: Login as administrator or users

Testing Objective: To ensure the login form working correctly

No Event Attributes and Expected Result Result

values
1.1 Login with correct username Username: Successfully login to the Pass
and correct password admin system and redirect to
Password: homepage.
admin

1.2 Login with empty username Username: Failed to login and turn the Pass
and empty password null require field to red color.
Password:
null

1.3 Login with correct username Username: Failed to login and prompt Pass
and wrong password admin wrong username or password
Password:
abc

1.4 Login with wrong username Username: Failed to login and prompt Pass
and correct password abc wrong username or password.
Password:
admin

1.5 Login with correct username Username: Failed to login and turn the Pass
and empty password admin require field to red color
Password:
null

BIS (Hons) Information System Engineering 80

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

1.6 Login with empty username Username: Failed to login and turn the Pass
and correct password null require field to red color
Password:
admin

Table 5-1 T1Unit Test 1: Login as administrator or users

Unit Test 2: Register Customer

Testing Objective: To ensure the registration of customer work correctly.
No Event Attributes and Expected Result Result
values
2.1 Register User with valid Username: The web page will redirect to Pass
username,valid Cust1 the login page.
password,Valid I/C Number Password:
and Valid Access Code a
I/C Number:
880519-04-4889
Access Code:
7302

BIS (Hons) Information System Engineering 81

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

2.2 Register User with duplicate Username: The form will show "This I/C Pass
username,valid Cust1 was registered"
password,duplicate I/C Password:
Number and Valid Access a
Code I/C Number:
880519-04-4889
Access Code:
7302

2.3 Register User with empty Username: The form will show " Pass
username,empty null Please insert username.
password,empty I/C Number Password: Please insert password.
and empty Access Code null Please insert I/C number.
I/C Number: Please insert access code.
null "
Access Code:
null

2.4 Register User with valid Username: The form will show " Pass
username,valid Cust1 Access code not match with
password,valid I/C Number Password: the I/C number
and invalid Access Code a "
I/C Number:
880519-04-4889
Access Code:
73021

Table 5-1 T2 Unit Test 2: Register Customer

BIS (Hons) Information System Engineering 82

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Unit Test 3: Change User Password

Testing Objective: To ensure user’s password update correctly
No Event Attributes and Expected Result Result
values
3.1 Update Password with valid Current The web page will prompt an Pass
current password, valid new Password: alert show "Success to Update
password and valid confirm a password"
new password New Password:
b
Confirm New
Password:
b

3.2 Update Password with empty Current The form will show "Please fill Pass
current password, empty new Password: in the field with red label and
password and empty confirm null *"
new password New Password:
null
Confirm New
Password:
null

3.3 Update Password with valid Current The form will show "Please Pass
current password, valid new Password: insert same password for NEW
password and different a PASSWORD and CONFIRM
confirm new password New Password: NEW PASSWORD
b "
Confirm New
Password:
c

BIS (Hons) Information System Engineering 83

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

3.4 Update Password with valid Current The form will show " Pass
current password, same new Password: Please insert different
password and same confirm a password for new password
new password with current New Password: "
password a
Confirm New
Password:
a

Table 5-1 T3 Unit Test 3: Change User Password

Unit Test 4: Insert new role

Testing Objective: To test the new role was insert correctly.
No Event Attributes and Expected Result Result
values
4.1 Insert new role with valid role Role Name: The web page will prompt an Pass
name admin2 alert show "New
Role:ADMIN2 successcfully
added"
4.2 Insert new role with empty Role Name: The form will show "Please fill Pass
role name null in the field with red label and
*"
4.3 Insert new role with existed Role Name: The form will show "The Pass
role name admin2 role:Admin2 was exist.
"

Table 5-1 T4 Unit Test 4: Insert new role

BIS (Hons) Information System Engineering 84

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Unit Test 5: Insert new page

Testing Objective: To test the new page is inserting correctly
No Event Attributes and Expected Result Result
values
5.1 Insert new page with valid File Name: The web page will prompt an Pass
file name test_insert alert show "New Page:
test_insert successcfully
added"
5.2 Insert new page with empty File Name: The form will show "Please fill Pass
file name null in the field with red label and
*"
5.3 Insert new page with repeated File Name: The form will show "The file: Pass
file name test_insert test_insert was exist.
"

Table 5-1 T5 Unit Test 5: Insert new page

Unit Test 6: Add new user

Testing Objective: To test the new user is added correctly
No Event Attributes and Expected Result Result
values
6.1 Insert new user with valid username: Prompt alert to show " New Pass
username, valid password manager1 user added successfully"
password:
a

BIS (Hons) Information System Engineering 85

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

6.2 Insert new user with empty username: The form will show "Please fill Pass
username, empty password null in the field with red label and *"
password:
null
6.3 Insert new user with existed username: The form will show "username Pass
username, valid password manager1 existed"
password:
a
Table 5-1 T6 Unit Test 6: Add new user

BIS (Hons) Information System Engineering 86

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Unit Test 7: Add new Promotion

Testing Objective: To ensure the promotion validate correctly
No Event Attributes and Expected Result Result
values
7.1 Insert new promotion with Promotion Title: The promotion will be created Pass
valid title, valid start date, test and the page will redirect to
valid end date, valid content, start date: customer filtering page
select a product and choose 2014-4-1
some outlet end date;
2014-4-5
Product detail:
testing content
Product:
Apparel-
Children's Wear-
Baby Clothes-
Enel Baby
Clothes
Selected Outlet:
Johor-
Batu Bahat
Outlet

BIS (Hons) Information System Engineering 87

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

7.2 Insert new promotion with Promotion Title: Bottom of the form will show " Pass
empty title, empty start date, null Please insert title.
empty end date, empty start date: Please select start date.
content, select a product and null Please select end date.
empty outlet end date; Please insert the promotion's
null detail."
Product detail:
null
Product:
Apparel-
Children's Wear-
Baby Clothes-
Enel Baby
Clothes
Selected Outlet:
null

BIS (Hons) Information System Engineering 88

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

7.3 Insert new promotion with Promotion Title: The page will show "The Pass
valid title, valid start date, test following outlets is having test
valid end date, valid content, start date: for Enel Baby Clothes on 2014-
select a product and choose 2014-4-1 04-01 to 2014-04-05
some outlet which are totally end date; BATU PAHAT OUTLET"
same with testing 7.1 2014-4-5
Product detail:
testing content
Product:
Apparel-
Children's Wear-
Baby Clothes-
Enel Baby
Clothes
Selected Outlet:
Johor-
Batu Bahat
Outlet

BIS (Hons) Information System Engineering 89

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

7.4 Insert new promotion with Promotion Title: The promotion will be created Pass
valid title, valid start date, test and the page will redirect to
valid end date, valid content, start date: customer filtering page
select a product and choose 2014-4-1
some outlet which are totally end date;
same with testing 7.1 except 2014-4-5
the outlet. This test will Product detail:
choose another outlet. testing content
Product:
Apparel-
Children's Wear-
Baby Clothes-
Enel Baby
Clothes
Selected Outlet:
Kedah-
Alor Setar Outlet

BIS (Hons) Information System Engineering 90

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

7.5 Insert new promotion with Promotion Title: Bottom of the form will show " Pass
valid title, invalid start date, test End date must later than start
invalid end date, valid start date: date."
content, select a product and 2014-4-5
choose some outlet. The end date;
testing is putting the start date 2014-4-1
later than end date. Product detail:
testing content
Product:
Apparel-
Children's Wear-
Baby Clothes-
Enel Baby
Clothes
Selected Outlet:
Kedah-
Alor Setar Outlet
Table 5-1 T7 Unit Test 7: Add new Promotion

BIS (Hons) Information System Engineering 91

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

5-2 Functional Testing

After completing the unit testing, functional testing is require to perform. The purpose of
functional testing is to ensure the system is performing as the system requirement stated.
This is more on testing the correctness of workflow of the system.

Functional Test 1: Login with different roles

Testing Objective: To ensure different user’s role log in will display different navigation menu.
No Event Attributes and Expected Result Result
values
1.1 Login with the ADMIN role Username: The navigation menu having Pass
admin 'Home', 'User', 'System',
Password: 'Setting', 'Logout'
admin

1.2 Login with the Username: The navigation menu having Pass
HQ_MANAGER role manager 'Home', 'Analysis', 'Promotion',
Password: 'Setting', 'Logout'
a

1.3 Login with the Username: The navigation menu having Pass
BRANCH_MANAGER role bmanager 'Home', 'Promotion', 'Setting',
Password: 'Logout'
a

BIS (Hons) Information System Engineering 92

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

1.4 Login with the Username: The navigation menu having Pass
SERVICE_STAFF role bstaff 'Home', 'Promotion', 'Setting',
Password: 'Logout'
a

1.5 Login with the CUSTOMER Username: The navigation menu having Pass
role custA 'Home', 'Transaction', 'Setting',
Password: 'Logout'
a

1.6 Using PUBLIC role The navigation menu having Pass

'Home', 'Register', 'Logout'
Table 5-2 T1 Functional Test 1: Login with different roles

Functional Test 2: Create and Update User

Testing Objective: Ensure the management of user is working correctly.
No Event Attributes and values Expected Result Result

2.1 Login with Admin username: The user login the admin Pass
throught the login page Admin page with admin's
password: navigation bar. Admin's
admin navigation bar should
display 'Home', 'User',
'System', 'Setting' and
'Logout'

BIS (Hons) Information System Engineering 93

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

2.2 Go to the create user page Menu -> A New User registration Pass
User List (Internal User) form appear in the page.

Button->
New User

2.3 Fill the new user's detail, username: An alert prompt out and Pass
then click the 'Add' bstaff2 show "Success to add new
button. password: user. ". Then return to the
a user list page.
Role:
SERVICE_STAFF
Outlet:
ALOR SETAR OUTLET

2.4 Click the username Table -> The system will go to Pass
created in previous event SERVICE_STAFF -> User-Edit page.
bstaff2

2.5 Insert the updated password: An alert prompt out and Pass
information and click b show "Success to update"
'Update' button Role:
BRANCH_MANAGER
Outlet:
BATU BAHAT OUTLET

Table 5-2 T2 Functional Test 2: Create and Update User

BIS (Hons) Information System Engineering 94

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Functional Test 3: Create and Update Role in System

Testing Objective: The ensure the management module of user role working correctly
No Event Attributes and Expected Result Result
values
3.1 Login with Admin throught username: The user login the admin page Pass
the login page Admin with admin's navigation bar.
password: Admin's navigation bar should
admin display 'Home', 'User', 'System',
'Setting' and 'Logout'

3.2 Go to the create role page Menu -> A New Role creation form Pass
User -> appear in the page.
Role

Button->
New Role
3.3 Fill in the detail and click the Role Name: An alert prompt out and show Pass
'Add' button Test_Role "New Role: Test_role
successfully added. After this,
Pages: the page will redirect to the
Home user's role list page.

Widgets:
user_login
3.4 Click the role's name in the Table -> The page will redirect to the
list to update the details. Name of Role -> Role-Edit page.
TEST_ROLE

BIS (Hons) Information System Engineering 95

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

3.5 Change the role's detail and Role Name: An alert prompt out and show
click 'Update' button to update Test_Role2 "Role: Test_role successfully
the role. updated. After this, the page
Pages: will redirect to the user's role
All list page.

Widgets:
All
Table 5-2 T3 Functional Test 3: Create and Update Role in System

Functional Test 4: Create and Update System Page

Testing Objective: Ensure the page managament system working correctly
No Event Attributes and Expected Result Result
values
4.1 Login with Admin throught username: The user login the admin page Pass
the login page Admin with admin's navigation bar.
password: Admin's navigation bar should
admin display 'Home', 'User', 'System',
'Setting' and 'Logout'

4.2 Go to the create page page Menu -> A New Page creation form Pass
System -> appear in the page.
Page

Button->
New Page

BIS (Hons) Information System Engineering 96

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

4.3 Fill in the page detail and File Name: An alert prompt out and show Pass
click the 'Add' button test_page "New Page: test_page
successfully added.". After this,
Type: the page will redirect to the
PAGE page list interface.

Role:
ADMIN
4.4 Click the page name to update Table -> The page will redirect to the Pass
the page detail PAGE -> Page-Edit form will filled
Name of Page-> information.
test_page
4.5 Change the data and click File Name: An alert prompt out and show Pass
'Update' button to update the test_page2 "Page: test_page2 successfully
page. updated.".
Type:
WIDGET

Role:
ALL
Table 5-2 T4 Functional Test 4: Create and Update System Page

BIS (Hons) Information System Engineering 97

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Functional Test 5: Change user password

Testing Objective: To ensure the user of system can change their password
No Event Attributes and Expected Result Result
values
5.1 Login with the the user username: The user login the admin page Pass
created in Functionl Test 2 bstaff2 with Branch manager's
throught the login page password: navigation bar. Branch
b manager's navigation bar.
should display 'Home',
'Promotion', 'Setting' and
'Logout'
5.2 Go the change password Menu -> The system will redirect to the Pass
change by the menu button Setting -> Change Password Form
Change
Password
5.3 Insert the current password, Current An alert will prompt out and Pass
new password and confirm Password: show " Success to update
new password to change the b password ".
current password to new
password. New Password:
a

Confirm New
Password:
a
5.4 Logout the user to further test Menu -> The system will go to logout Pass
whether the password was Logout page and redirect to public
change Home page in 3 seconds.

BIS (Hons) Information System Engineering 98

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

5.5 Click Login button to login Menu -> The system will go to the login Pass
the user changed password Login page
5.6 Login the user with the new username: The user logged into the system Pass
password bstaff2 and the system will redirect to
password: the user's Home Page
a
Table 5-2 T5 Functional Test 5: Change user password

Functional Test 6: Customer Filtering and Profiling

Testing Objective: To ensure the customer filtering and profile working well.
No Event Attributes and Expected Result Result
values
6.1 Login with HQ_MANAGER username: The user login the HQ Pass
throught the login page manager Manager's page with HQ
password: Manager's navigation bar. HQ
a Manager's navigation bar
should display 'Home',
'Analysis Tools', 'Promotion
Tools', 'Setting' and 'Logout'
6.2 Go to the customer filter page Menu -> The system will go to the filter Pass
Analysis Tools-> customer form.
Filter Customer

BIS (Hons) Information System Engineering 99

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

6.3 Select the options to filter Gender: The system will go to a page Pass
customers then click 'Search' MALE display many tables. These
button Age: table included Filter Option,
20 to 30 Summary (Gender, race, age,
Race: State, City), and a Customer
CHINESE List Table.
State:
PERAK
City:
IPOH
6.4 Click on the customer's name The customer profile page is Pass
in the Customer List table to showing customer's
see the customer's profile information, Customer behavior
(Most Favourite Item, Visit
Frequency, Span on Different
Category) and Transaction
History
6.5 Click the ID in the The transaction detail will show Pass
Transaction History table to in the coloumn beside the
get the detail of the selected transaction table.
transaction
Table 5-2 T6 Functional Test 6: Customer Filtering and Profiling

BIS (Hons) Information System Engineering 100

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Functional Test 7: Product Analysis Testing

Testing Objective: To ensure the product could be analyze correctly
No Event Attributes and Expected Result Result
values
7.1 Login with HQ_MANAGER username: The user login the HQ Pass
throught the login page manager Manager's page with HQ
password: Manager's navigation bar. HQ
a Manager's navigation bar
should display 'Home',
'Analysis Tools', 'Promotion
Tools', 'Setting' and 'Logout'
7.2 Go to the product selection Menu -> The system will go to the Pass
page Analysis Tools-> production selection form.
Analyze
Products

7.3 Select Main Category Main Category: A list of second category will be Pass
Apparel displayed
7.4 Select Secondary Category Second A list of third category will be Pass
Category: displayed
Children's Wear
7.5 Select Third Category Third Category: A list of products will be Pass
Baby Clothes displayed

BIS (Hons) Information System Engineering 101

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

7.6 Click on the products name in Product Detail-> A product profile page will Pass
the product detail table to see Product Name-> show product's information and
the analysis of the selected Enel Baby Product Sale Perfomance
product Clothes (Month Analysis, Weekday
Analysis, Outlet Analysis,
Gender, Age, Race, City and
State Analysis)

Table 5-2 T7 Functional Test 7: Product Analysis Testing

Functional Test 8: Create and Update Promotion

Testing Objective: To ensure the promotion management tools working correctly
No Event Attributes and Expected Result Result
values
8.1 Login with HQ_MANAGER username: The user login the HQ Pass
throught the login page manager Manager's page with HQ
password: Manager's navigation bar. HQ
a Manager's navigation bar
should display 'Home',
'Analysis Tools', 'Promotion
Tools', 'Setting' and 'Logout'
8.2 Go to the new promotion page Menu -> The system will go to the new Pass
Promotion promotion form.
Tools->
New Promotion

BIS (Hons) Information System Engineering 102

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

8.3 Insert the promotion detail Active: The promotion was created and Pass
and click 'Create' button Checked the system will display
Customer Filtering Page
Promotion:
Test Promotion

Main Category:
Apparel

Second
Category:
Children's Wear

Third Category:
Baby Clothes

Product:
Enel Baby
Clothes

Start Date:
2014-4-20

End Date:
2014-4-25
Promotion
Detail:
Test Promotion
Content

BIS (Hons) Information System Engineering 103

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Promotion
Outlet:
Johor

8.4 Go to promotion list select the Menu -> A list of promotion displayed Pass
promotion created in Testing Promotion
8.3 to update Tools->
All Promotion
8.5 Click on the promotion title to Table -> Edit Promotion Form displayed Pass
update the promotion Promotion ->
Title ->
Test Promotion
8.6 Change the information of the Active: The promotion was updated and Pass
promotion and click 'Save' Checked the system will display
button Customer Filtering Page
Promotion:
Test Promotion2

Main Category:
Apparel

Second
Category:
Children's Wear

Thid Category:
Baby Clothes

BIS (Hons) Information System Engineering 104

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Product:
Enel Baby
Clothes

Start Date:
2014-4-18

End Date:
2014-4-25

Promotion
Detail:
Test Promotion
Content2

Promotion
Outlet:
Johor, Kedah
Table 5-2 T8 Functional Test 8: Create and Update Promotion

BIS (Hons) Information System Engineering 105

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

Functional Test 9: Select Promotion Target Customer

Testing objective: To ensure the sytem can filter a list of customer and target them based on the
promotion.
No Event Attributes and Expected Result Result
values
9.1 Login with HQ_MANAGER username: The user login the HQ Pass
throught the login page manager Manager's page with HQ
password: Manager's navigation bar. HQ
a Manager's navigation bar
should display 'Home',
'Analysis Tools', 'Promotion
Tools', 'Setting' and 'Logout'
9.2 Go to promotion list select the Menu -> A list of promotion displayed Pass
promotion created in Testing Promotion
8.3 to update Tools->
All Promotion
9.3 Click on the promotion title to Table -> Edit Promotion Form displayed Pass
update the promotion Promotion ->
Title ->
Test Promotion
9.4 Click the 'Save' button without The system will display a Pass
changing the promotion's customer filter form
detail
9.5 Select an filter option to filter Filter option: The page will show a list of Pass
the customer then click the Customer who customer fullfilled the filter
'Submit' button never purchase option.
before.

BIS (Hons) Information System Engineering 106

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

9.6 Click the 'process' button to The system will return to the Pass
confirm the promotion's target Home Page
customer
Table 5-2 T9 Functional Test 9: Select Promotion Target Customer

Functional Test 10: Sending promotion to customer and Getting Respond

Testing Objective: To ensure the staff can promote the promotion to the customers assigned to them.
Beside, the customer registered a account also able to respond to the promotion.
No Event Attributes and Expected Result Result
values
10.1 Login with the staff accoun to username: The user login the staff page Pass
perform the testing bstaff with staff's navigation bar.
Staff's navigation bar should
password: display 'Home', 'Promotion
a Tools', 'Setting' and 'Logout'
10.2 Search the task of the Menu -> Task Page will be displayed. Pass
customer. Home Within the page, there are a
table of promotions list.
10.3 Click on the promotion's title Table -> The page will display 2 tables Pass
to promote the promotion to Task -> which are promotion detail and
the customers Title -> targeted customer.
Test Promotion2

10.4 Click on the 'EMAIL' link Table -> A new page with email template Pass
within the customer's row to Targeted will displayed
send the email to the customer Customer ->
Action ->
EMAIL

BIS (Hons) Information System Engineering 107

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

10.5 Click the 'Send' button to send The page will closed Pass
the email with final content to
the customer
10.6 Click on the 'PHONE' link Table -> A new page with phone call Pass
within the customer's row to Targeted detail will displayed
make phone call to the Customer ->
customer Action ->
PHONE
10.7 Click the 'End Call' button to The page will closed Pass
end the call with customer

10.8 Click on the 'SMS' link within Table -> A new page with SMS template Pass
the customer's row to send the Targeted will displayed
SMS to the customer Customer ->
Action ->
SMS
10.9 Click the 'Send' button to send The page will closed Pass
the SMS with final content to
the customer
10.10 Click on the refresh button of Refresh' button The action column of the Pass
the browser to see the update OR customer selected in previous
information press 'F5' testing will become EMAIL(1),
PHONE(1), SMS(1)

BIS (Hons) Information System Engineering 108

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

10.11 Click on customer name to get Table -> A new customer profile page Pass
customer's IC and Access Targeted will be open
Code Customer ->
Customer's
Name ->
previous
customer
10.12 Open another web browser url: public's Home Page displayed Pass
and open the My CRM web localhost/CRM
system
10.13 Go to the customer Menu -> The system will show Pass
registration page Register customer's user register form
10.14 Register a new customer with username: The user was created and the Pass
the I/C number and access Customer1 system will show the login
code retrieved in Testing form.
10.11. Then click the password:
'Register' button to register. a

I/C Number:
841016-02-4939

Access Code:
6651
10.15 Login with the customer's user username: The system will go to customer Pass
created in Testing 10.14. Customer1 Home Page. The navigation bar
of this user will display
password: Home,Transaction, Setting and
a Logout

BIS (Hons) Information System Engineering 109

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 5 System Testing

10.16 Review the detail of the Table -> The page will display the detail Pass
promotion received Promotion of the selected promotion
Offered ->
Action ->
View
Table 5-2 T10 Functional Test 10: Sending promotion to customer and Getting Respond

Functional Testing 11: Promotion performance

Testing Objective: To ensure the manager user can check the performance of the promotion.

No Event Attributes and Expected Result Result

values
11.1 Login with HQ_MANAGER username: The user login the HQ Pass
throught the login page manager Manager's page with HQ
password: Manager's navigation bar. HQ
a Manager's navigation bar
should display 'Home',
'Analysis Tools', 'Promotion
Tools', 'Setting' and 'Logout'
11.2 Go to the promotion list page Menu -> The system will show the list of Pass
Promotion promotion
Tools->
All Promotion
11.3 Select the promotion to Table -> The page will display the Pass
review Promotion-> promotion details, Analysis
Performance-> (Total Promotion Done, Total
CHECK (Test Feedback Done and Feedback
Promotion2) VS Promotion)
Table 5-2 T11 Functional Testing 11: Promotion performance

BIS (Hons) Information System Engineering 110

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 6 Discussion and Conclusion

Chapter 6 Discussion and Conclusion

6-1 Project Review
In conclusion, customer leaving is the problem faced by all of the organization. This
problem is no method to solve completely because every customer was unique and
changing every day. This problem was serious because it will directly affect the profit of
the company; the method to decrease the number of customer leaving is increasing
customer loyalty. The proposed solution to decrease the customer retention in this project
is applying the customer relationship management (CRM) system to the organization.
This CRM system will help the company to have a more clearly and critically view to the
customer, then increase the current customer’s loyalty and stay the customers before they
leave.

This project was developed a CRM at the end. This CRM system was achieve the
objectives of the project. The objectives were done by different modules of the system.
The modules included customer segmentation and filtering, system page management,
customer profiling and promotion management tools.

6-2 Strength and Limitation

The Strength of this system is using data mining to discover the history data with more
patterns and make it more valuable. This system is using data mining technology to
generate the profile of the customer base on the purchase history. The customer profile

BIS (Hons) Information System Engineering 111

Faculty of Information and Communication Technology (Perak Campus), UTAR
Chapter 6 Discussion and Conclusion

included the analysis like which products is most frequent bought by the customer, which
category of product customer spend most and others.

The data mining technology also used to find out the potential buyer for the promotion.
The system can find out the customer who frequently purchasing the promoted product or
the customer who never but the promoted products. After that, the user can send the
promotion to these targeted and listed customers.

The Limitation of this CRM system is it complexity for use. New user might not easy to
handle the features in the system since the features is included many pages. So the new
user might need to be trained before using the system.

6-3 Future Enhancement

There are some enhancements available for this project. The first enhancement is the
module of the system. This CRM is not complete and still have a lot of space to expand.
The module can be added included Sales Force Automation (SFA), Service Automation,
Marketing Automation and others. While the system added these modules, this CRM will
be more complete and more powerful for the organizations.

Beside the modules, this system can be improve to be more merge able with another
Enterprise Resource Planning (ERP) System. The system can add module to customize
the connection with other system’s database, and make it adaptable to most of the
database design of other ERP system. So this CRM could become more standalone
system but adaptable to other systems at the same time.

BIS (Hons) Information System Engineering 112

Faculty of Information and Communication Technology (Perak Campus), UTAR
References
1. Jerry W. Thomas, Market segmentation
Available from: http://www.decisionanalyst.com/Downloads/MarketSegm.pdf
[Access 6th July 2013]
2. Gunter, Barrie and Adrian Furnham, 1992, Consumer profiles: An introduction
to psychographics, London, Routledge
3. Francis Buttle, 2008, Customer Relationship Management: Concept and
Technologies , Second Edition, UK, taylor & francis
4. Armstrong, Gary & Kotler, Philip, 2005, Marketing: An Introduction, Seventh
Edition, Upper Saddle River, N.J. Prentice Hall
5. Pickton, David & Broderick, Amanda, 2005, Integrated marketing
communications, Second Edition
6. Kotler, Philip & Keller, Kevin Lane, 2009, Marketing Management, Thirteenth
Edition, Pearson Education International
7. Airtel, Vodafone Idea Lose Cell Users
Available from: http://www.businessworld.in/en/storypage/-/bw/airtel-vodafone-
idea-lose-cell-users/570220.37489/page/0
[Accessed 24 November 2012]

BIS (Hons) Information System Engineering 113

Faculty of Information and Communication Technology (Perak Campus), UTAR
Bibliography
p./pp. Page/pages

BIS (Hons) Information System Engineering 114

Faculty of Information and Communication Technology (Perak Campus), UTAR
APPENDIX A Turnitin Report

Figure A-1-F1 Turnitin Report

BIS (Hons) Information System Engineering A-1

Faculty of Information and Communication Technology (Perak Campus), UTAR