Page 1 of 46

Table of Contents

I. Executive Summary .............................................................................................................. 2
II. Introduction .......................................................................................................................... 3
Company Profile ................................................................................................................... 3
Company History .................................................................................................................. 3
System Overview .................................................................................................................. 9
System Goal and Objectives ............................................................................................... 9
Scope and Limitations ........................................................................................................10
Assumption..........................................................................................................................10
III. Analysis of the Existing System .......................................................................................11
Use Case Diagram and Use Case Narratives .....................................................................11
Activity Diagrams: ...............................................................................................................20
RCA Diagrams: ....................................................................................................................27
Problems and Recommendations ......................................................................................30
IV. Design of the Proposed System .......................................................................................31
System Features and Functionalities .................................................................................31
Site Map / Program Hierarchy and Screen UI Designs/ Mock-ups ...................................34
Screen UI Designs or Mockups ..........................................................................................37
V. References ..........................................................................................................................42
VI. Appendices ........................................................................................................................43



Page 2 of 46

I. Executive Summary

In the Philippines, passengers usually commute by bus especially when their destination are
provinces since the tickets of the bus are cheaper than airplane fares. It will take a long time for
the passengers arrive to their destination. For provinces like Isabela, it will take 8-10 hours
before the passengers arrive there. On the other hand, if they travel by airplane, it will only take
1-2 hours for them to arrive to Isabela. And according to the National Statistical Coordination
Board, there were 8,769 registered vehicles in 2011.

The members of this study conducted a research on the process of how passengers purchase
their tickets when boarding a bus. According to our research, we found out that passengers go
to the bus terminals ticket booth to purchase the tickets.

The members chose to provide a BOTS (Bus Online Ticketing System) which will contain
information about the departure time, arrival time, destination and date of the ticket. We want to
help reduce the hassle of purchasing the tickets by proposing this system for the passengers.

The proposed system allows the passengers to reserve their tickets online. They just need to fill
out the form about their personal information, route, bus class and the number of tickets they
will purchase. In order to pay the tickets, the user must print out the itinerary receipt that will be
presented in banks or bayad centers. Users can create their account to track their transactions
with the company. They can also re-schedule or cancel their trip. With an account, they will also
be able to comment, send suggestions and feedback to the company.











Page 3 of 46

II. Introduction

Company Profile

ALPS THE BUS INC (ALPS) is a family corporation. Owned by the Perez family from Dagatan,
Batangas. Formerly led by the head of the family the late Mr. Arcadio L. Perez, from whom the
name ALPS was coined. He was the first President and General Manager of the company. His
wife, Mrs. Consolacion E. Perez is the current president of the company. Being a Family owned
Company Their children take charge in the major positions themselves : Mr. Felix E. Perez -
Vice President for Operations & Purchasing Manager and Mrs. Lourdes Perez-Cleofe, the
youngest in the family is the Corporate Secretary and the Senior Vice President / Finance
Manager. ALPS so far has gone quite a distance and still running towards the direction probably
farther than our eyes can see or broader than our minds could imagine, because it is the
family's vision to grow and to grow in the service of the commuting public, the ALPS adopted
family


Company History

Vision Statement
We want to be a dynamic, modern, reputable and the safest transport company with an
increasing share in the transport market, ensuring constant customer satisfaction and
performance improvement with respect to our environment and safety while delivering our
services. Our corporate vision is to become the best transportation company providing services
of regional and domestic passenger road transport in the Philippines.

Mission Statement
ALPS THE BUS' corporate mission is to provide services of high quality and safe transportation
to public, to approach actively to the resolution of any customer needs, to face any challenges
within bus and coach transport nationwide, as well as to increase efficiency and effectiveness of
all activities performed in favour of fulfilment of common goals set by our shareholders,
management and employees.

Products and Services
Services
Page 4 of 46

