SHOPPING MALL PROMOTION TRACKER SUBSYSTEM FOR PIN-IT SOCIAL NETWORK
TAN CHUN CHIEH
JUDUL: SHOPPING MALL PROMOTION TRACKER SUBSYSTEM FOR PIN-IT SOCIAL NETWORK (SMPTS)
SESI PENGAJIAN: 2012/2013
Saya TAN CHUN CHIEH mengaku membenarkan tesis (PSM/Sarjana/Doktor Falsafah) ini disimpan di Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat kegunaan seperti berikut:
1. Tesis dan projek adalah hakmilik Universiti Teknikal Malaysia Melaka.
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan membuat salinan untuk tujuan pengajian sahaja.
3. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan membuat salinan tesis ini sebagai bahan pertukaran antara institusi pengajian tinggi.
4. ** Sila tandakan (/)
________ SULIT (Mengandungi maklumat yang berdarjah
keselamatan atau kepentingan Malaysia seperti yang termaktub di dalam AKTA RAHSIA RASMI 1972) ___/____ TERHAD (Mengandungi maklumat TERHAD yang telah ditentukan oleh organisasi/badan di mana penyelidikan dijalankan)
________ TIDAK TERHAD
___________________________ ___________________________ (TANDATANGAN PENULIS) (TANDATANGAN PENYELIA) Alamat tetap: 2, Jalan Tembusu 8, NURIDAWATI BINTI MUSTAFA Taman Merdeka, Batu Berendam, Nama Penyelia
75350, Melaka, Malaysia.
Tarikh: ___________________ Tarikh: _____________________ CATATAN: * Tesis dimaksudkan sebagai Laporan Akhir Projek Sarjana Muda(PSM)
ii
SHOPPING MALL PROMOTION TRACKER SUBSYSTEM FOR PIN-IT SOCIAL NETWORK
TAN CHUN CHIEH
This report is submitted in partial fulfillment of the requirements for the Bachelor of Computer Science (Software Development)
FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY UNIVERISITI TEKNIKAL MALAYSIA MELAKA
DECLARATION
I hereby declare that this project report entitled
SHOPPING MALL PROMOTION TRACKER SUBSYSTEM FOR PIN-IT SOCIAL NETWORK
is written by me and is my own effort and that no part has been plagiarized without citations.
STUDENT : ______________________________________ Date : __________
(TAN CHUN CHIEH)
iii
DEDICATION
This thesis is dedicated to my dad, Tan Poh Hwa. His caring and support throughout the whole project has enabled me to complete this task successfully. He is my greatest dad.
ACKNOWLEDGEMENTS
v
ABSTRACT
TABLE OF CONTENT
ACKNOWLEDGEMENTS ... iv
ABSTRACT ... v
TABLE OF CONTENT ... vi
LIST OF TABLES ... x
LIST OF FIGURES ... xii
LIST OF ABBREVIATION... xiii
CHAPTER I ... 1
INTRODUCTION... 1
1.1 Introduction ... 1
1.2 Problem Statement ... 2
1.3 Objective ... 3
1.4 Scope ... 3
1.5 Project significance ... 4
1.6 Conclusion ... 4
CHAPTER II ... 5
LITERATURE REVIEW AND PROJECT METHODOLOGY ... 5
2.1 Introduction ... 5
2.2 Fact and finding (based on topic) ... 5
2.3 Project Methodology ... 7
2.4 Project Requirements ... 8
2.4.1 Software Requirement ... 8
vii
2.5 Project Schedule and Milestones ... 9
2.6 Conclusion ... 10
CHAPTER III ... 12
ANALYSIS ... 12
3.1 Introduction ... 12
3.2 Problem Analysis ... 13
3.3 Requirement Analysis ... 13
3.3.1 Data Requirement ... 13
3.3.2 Functional Requirement ... 14
3.3.3 Non-Functional Requirements ... 16
3.4 Conclusion ... 18
CHAPTER IV... 19
DESIGN ... 19
4.1 Introduction ... 19
4.2 High Level Design... 20
4.2.1 System Architecture... 20
4.2.2 User Interface Design ... 21
4.2.3 Database Design ... 28
4.3 Detailed Design ... 48
4.3.1 Physical Database Design ... 48
4.4 Conclusion ... 56
CHAPTER V ... 57
IMPLEMENTATION ... 57
5.1 Introduction ... 57
5.2 Software Development Environment Setup ... 58
5.2.1 Software Development Environment Setup ... 59
5.3 Software Configuration Management ... 62
5.3.1 Configuration environment setup ... 62
5.3.2 Version Control Procedure ... 64
5.4 Implementation Status ... 65
5.5 Conclusion ... 66
CHAPTER VI... 67
TESTING ... 67
6.1 Introduction ... 67
6.2 Test Plan ... 68
6.2.1 Test Organization... 68
6.2.2 Test Environment... 68
6.2.3 Test Schedule ... 69
6.3 Test Strategy ... 70
6.3.1 Classes of test ... 70
6.3.1.1 Output Correctness Test ... 70
6.3.1.2 Stress Test ... 70
6.4 Test Design ... 71
6.4.1.1 Login test description ... 71
6.5 Test Result and Analysis ... 72
6.6 Conclusion ... 72
CHAPTER VII ... 73
CONCLUSION ... 73
7.1 Introduction ... 73
7.2 Observation on Strengths and Weakness ... 74
7.3 Proposition of Improvement ... 74
ix
7.4.1 Contribution to Individual ... 75
7.4.2 Contribution to the University ... 75
7.4.3 Contribution to the shopping mall ... 75
7.5 Conclusion ... 75
REFERENCES ... 76
BIBLIOGRAPHY ... 78
LIST OF TABLES
Table 2.4-a : Software Requirement ... 8
Table 2.4-b: Hardware Requirement ... 8
Table 2.5-a: Project Milestones ... 9
Table 3.3-a : Functional Requirement of SMPTS... 14
Table 3.3-b: Performance of SMPTS ... 16
Table 3.3-c: Integrity of SMPTS... 16
Table 3.3-d: Reliability and availability of SMPTS ... 17
Table 3.3-e: Security of SMPTS ... 17
Table 3.3-f: Reusability of SMPTS ... 17
Table 3.3-g: Usability of SMPTS ... 18
Table 3.3-h: Manageability of SMPTS ... 18
Table 4.2-a: Input Design for SMPTS ... 26
Table 4.2-b: Accounts Table ... 31
Table 4.2-c: Friends Table ... 33
Table 4.2-d: Posts Table ... 34
Table 4.2-e: Chats Table... 35
Table 4.2-f: Privacies Table ... 36
Table 4.2-g: Notifications Table... 38
Table 4.2-h: Weathers Table ... 39
Table 4.2-i: Questions Table ... 40
Table 4.2-j: Likes Table ... 41
Table 4.2-k: Likes Table ... 42
Table 4.2-l: Shopping Table ... 43
Table 4.2-m: ShoppingPost Table ... 44
Table 4.2-n: Country Table ... 47
Table 5.2-a: Implementation Environment ... 58
xi
Table 5.4-a: implementation status for each module. ... 65
Table 6.2-a: Test Organization ... 68
Table 6.2-b: Test Schedule for SMPTS ... 69
LIST OF FIGURES
Figure 2.3-a: Evolutionary Model ... 7
Figure 3.3-a: Use Case Diagram for SMPTS... 15
Figure 4.2-a: System Architecture of SMPTS ... 20
Figure 4.2-b: Registration’s Interface ... 21
Figure 4.2-c: Login’s Interface ... 22
Figure 4.2-d: Home Page’s Interface for SMPTS ... 22
Figure 4.2-e: Promotion List Posted by User ... 23
Figure 4.2-f: Add New Post’s Interface ... 24
Figure 4.2-g: Statistic and Setting Tools ... 24
Figure 4.2-h: Navigation Design for SMPTS ... 25
Figure 4.2-i: Null class name text field alert box for SMPTS ... 25
Figure 4.2-j: Update Profile Interface ... 27
Figure 4.2-k: Chatting Interface ... 28
Figure 4.2-l: ERD of SMPTS ... 30
Figure 5.2-a: Deployment diagram of SMPTS ... 59
Figure 5.2-b: Software Architecture for SMPTS ... 60
Figure 5.2-c: Authentication required when accessing the database. ... 61
Figure 5.2-d: Database of SMPTS. ... 61
Figure 5.3-a: The sequence of Installation Tools for SMPTS ... 63
xiii
LIST OF ABBREVIATION
ERD - Entity Relationship Diagram FR - Functional Requirement ITP - Integration Testing Plan N/A - Not Applicable
NFR - Non Functional Requirement SC - Security Characteristics
SCM - Software Configuration Management SDE - Software Development Environment
SMPTS - Shopping Mall Promotion Tracking System
ST - System Testing
CHAPTER I
INTRODUCTION
1.1 Introduction
Today, people are living in the hassle and bustle of busy city life where this busy lifestyle leave them a little time to seek for more information on promotions held by shopping malls. This eventually causes them to miss out great promotions and also reduce their shopping experience. Thus, by developing Shopping Mall Promotion Tracker Subsystem (SMPTS), it is believed that this system can help people to be more aware on the promotions held by shopping malls.
2
1.2 Problem Statement
This project embarks on the following objectives:
i) To let people be aware about the latest promotion of the shopping mall
As people today are busy with their working life and tend to miss out the great promotions, with the help of SMPTS, promotion and latest up-to-date sales information is literally at the fingertips. People can relate the promotion activity with geo-tagging capabilities using map in Pin-It.
ii) To enable user to access more information about the promotion that is being held by certain shopping malls through online
All information about the promotion that is being held by the shopping malls can easily be accessed, at the press of a button. User can now use smart phones or laptop to check product price.
iii) To enable stakeholders of shopping mall promote products using eco-friendly method
With SMPTS, the company no longer need to waste money on printing brochures as all promotion are done through online.
1.4 Scope
4
1.5 Project significance
SMPTS has a great potential to use in various fields of application. With this new technology, user will be able to gain more knowledge about the promotion that is held by the shopping mall. This eventually will help them to spend their expenses wisely and also will become an updated consumer. Besides, this system will be able to help the shopping malls to promote their products. They no longer need to print brochures in order to inform the public about the promotion, which is more eco-friendly.
1.6 Conclusion
CHAPTER II
LITERATURE REVIEW AND PROJECT METHODOLOGY
2.1 Introduction
This section of report will discuss the literature review and methodology used in this project.
2.2 Fact and finding (based on topic)
6
opportunity for everyone to become knowledgeable about what is “out there”. The appropriate maps can be printed any time when a local community group needs information about an area.
According to Simbirsk Technologies Ltd (2013), promotion is one of the marketing tools which are developed to attract and retain customers. The creation of CS-Cart Promotion System is intended to provide customers with promotional offers. The system is quite easy and pleasure to use as variety of promotions such as discount on products, additional free products or a gift certificate can be offered through the system. For customers, they will be able to view promotion details and select their product.
According to Trade Area Systems (TAS) (Atelierlks, 2009), the browser-based solution built on Microsoft Bing Maps allows users to collaborate with other TAS Unity users and enable business users to obtain and share the information of company. TAS Online TM is the
The evolutionary methodology has been selected as the software development reference to this project after conducting review and comparison against other methodologies available. The evolutionary model is a two-dimensional software life-cycle model which considers the software development process as continuous evolution of object as for software products have their feature sets redefined during development because of external factor or user requirements.
This model act as a maintenance-oriented process as it is based on a tree of engineering decisions made at various times. This model has five phases through the phases of Planning, Analysis, Design, Implementation, and Maintenance (Hoffer, George, & Valacich, 2008, p.138).
For the second-generation, system is developed from the first generation based on the improvements proposed in the previous step. When the system is tested as was the first, its performance is evaluated and possible improvements are determined. The process is repeated as many times as necessary (regression testing) to obtain user satisfactory. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.
8
2.4 Project Requirements
This section introduces the requirement of project which is categorized into two parts, software requirement and hardware requirement.
2.4.1 Software Requirement
This section introduces the requirement of software for the project. Table 2.4-a : Software Requirement
Item Description
Windows Professional 7 Operating System
Start UML Unified Modelling Language Tool
MySQL Database Database for the system
Adobe Dreamweaver Used to create web pages (not just web pages that happen to be the primary landing page).
Ajax Web applications can send data to, and retrieve data from, a server asynchronously (in the background) without interfering with the display and behavior of the existing page.
2.4.2 Hardware Requirement
This section introduces the requirement of hardware for the project. Table 2.4-b: Hardware Requirement
Suggested Configuration Minimum Configuration
4GB RAM (Random Access Memory) 1GB RAM
A project schedule and milestones represents the action plan throughout the development phases. Action is divided into sub action or task to be accomplished in a certain timeline. The timeline is estimated by including the extra duration to the task. In this project, Gantt chart is used to represent the tasks distribution with timing. Refer Appendix 2.1 for Gantt chart. The table below shows the project milestones of SMPTS.
Table 2.5-a: Project Milestones
Task Name Duration Start Finish
SMPTS FOR PIN-IT SOCIAL NETWORK 137 days Mon 2/11/13 Tue 8/20/13
Project Kick-Start 5 days Mon 2/11/13 Fri 2/15/13
Meeting with supervisor 1 day Mon 2/11/13 Mon 2/11/13
Define objective, scope, problem statement, and
project significant. 1 day Tue 2/12/13 Tue 2/12/13
Submit proposal and Gantt chart. 2 days Wed 2/13/13 Thu 2/14/13
Approval Obtained 1 day Fri 2/15/13 Fri 2/15/13
Planning Stage 16 days Mon 2/18/13 Mon 3/11/13
Complete Chapter 1: Introduction 7 days Mon 2/18/13 Tue 2/26/13
Submit Chapter 1 1 day Wed 2/27/13 Wed 2/27/13
Complete Chapter 2: Literature Review and
Methodology 7 days Thu 2/28/13 Fri 3/8/13
Submit Chapter 2 1 day Mon 3/11/13 Mon 3/11/13
Approval obtained 1 day Mon 3/11/13 Mon 3/11/13
Analysis Stage 17 days Tue 3/12/13 Wed 4/3/13
Study similar system 3 days Tue 3/12/13 Thu 3/14/13
Study similar system's database 3 days Fri 3/15/13 Tue 3/19/13 Revise analysis documents 3 days Wed 3/20/13 Fri 3/22/13 Complete Chapter 3: Analysis 7 days Mon 3/25/13 Tue 4/2/13
Submit Chapter 3 1 day Wed 4/3/13 Wed 4/3/13
Approval obtained 1 day Wed 4/3/13 Wed 4/3/13
Design Phase 74 days Thu 4/4/13 Tue 7/16/13
Design Database 5 days Thu 4/4/13 Wed 4/10/13
Create ERD 3 days Thu 4/11/13 Mon 4/15/13
Design System Functions 5 days Tue 4/16/13 Mon 4/22/13