ABSTRACT
This project addresses the study and development of an Online Bus Ticketing System web portal to enable users, both the bus operators and the customers to make an online bus ticket sale/ purchase and act as an operation tool for bus operators to operate their organization effectively. Traditionally, bus ticket purchase has been over the counter in bus terminals, however, today it has evolved with the rapid expansion of e-commerce. Thus, prior to developing the system, a this research critically assess and study the reason behind the evolution and the current e-ticketing systems. This project also addresses the problems faced by customers and bus operators especially on illegal bus operators, long wait to purchase a bus ticket, unsafe environment and many more. The research studies some issues on implementation and also recommendations on how Online Bus Ticketing System web portal can take place effectively. This research recommends on a star ranking system based on monthly sales, bus operator popularity and law traffic offences. This research also recommends a Decision Support System to deal with the customer’s requirement whereby it provides reliable choices to a customer to make decision. This research includes the development of a prototype Online Bus Ticketing System web portal to support the research objective. This web portal will assist in future development that would support a fully integrated system that links bus operators to customers, bus operators to bus operators, bus operators to other mode of transport providers, bus operator to businesses and bus operators to government agencies.
3
TABLE OF CONTENTS | ||
CONTENTS | PAGE | |
Abstract | i | |
Acknowledgement | ii | |
Table of Contents | iii | |
List of Figures | ix | |
List of Tables | xiii | |
List of Appendices | xiv | |
CHAPTER 1: INTRODUCTION | 1 | |
1.1 | Introduction | 1 |
1.2 | Problem Statement | 4 |
1.3 | Objectives | 8 |
1.4 | Scope of the Research | 10 |
1.5 | Significance of the Research | 12 |
1.6 | Methodology | 12 |
1.7 | Organization of Thesis | 15 |
1.8 | Expected Research Outcome | 17 |
1.9 | Conclusion | 18 |
5
CHAPTER 2: LITERATURE REVIEW | |||
2.1 | Introduction | 19 | |
2.2 | E- Commerce | 19 | |
2.3 | Business to Consumer (B2C) | 20 | |
2.4 | Portal | 21 | |
2.5 | Management Information System | 22 | |
2.6 | Decision Support System | 24 | |
2.7 | Security | 25 | |
2.8 | Payment | 27 | |
2.9 | Analysis of Puduraya Bus Terminal | 31 | |
2.10 | Ticketing System | 34 | |
2.10.1 Analysis on the Existing Manual Bus Ticketing | 35 | ||
System | |||
2.10.2 Analysis on the Existing Computerized Bus | 36 | ||
Ticketing System | |||
2.10.3 Comparison between Manual and Computerized | 37 | ||
Ticketing System | |||
2.10.4 Analysis of Existing Online Ticketing System | 39 | ||
2.10.4.1 Malaysia | 39 | ||
2.10.4.1.1 | Plusliner Sdn Bhd | 39 | |
2.10.4.1.2 | Konsortium Bus Express | 45 | |
Semenanjung | |||
2.10.4.1.3 | The Ticketing.com | 49 | |
2.10.4.1.4 | Aeroline Malaysia | 53 | |
2.10.4.1.5 | Air Asia Sdn Bhd | 56 | |
2.10.4.2 North America | 62 |
6
2.10.4.2.1 | Greyhound Lines, Inc | 62 | |
2.10.4.2.2 | Tompkins Consolidated | 66 | |
Area Transit | |||
2.10.4.3 Hungary | 68 | ||
2.10.4.3.1 | Volanbusz.com | 68 | |
2.10.4.4 India | 71 | ||
2.10.4.4.1 SPAN Group Company | 71 | ||
2.11 | Comparison Between Existing Bus e-ticketing Systems | 75 | |
2.12 | Conclusion | 79 |
CHAPTER 3: METHODOLOGY | 80 | ||
3.1 | Introduction | 80 | |
3.2 | Choice of Methodology | 80 | |
3.3 | Research Methodology | 84 | |
3.3.1 | Fact Finding | 85 | |
3.3.1.1 Observation | 85 | ||
3.3.1.2 Interview | 85 | ||
3.3.1.3 Questionnaire | 86 | ||
3.3.2 | Prototype | 86 | |
3.4 | Questionnaire Analysis and Result | 86 | |
3.4.1 Public and bus operators’ perception towards | 87 | ||
Online Bus Ticketing System | |||
3.5 | Interview Questions and Results | 98 | |
3.5.1 Interview with Plusliner Sdn. Bhd. and Eltabina | 98 | ||
Express Sdn. Bhd | |||
3.6 | Conclusion | 103 |
7
CHAPTER 4: SYSTEM ANALYSIS | 106 | ||
4.1 | Introduction | 106 | |
4.2 | Description of the Proposed System | 106 | |
4.3 | Intended Users | 108 | |
4.4 | Brief Overview of the Proposed System Functions | 108 | |
4.5 | Functional requirement | 109 | |
4.5.1 | Administrators | 110 | |
4.5.1.1 Bus Company Information | 110 | ||
4.5.1.2 Bus Information | 111 | ||
4.5.1.3 Member Account and Staff Profile | 112 | ||
4.5.1.4 Purchasing and Booking Cancellation | 112 | ||
113 | |||
4.5.1.5 Report | |||
4.5.1.6 Authority | 114 | ||
4.5.2 | Customers | 115 | |
4.5.2.1 Main Page | 115 | ||
4.5.2.2 Registration | 117 | ||
4.5.2.3 Bus Schedule and Details | 118 | ||
4.5.2.4 Booking | 118 | ||
4.5.2.5 Payment | 119 | ||
4.5.2.6 Ticket | 119 | ||
4.5.2.7 Booking Cancellation | 119 | ||
4.6 | Bus Operator Ranking | 120 | |
4.7 | Non- functional requirement | 121 |
8
4.8 Conclusion 124
CHAPTER 5: SYSTEM DESIGN AND | 125 | ||
IMPLEMENTATION | |||
5.1 | Introduction | 125 | |
5.2 | System Functional Design | 125 | |
5.2.1 | Structure Design | 125 | |
5.2.1.1 Structure Chart for Administrator Section | 126 | ||
5.2.1.1.1 Structure Chart for Authority | 128 | ||
Module | |||
5.2.1.2 Structure Chart for Customer Section | 128 | ||
5.2.2 | Data Flow Diagram | 130 | |
5.2.2.1 Data Flow Diagram 0 | 131 | ||
5.3 | Database Design | 132 | |
5.3.1 | Data Dictionary | 132 | |
5.3.2 | Entity Relationship Model | 137 | |
5.4 | Tools and Methodology used | 138 | |
5.4.1 | Software Package used | 138 | |
5.4.2 | Tools used | 139 | |
5.4.2.1 Software Requirement | 139 | ||
5.4.2.2 Scripting Language | 139 | ||
5.4.2.3 Database Management | 140 | ||
5.4.2.4 Operating System | 140 | ||
5.5 | Hardware and Software Requirements | 140 | |
5.5.1 | Requirement for System Development | 141 | |
5.6 | Human Computer Interaction (HCI) Factors | 141 |
9
5.7 | Goals of User Interface (Usability Factors) | 142 |
5.8 | Web Page Design Principles | 143 |
5.9 | System Implementation | 144 |
5.9.1 Guidelines on How Online Bus Ticketing System | 145 | |
web portal can be implemented | ||
5.10 | Suggested Guidelines | 146 |
5.11 | Features and components of the Prototype | 147 |
5.12 | Interface Design | 147 |
5.13 | Source Codes | 147 |
5.14 | Conclusion | 148 |
CHAPTER 6: SYSTEM TESTING | 149 | ||
6.1 | Introduction | 149 | |
6.2 | Testing | 149 | |
6.2.1 | Unit Testing | 150 | |
6.2.2 | Integration Testing | 152 | |
6.2.3 | System Testing | 152 | |
6.2.4 | Acceptance Testing | 155 | |
6.2.4.1 Analysis of Bus Operator Administrator | 156 | ||
Acceptance Testing | |||
6.2.4.2 Analysis of Customer Acceptance Testing | 160 | ||
6.3 | Conclusion | 164 |
CHAPTER 7: CONCLUSION | 165 |
7.1Introduction | 165 |
10
7.2 | Outcomes of the research | 165 |
7.3 | Limitations of the research | 167 |
7.4 | Future work of the research | 167 |
7.5 | Conclusion | 169 |
REFERENCES | 294 |
11
LIST OF FIGURES | ||
Figure 1.1 | Research Process | 14 |
Figure 2.1 | Puduraya Bus Terminal | 31 |
Figure 2.2 | Scenario of traffic congestion along Jalan Pudu | 33 |
Figure 2.3 | The number of seats available for specific route | 40 |
Figure 2.4 | The Availability of seats | 40 |
Figure 2.5 | The Schedule form | 41 |
Figure 2.6 | The Fare and Schedule form | 41 |
Figure 2.7 | Membership Registration form | 42 |
Figure 2.8 | Ticket Reservation and Purchasing form | 42 |
Figure 2.9 | Seat Map | 43 |
Figure 2.10 | Confirmation slip | 44 |
Figure 2.11 | New Member Registration | 46 |
Figure 2.12 | Ticket Purchase form | 46 |
Figure 2.13 | Confirmation Information | 47 |
Figure 2.14 | Counter Location Map | 48 |
Figure 2.15 | Search form | 49 |
Figure 2.16 | Bus Schedule | 50 |
Figure 2.17 | Trips Information | 50 |
Figure 2.18 | The Member Login section of Maybank2u.com | 51 |
Figure 2.19 | Login form to Print Tickets after Payment | 52 |
Figure 2.20 | Plan Trip form | 54 |
Figure 2.21 | Select Form | 54 |
Figure 2.22 | Confirmation form | 55 |
12
Figure 2.23 | Payment form | 55 |
Figure 2.24 | Air Asia Flight Search form | 57 |
Figure 2.25 | Flight information using the search function | 58 |
Figure 2.26 | The confirmation screen provided by airasia.com | 59 |
Figure 2.27 | The contact screen | 60 |
Figure 2.28 | The Purchase screen | 61 |
Figure 2.29 | Buy Tickets form | 63 |
Figure 2.30 | The Discount form | 63 |
Figure 2.31 | The Schedule form | 64 |
Figure 2.32 | The Fares form | 64 |
Figure 2.33 | The Purchase form | 65 |
Figure 2.34 | The “Plan A Trip” form | 67 |
Figure 2.35 | The online ticket booking form | 69 |
Figure 2.36 | Available dates traveling form | 69 |
Figure 2.37 | Conformation form | 70 |
Figure 2.38 | Conformation Ticket | 70 |
Figure 2.39 | Journey and date departure screen | 72 |
Figure 2.40 | The current status screen | 72 |
Figure 2.41 | The booking details and seat selection screen | 73 |
Figure 2.42 | Personal Information form | 73 |
Figure 2.43 | Final Conformation form | 74 |
Figure 2.44 | Payment details form | 74 |
Figure 3.1 | Waterfall model | 81 |
Figure 3.2 | Age Distribution of Respondents | 88 |
13
Figure 3.3 | Respondents who have conducted an Online | 90 |
Payment through Internet | ||
Figure 3.4 | Awareness of Existence of bus e-ticketing systems | 91 |
Figure 3.5 | Satisfaction of services provided in the existing | 94 |
Online Bus Ticketing Systems | ||
Figure 3.6 | Reasons for using services from 1 type of bus | 95 |
operator | ||
Figure 3.7 | Preferred Payment options for future Online Bus | 95 |
Ticketing System | ||
Figure 5.1 | Structure design of Online Bus Ticketing Main | 126 |
System | ||
Figure 5.2 | Structure chart for Online Bus Ticketing System | 127 |
Administrator Section | ||
Figure 5.3 | The Structure Chart for the Online Bus Ticketing | 128 |
Authority Module | ||
Figure 5.4 | The Structure Chart for the Online Bus Ticketing | 129 |
Customer Section | ||
Figure 5.5 | The Online Bus Ticketing System Context | 130 |
Diagram | ||
Figure 5.6 | Data Flow Diagram 0 for Online Bus Ticketing | 131 |
System | ||
Figure 5.7 | Entity Relationship Diagram for Online Bus | 137 |
Ticketing System | ||
Figure 5.8 | Framework for Online Bus Ticketing System web | 146 |
portal Implementation | ||
Figure 6.1 | Respondents who have rated the systems features | 156 |
and functionalities | ||
Figure 6.2 | Respondents who have rated the familiarity of the | 157 |
Online Bus Ticketing System web portal | ||
Figure 6.3 | Respondents who have rated the system | 157 |
helpfulness in their daily operations |
14
Figure 6.4 | Respondents who have rated for additional features | 158 |
and functions in the system | ||
Figure 6.5 | Respondents who have rated the Online Bus | 159 |
Ticketing web portal interface design | ||
Figure 6.6 | Respondents who have rated the Online Bus | 159 |
Ticketing web portal | ||
Figure 6.7 | Respondents who have rated the systems features | 160 |
and functionalities | ||
Figure 6.8 | Respondents who have rated the familiarity of the | 161 |
Online Bus Ticketing System | ||
Figure 6.9 | Respondents who have rated helpfulness in ticket | 162 |
purchasing | ||
Figure 6.10 | Respondents who have rated for additional features | 162 |
and functions in the system | ||
Figure 6.11 | Respondents who have rated the Online Bus | 163 |
Ticketing web portal interface design | ||
Figure 6.12 | Respondents who have rated the Online Bus | 164 |
Ticketing web portal |
15
LIST OF TABLES | ||
Table 2.1 | Comparison summary between manual and | 38 |
computerized Ticketing System | ||
Table 2.2 | Summary of the features available between the | 77 |
existing online ticketing systems | ||
Table 3.1 | Respondents view on condition in Puduraya Bus | 89 |
Terminal | ||
Table 3.2 | Effectiveness of Online Bus Ticketing System | 92 |
Table 6.1 | Unit Testing for Administrator login module | 150 |
Table 6.2 | Unit Testing for the Administrator Ticket Booking | 151 |
module | ||
Table 6.3 | Integrated Testing for the Administrator Booking | 153 |
Ticket module | ||
Table 6.4 | Integrated Testing for the Administrator Ticket | 153 |
Cancellation module | ||
Table 6.5 | Integrated Testing for the Customer Booking | 154 |
Ticket module | ||
Table 6.6 | Integrated Testing for the Customer Ticket | 155 |
Cancellation module |
16
LIST OF APPENDICES | ||
A: | List of Bus Operators and Taxi at Puduraya Bus Terminal | 171 |
B: | Questionnaire Form | 174 |
C: | Bus Schedule of Plusliner Sdn Bhd | 195 |
Reservation and Purchasing form of Eltabina Express | 197 | |
Sdn Bhd | ||
D: | System Evaluation Form | 199 |
E: | Commercial Banks in Malaysia | 203 |
F: | Interface Design (Administrator) | 204 |
G: | Interface design (Authority) | 227 |
H: | Interface Design (Customer) | 230 |
I: | Source Codes (Administrator section) | 253 |
J: | Source Codes (Authority section) | 283 |
K: | Source Codes (Customer section) | 385 |
DISCLAIMER: All project works, files and documents posted on this website, eProjectTopics.com are the property/copyright of their respective owners. They are for research reference/guidance purposes only and some of the works may be crowd-sourced. Please don’t submit someone’s work as your own to avoid plagiarism and its consequences. Use it as a reference/citation/guidance purpose only and not copy the work word for word (verbatim). The paper should be used as a guide or framework for your own paper. The contents of this paper should be able to help you in generating new ideas and thoughts for your own study. eProjectTopics.com is a repository of research works where works are uploaded for research guidance. Our aim of providing this work is to help you eradicate the stress of going from one school library to another in search of research materials. This is a legal service because all tertiary institutions permit their students to read previous works, projects, books, articles, journals or papers while developing their own works. This is where the need for literature review comes in. “What a good artist understands is that nothing comes from nowhere. The paid subscription on eProjectTopics.com is a means by which the website is maintained to support Open Education. If you see your work posted here by any means, and you want it to be removed/credited, please contact us with the web address link to the work. We will reply to and honour every request. Please notice it may take up to 24 – 48 hours to process your request.