We want to care about our customers. Travelling by bus or coach is not only a transportation
service but it is also a way of attending to our customers' needs. We do our best to make your
travelling more comfortable, safe and enjoyable. We want to be partners to our customers.

Customer Services

General Travel Information
Where does ALPS travel?
ALPS have the following TRAVEL DESTINATIONS:
1.) Alabang Grand Terminal to Batangas City Pier and vice versa
2.) Araneta Center Bus Terminal, Cubao Quezon City to Batangas City Pier and vice versa
3.) ALPS EDSA Terminal, EDSA Southbound fronting Nepa Q-mart to Batangas City Pier and
vice versa
4.) ALPS EDSA Terminal, EDSA Southbound fronting Nepa Q-mart to San Juan, Batangas and
vice versa
5.) Club Manila East Terminal, Taytay to either Naga or Legaspi or Tabaco and vice versa
6.) Araneta Center Bus Terminal, Cubao Quezon City to either Naga or Legaspi or Tabaco and
vice versa
7.) Batangas City Grand Terminal to Nasugbu Batangas and vice versa

How are the buses equipped?
Yes. All ALPS' air-conditioned buses are equipped with free WIFI connections, DVD Player,
television, air conditioning, reclining seats with headrests, and curtain covered windows.

Do the buses make stops?
Most buses make intermediate stops to either pick up additional passengers or to drop
passenger en route to their destinations.

Are stopovers permitted?
Stopovers are only permitted for BICOL route.

On-Board Information
Is there assigned seating on ALPS?
Page 5 of 46

Seating is on a first-come, first-served basis for Batangas City to Manila route. However,
reserve seats are assigned for reservation on BICOL routes.

Is smoking allowed on board?
ALPS does not permit smoking on air conditioned buses.

Are meals provided on board?
No. Meals are not provided.

Are food and drink allowed on board?
Yes. Food and non-alcoholic drinks/beverages may be carried on board for personal
consumption.

Are radios, laptops, cellular phones, or electronic gadgets allowed on buses?
Radios, laptops and other electronic items may be carried on board, provided that they do not
disturb fellow passengers and that headphones are used.

Are pets allowed on board?
Any kinds of pets are strictly not allowed on board.

Are pillows and blankets available for nighttime travel?
No, but you are welcome to bring your own within your carry-on luggage.

Does all buses show movies?
No. However all air conditioned bus show movies en route

Passenger Services

Are route maps available?
Route maps are not available.

Does ALPS have discount programs for students?
Yes. ALPS maintains a 20 percent discount for students applicable only for non-air conditioned
buses only.
Page 6 of 46

Does ALPS have discount programs for seniors?
Yes. Passengers 60 years and older who are able to present a Senior Citizen ID provided by
Municipal Mayor can avail 20 percent discount.

Does ALPS have discount programs for children?
Yes. ALPS maintains a half-price fare for children above 2 years and below 10 years old for
ordinary buses only.

Does ALPS have any programs for Passengers with Disabilities?
Yes, the front right seat near the door are reserve for disabled individual.

Does ALPS have a policy with regard to unruly passengers?
ALPS reserves the right to refuse to transport a person under the influence of intoxicating liquor
or drugs or who refuses to comply with any lawful rule or regulations. If you witness any unruly
behavior or suspect any trouble with a fellow passenger during your trip, please notify the driver.

Fares and Schedule

How do I locate information for the nearest ALPS terminal?
Please check our Terminal page for location details, or check the yellow pages of a local phone
directory.

Are there discount fares available?
Yes. There are discounts available for children, college students and seniors over age 60.
Appropriate identification may be required for these discounts.

Are there children's fares?
Yes. Children 44" tall ride free when accompanied by an adult.

May children travel alone on ALPS
Yes. Any passenger between the ages of eight and 14 may travel. The child must pay adult fare.


Does ALPS guarantee its departure and arrival times?
Page 7 of 46

No. However, ALPS makes its best effort to provide on-time service, it does not guarantee its
departure and arrival times, which may be delayed by any number of factors, including weather,
traffic, or mechanical problems.

Ticketing
Is the ticket available at the terminal?
For Batangas to Manila and vice versa, the tickets are given by the conductor aboard the bus.
For BICOL routes, tickets are given or reservations can be made on specified booking stations
on Reservation section.

Is ticket refundable?
For Batangas to Manila and vice versa, refund of ticket is strictly prohibited. However in case of
mechanical failure and the bus is unable to continue to travel passengers will be transfered into
another bus going to the same destination.
For BICOL routes, tickets are refundable but 20% of the amount will be deducted against the
amount of the ticket to be refunded for cancellation charge.

Baggage Information
What are the restrictions on carry-on baggage?
In order to provide all passengers with reasonable safety and comfort on board, carry-on
baggage is restricted to two carry-on pieces per person, both of which must fit either overhead
or under the seat of the passenger. However, if the passenger has a bulky baggage it will be put
on the compartment of the bus and its corresponding payment will depend on the negotiation
between the conductor and passenger. Passengers are reminded to keep their valuables with
them at all times.

What if I lost my baggage while on board the bus?
Any negotiation that will arise regarding baggage the passenger or claimant will pursue his
claims to ALPS' main office.

Customer Assistance



Page 8 of 46

Organizational Chart:
As of August 2014

Page 9 of 46



System Overview

The system allows the users to reserve and purchase tickets without directly going to the ticket
store. Its main purpose is to give convenience to travelers by reducing/avoiding long lines
especially during peak days. It also allows admins to know the number of travelers per day,
places where most travelers go and other reports. Users could also send feedbacks and
suggestions to the admin. Users can create their accounts as well (optional). When they have
account, they could trace transactions they had with the company. This system also aims to
minimize the hassle for the customer, it also minimizes all the errors that can occur when
bought on-counter and lastly, it reduces the work force needed, that would help the company
save up.

System Goal and Objectives

Bus Online Ticketing System (BOTS)s goal is to give a better and easier access for the
customer and a better system for the bus company. The objectives of our system are two-fold.
Firstly, for the company to raise their profits and customers attraction since there are lots of
option for the commuters like MRT, LRT, taxi and airplane. Secondly, the system will aid
Page 10 of 46

customers in purchasing their bus tickets. With our system, the customers can reserve and
purchase the bus tickets online. This will not only be convenient for them, but it will also save
their time since they dont have to go to the bus terminal anymore.

Scope and Limitations

The scope of this ticketing system is that it is easy to access everywhere, all you need is an
internet connection, with this system you can easily view the crowd control in the vicinity of the
terminal, you can also know what are the time of departure and arrival of other trips. This
system also gives a ticket reservation, if you are still uncertain of the date that you will travel,
you can reserve it.

The limitation of this system is users will not be able to use any credit card or online payment
account. Instead, they will be given itinerary receipt and which they can present at banks and
bayad centers

Assumption

The priority of the company at the time of study is at least the existing system can track how
many tickets they sold and if there are people who reserve a ticket for the coming trip.

After we analyzed the existing system, we proposed the BOTS (Bus Online Ticketing System)
wherein customer can reserve a ticket online after she/he filled-up the reservation form. The
customer can also purchase the ticket online, and just like reservation she/he needs to fill-up the
form. This is so that the company will create/update the record of the customer, especially the
tickets destination. They can also cancel the ticket they purchased/reserved if there are any
changes in their plan. System also automatically tracks how many ticket was sold and how
many people has reserved a ticket.

We assumed that this system will help the bus company to make their work easier because
everything will be automated by the system. Another is that it will also attract customers since it
also provides convenience to the customer because they can do their reservation/purchasing of
ticket online. With these, the company will gain more profit from it.

Page 11 of 46


Glossary:

BOTS - Bus Online Ticketing System
Customer - The one who purchases/reserves ticket at the bus terminal.
Cashier - The one who processes the ticket of the customer.


III. Analysis of the Existing System

Use Case Diagram and Use Case Narratives







Page 12 of 46


Identification Summary
Title: Go to bus terminal
Summary: This use case describes the steps associated with going to the bus terminal.
Actors:
1. Customer - goes to the bus terminal

Creation Date: August 16, 2014 Date of Update: August 23, 2014
Version: v1.0 Person in Charge: Marianne Pua

Flow of Events
Preconditions:
1. Customer must have money for the transportation to the bus terminal.

Main Success Scenario:
1. Customer rides any kind of transportation (jeepney, bus or lrt)
2. Customer waits until he reaches the bus terminal..
3. Customer gets off at the bus terminal.

Alternative Sequences
A3. Customer wasnt able to get off at the exact place of bus terminal.
1. Customer walks towards the bus terminal.

Error Sequences
E1. Customer ride the wrong transportation (transportation doesnt pass by the bus terminal)
1. Use case ends.

Post Conditions
1. Customer arrived at the bus terminal.





Page 13 of 46


Identification Summary
Title: Queue in Line
Summary: This use case describes the steps associated with queueing in line.
Actors:
1. Customer - queues in line for the ticket

Creation Date: August 10, 2014 Date of Update: August 23, 2014
Version: v1.0 Person in Charge: Julie Mansalapus

Flow of Events
Preconditions:
1. Customer must be in the bus terminal

Main Success Scenario:
1. Customer goes to bus terminal
2. Customer falls in line of the ticket booth.
3. Customer waits for his turn.

Alternative Sequences
A2. The person ahead of the customer is taking too long.
1. Use case proceeds to step 3 of main success scenario.
Error Sequences
E2. Customer queued in the wrong lane.
1. Customer decided not to queue again.
2. Use case ends


Post Conditions
1. Customer is waiting in line at the ticket booth.




Page 14 of 46


Identification Summary
Title: Select ticket
Summary: This use case describes the steps associated with selecting the ticket.
Actors:
1. Customer - selects the ticket he will buy.
2. Cashier - checks the availability of the tickets

Creation Date: August 10, 2014 Date of Update: August 23, 2014
Version: v1.0 Person in Charge: Jericho Piana

Flow of Events
Preconditions:
1. Customer must be in the bus terminal to be able to select the ticket.

Main Success Scenario:
1. Customer asks what tickets are available.
2. Cashier checks availability of tickets
3. Cashier tells customer the available tickets
4. Customer selects the ticket

Alternative Sequences
A3. The ticket is not available
1. Customer asks the cashier again about the other tickets
2. Use case proceeds to step 2 of main success scenario.

Error Sequences
E3. Customer accidentally selects the wrong ticket.
1. Cashier created a transaction for the customer already.
2. Customer wanted to change his ticket.
3. Cashier doesnt allow the customer to change the ticket since it is already recorded in
the transaction.
4. Use case ends (?)

Page 15 of 46

Post Conditions
1. Customer has already chosen a ticket.


Identification Summary
Title: Pays for ticket
Summary: This use case describes the steps associated with paying the ticket.
Actors:
1. Customer - pays the ticket he will buy.
2. Cashier - receives the payment for the ticket

Creation Date: August 16, 2014 Date of Update: August 23, 2014
Version: v1.0 Person in Charge: Shahin Sepasi

Flow of Events
Preconditions:
1. Customer must have money to buy the ticket.

Main Success Scenario:
1. Customer asks the price of the ticket.
2. Cashier checks the price of the ticket.
3. Cashier tells customer the price of the ticket.
4. Customer gets money from wallet.
5. Customer gives payment to the cashier.

Alternative Sequences
A3. Customer forgot to bring money to pay for the ticket.
1. Customer will go and get money from his house
2. Use case resumes at step 1 of main success scenario.


Error Sequences.
E1. Customers money is not enough to pay the ticket.
1. Customer leaves the bus terminal
Page 16 of 46

2. Use case ends.
E3. Cashier commits error in telling the customer the price of the ticket.
1. Cashier checks the price of the ticket again.
2. Use case ends

Post Conditions
1. New order transaction.
2. Customer paid his ticket.


Identification Summary
Title: Check availability of tickets
Summary: This use case describes the steps associated with checking the availability of the
tickets.
Actors:
1. Customer - asks what are the available tickets.
2. Cashier - checks the availability of the tickets

Creation Date: August 16, 2014 Date of Update: August 27, 2014
Version: v1.0 Person in Charge: Julie Mansalapus

Flow of Events
Preconditions:
1. Cashier must have the machine needed to check the availability of the ticket.

Main Success Scenario:
1. Customer asks cashier what tickets are available.
2. Cashier uses machine to check availability of tickets.
3. Customer confirms what she/he want on the available tickets.


Alternative Sequences
A2. Customer wants to change the ticket he chose
1. Customer asks cashier what are the other tickets.
Page 17 of 46

2. Use case proceeds to step 2 of main success scenario
Error Sequences
E3. An error occurred during checking of the available tickets.
1. Use case ends

Post Conditions
1. Cashier checked the availability of ticket for the customer.


Identification Summary
Title: Receives payment
Summary: This use case describes the steps associated with receiving the payment of the ticket.
Actors:
1. Customer - pays for the purchased ticket.
2. Cashier - receives the payment of the ticket.

Creation Date: August 19, 2014 Date of Update: August 23, 2014
Version: v1.0 Person in Charge: Marianne Pua

Flow of Events
Preconditions:
1. Customer must give money to the cashier.

Main Success Scenario:
1. Customer asks the price of the ticket.
2. Cashier checks price of ticket.
3. Cashier tells customer price of the ticket.
4. Customer gives payment to cashier.
5. Cashier receives payment.

Alternative Sequences
A4. Customer doesnt have enough money to pay for the ticket.
1. Customer leaves the bus terminal to get money.
2. Customer comes back to the terminal.
Page 18 of 46

3. Customer goes to the ticket booth.
4. Use case proceeds to step 4 of main success scenario.

Error Sequences
E5a. Cashier noticed that he received fake money.
1. Cashier returns money to the customer
2. Customer receives his fake money.
3. Use case ends.

E5b. Cashier didnt notice that he received fake money.
1. The cashiers salary will be deducted by the amount of the fake money.
2. Use case ends.

Post Conditions
1. Cashier received the payment of the ticket from the customer.


Identification Summary
Title: Gives ticket to the customer
Summary: This use case describes the steps associated with giving the ticket to the customer.
Actors:
1. Customer - receives ticket given by the cashier
2. Cashier - gives ticket to the customer

Creation Date: August 27, 2014 Date of Update: August 29, 2014
Version: v1.0 Person in Charge: Julie Mansalapus

Flow of Events
Preconditions:
1. Customer must give payment to the cashier.


Main Success Scenario:
1. Cashier prepares the ticket bought by the customer.
Page 19 of 46

2. Cashier gives the ticket to the customer
3. Customer receives the ticket.
4. Customer leaves the bus terminal.

Alternative Sequences
A2. Customer forgot to take his ticket.
1. Cashier will call the attention of the customer.
2. Cashier will give the ticket to the customer.

A2. Cashier gives accidentally gives the wrong ticket.
1. Customer gives back the wrong ticket to the cashier.
2. Cashier gives the correct ticket to the customer.

Error Sequences
E2. Customer did not receive the ticket.
1. Use case ends.

Post Conditions
1. Customer received the ticket.
2. Updated daily sales
3. New transaction record.













Page 20 of 46

Activity Diagrams:

1. Go to bus terminal







Page 21 of 46

2. Queue in Line











Page 22 of 46

3. Select ticket














Page 23 of 46

4. Pays for ticket







Page 24 of 46

5. Check availability of tickets
















Page 25 of 46

6. Receives payment















Page 26 of 46

7. Gives ticket to the customer










Page 27 of 46

RCA Diagrams:

Page 28 of 46





Page 29 of 46




Page 30 of 46

Problems and Recommendations


Problems Recommendations
Time and effort is being wasted because
customers have to follow the manual
procedures on purchasing their ticket.

The customers find it tiring to go to the bus
terminal and queue in long lines just to
purchase bus ticket or ask for bus schedule.
Sometimes, customers dont have time to go
to the bus terminal to purchase tickets
because of their busy schedule. Other
customers also try to call the bus companys
telephone but the line is always busy.


Create an online reservation/purchasing
system that will provide convenience to
the customers so that time and effort will
be saved.

Our system would let the customers
purchase/reserve tickets online. Customers
should go to the purchase/reservation page of
the companys website and fill up the
necessary details for the ticket. The record
would then be saved both in the account of
the customer and in the admins account.

Payment Transaction takes too long to
process due to manual operations leading
to poor customer satisfaction because of
time being wasted.

For the customers, it is very hassle to pay
their tickets at the bus terminal. In addition,
this is also causes time delay for both on the
part of the customers and cashier especially
during peak hours.



Create a feature wherein customers can
pay their tickets in any convenience store
(such as 7-Eleven, Mini Stop etc), bank or
bayad centers so that payment will be
more handier making customer
satisfaction higher.

Our system would provide the benefit of
allowing the customers to pay their ticket at
any convenience store, bank or bayad
centers. Customers should print out their
ticket and present it together with their
payment at the convenience store.
The current system does not allow ticket
cancellation that might lead customer to
dismay when they buy the wrong ticket.

Customers are not allowed to cancel their
ticket. Once they purchased it, they cant
return it to the bus company and they also
cant get back the money she/he paid. It is
also the same for the reservation of ticket.
Customers cannot cancel the ticket they
reserved.
Adds a feature that allows customers to
change or cancel their ticket so that
customer disappointment will be avoided.

Bus Online Ticketing System (BOTS) allows
the customers to cancel the ticket they
purchased/reserved 2 days before the
departure, especially if they changed their
mind or if the customer changed their plan. All
she/he has to do is go to the cancellation
page and fill-up the form in the page.
Customers have to queue in line at the
bus terminal to purchase the tickets giving
them hassles
Create an online reservation
ticket/purchasing system that will allow
customers to avail tickets online.
Page 31 of 46


Customers still need to wait in long lines
especially during peak hours in order for them
to purchase the tickets they want.

Our system allows customers to purchase
their tickets online. This will save their time
since they dont need to wait in line at the bus
terminal.
Both cashier and customers experiences
delays in checking the availability of
tickets

Before purchasing a ticket, customers usually
asks the cashier what tickets are available.
Then the cashier checks the availability of
tickets. This is very time consuming since
there may be multiple tickets for a journey.

Create a checks availability of tickets page
that allows cashier to check the
availability of tickets

Cashier can check the availability of tickets by
entering the destination and schedule of the
trip for the customers. Then the page will
display the information needed by the
customer.



IV. Design of the Proposed System

System Features and Functionalities

Functions Features
Ticket Purchasing Online ticket purchasing. Users fills out
form about what type of bus they want,
where they want to go and others.
Reporting Different graphs about different things like
the decline and increase of passengers
etc. (admin)
-Graph of an increase/decline of
passengers per month.
-Graph of places where most travellers go
including time/season they go there.
-Graph of an increase/decline of sales.
-Comments, feedbacks and suggestions
Page 32 of 46

of users.
Customers feedback This will help the company to improve
more by knowing the insights and the
comments of the customers.
Vicinity Viewing/Checking

With this , the customer will know
-How crowded the vicinity is, so he/she
will be ready for whats waiting for
him/her.
-Either live stream of cctv camera or
simply providing a graph or an illustration
about how crowded it could be.
Trip Check Trip Check provides the information that is
needed by a customer, whether he/she
waiting for his/her departure time, or the
arrival of someone special.
-Users will be able to view schedules
of different trips and departures.
-Users will be able to view if the trip
has been cancelled.

Ticket Reservation -User can reserve tickets weeks before
the prior time of departure.
-Users will be able to view available
travel destination, type of buses.
-They will not be paying it online,
instead they will be given an itinerary
which they can use to pay at bayad
centers (see Payment)
-Seat Selection
-Interactive Map for route selection
Page 33 of 46

Payment The user will pay via print out or itinerary
receipt, that will be presented in banks or
bayad centers.
-No payment transaction will be made
online, users like said above will receive
an itinerary or temporary ticket.
Ticket/Reservation Cancellation User can cancel 2 days before the
departure.
Trip Rescheduling/Account Logging in Users can create an account for them to
be able to track their transactions with the
comp.
-With an account, they will be able to
re-schedule/cancel their trip.
-They will also be able to comment,
and send suggestions and feedback, view
new promos and packages.














Page 34 of 46


Site Map / Program Hierarchy and Screen UI Designs/ Mock-ups

Site Maps:

Visitor















Page 35 of 46

User:




















Page 36 of 46

Admin:
















Page 37 of 46

Screen UI Designs or Mockups


(Index page)



(Home page)
Page 38 of 46



(Routes page)



(Buy ticket page)



Page 39 of 46



(About us page)



(Coming up soon page)

Page 40 of 46


(Mobil app page)


(How to buy page)




Page 41 of 46



(User login page)



(Reports page)





Page 42 of 46

V. References

About Us. (February 26, 2013). Retrieved [August 21, 2014], from [ALPS The Bus, Inc.]
Web site: [http://www.alpsthebus.com/]

Goal vs Objective. (August 27, 2014). Retrieved [August 29, 2014], from [Goal vs Objective -
Difference and Comparison | Diffen.] Web site:
[http://www.diffen.com/difference/Goal_vs_Objective]


























Page 43 of 46

VI. Appendices

Appendix A - Transcript of Interview
Appendix B - Pictures

Appendix A

Julie: Sir, do you have any system that you use at the moment? If you have what are the usual
problems that you encounter?

Patrick: Yes, we have system that we use now but for the privacy we cant tell you what is it but
we can tell you some examples of problems that we normally encounter.

Julie: Okay sir that would be great.

Patrick: In our everyday operations, we notice that customers have difficulty on queueing in
lines especially during peak hours.

Jericho: Ohh I see. I also experience that when I buy bus tickets.

Patrick: Another is, the current system we use does not allow ticket cancellation for the
customers.

Shahin: But what will happen to the customers ticket? What if he changed his mind about the
ticket?

Patrick: Since they already purchased it, we cannot do anything to cancel it. It is already
recorded in our records.

Shahin: Ohh thats too bad.

Marianne: Do you have any more problems that your company encounters?

Page 44 of 46

Patrick: There are also customers who complain that the payment transaction takes too much
time.

Jericho: An online ticketing system will be able to solve all of your problems sir.

Julie: It does not only solve the customers complaints, but it also attracts customers since they
dont have to go directly to the bus terminal to purchase tickets.

Marianne: They can also create their account, then the transactions they made will be saved in
their account.

Patrick: Its a great idea. But I think it is limited to only people who have internet access at home.

Shahin: They can go to computer shops near them and access the website. This is more
convenient for them rather than going to the bus terminal directly.

Patrick: Other than the customers attraction, convenience, what will our company benefit from it?

Shahin: Less paperwork will be done by your staffs. since everything will be automated by the
system.














Page 45 of 46



Appendix B




Page 46 of 46