Declaration

I, [Your Full Name], hereby declare that the work presented in this project, titled "[Project Title],"
is entirely my own effort. All the ideas, concepts, and findings expressed herein are original and
have not been submitted for any other academic purpose.

I affirm that all external sources used in this project have been duly acknowledged through proper
citations. Any references to the work of others are clearly indicated, and the intellectual property
of those sources has been respected.

I take full responsibility for the accuracy and authenticity of the content presented in this project.
No part of this work has been plagiarized, and all ethical standards in research and academic
integrity have been strictly adhered to.

Furthermore, I understand the consequences of academic dishonesty and declare that this project
represents an honest and genuine effort to contribute to the field of [Your Field of Study]. I am
prepared to defend the content and methodology of this project during any evaluation or
examination.

Tendai Peter Zulu

(Author)

Signature: _______________________

Date………………………………

Mr. B. Mutale

(supervisor)

Signature………………………………….

Date………………………………………..
Dedication

This project is dedicated to the unwavering support and love of those who have been instrumental
in my journey:

To my family, for their unconditional encouragement and sacrifices that have made this endeavor
possible.

To my friends, who stood by me with patience and understanding during the challenging phases
of this project.

To my mentors, whose guidance and wisdom have shaped my academic and professional growth.

To the pursuit of knowledge, for its transformative power and the doors it opens to new
possibilities.

This project is a testament to the collective efforts and positive influences that have shaped my
path. I dedicate this work to each person and factor that has contributed to my personal and
academic development.

Tendai Peter Zulu

Acknowledgement

I would like to express my deepest gratitude to the Almighty God for His unwavering love, care,
and blessings that have kept me healthy and provided the strength to undertake and complete this
project. His divine guidance has been my source of inspiration throughout this journey.

I extend my sincere appreciation to my Web Development Lecturer, Mr. Sangwapo, whose

expertise and guidance have been instrumental in shaping my understanding of web development
concepts. His passion for teaching and commitment to student success have been truly inspiring.

I am also grateful to Mr. B. Mutale, my dedicated supervisor, for his valuable insights, constructive
feedback, and continuous support. His mentorship has played a pivotal role in refining the scope
and quality of this project.

A heartfelt thank you to my friends and family for their constant encouragement and understanding
during the challenging phases of this Endeavor. Your belief in my abilities has been a driving force
that kept me motivated.

I would like to acknowledge Evelyn Hone College for the privilege they granted me and the
exceptional knowledge imparted during my time here. The educational environment provided by
the institution has been invaluable in shaping my skills and capabilities.

Lastly, I express my gratitude to the management of Evelyn Hone College for creating an
environment conducive to learning and growth. Your commitment to fostering academic
excellence is evident, and I am grateful for the opportunities and resources provided.

May God continue to bless the management, lecturers, friends, and family who have played a
crucial role in my academic and personal development. This project is a culmination of collective
efforts, and I am sincerely thankful for the support and guidance that has shaped its successful
completion.
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 make their organization work effectively.

The customer can make their reservation online and do not need to wait in the queue for the
purchase of tickets. The customers have access to all kinds of information at the ease of sitting at
home e.g., bus schedules, reservation information, hotel information etc. The system also
addresses the problems faced by the customers prior to the implementation of the proposed system.

The administration has the right and access to information, making amends such as addition,
deletion, update etc. This system is beneficial for both, the customers and the administration. The
company facilitates their customers by providing online information as compared to the previous
system which operated manually.

A lot of sweat, time and hard work has been put into the completion of the project including
comprehensive online research, interviews, different questionnaires etc. The system is developed
brick by brick: planning, analysis, design and implementation with UML diagrams such as use
cases, sequence diagrams and entity relationship diagrams. The system flow is very easy to follow.

The programming languages used are PHP, Html, JavaScript, CSS and MySQL.
Table of Contents

Declaration…………………………………………………………………………..0.0

Dedication……………………………………………………………………………0.1

Abstract ........................................................................................................................1

Acknowledgment ..........................................................................................................2

1 System Planning .........................................................................................................3

1.1 Overview ................................................................................................................4

1.2 Problem Statements: ...............................................................................................5

1.3 Aims and Objectives: ...............................………………………………………... 6

1.3.1 Data Accuracy: ....................................................................................................7

1.3.3 Bus Schedule and Ticket Information: .................................................................8

1.3.4 Improve Efficiency: ..............................................................................................9

1.4 Project Scope: ...........................................................................................................10

1.5 Project Methodology: ................................................................................................11

1.5.1 Requirement Analysis: ..........................................................................................12

1.5.2 Design: ...................................................................................................................13

1.5.3 Implementation: .....................................................................................................14

1.5.4 Testing: ...................................................................................................................15

1.5.5 Maintenance: ..........................................................................................................16

2 System Analysis ................................................................................................................17

2.1 Introduction: .................................................................................................................18

2.2 Fact Finding: .................................................................................................................19

2.2.1 Research: ..................................................................................................................20

2.2.2 Interviews: ................................................................................................................21

2.2.3 Observation: ..............................................................................................................22

 2.3 Feasibility: ........................................................................................................................23

2.3.1 Technical Feasibility: ...................................................................................................24

2.3.2 Operational Feasibility: ................................................................................................25

2.3.3 Economic Feasibility: ..................................................................................................26

3 System Design ........................................ …………………………………………………..27

3.1 Introduction: .....................................................................................................................28

3.2 Use Case Diagram for Bus Module: .................................................................................29

3.2.1 Use Case Name: ADD BUS: ........................................................................................30

3.2.2 Use Case Name: VIEW BUS: ......................................................................................31

3.2.3 Use Case Name: DELETE BUS: ..................................................................................32

3.2.4 Use Case Name: UPDATE BUS: ..................................................................................33

3.4 Use Case Diagram of Admin: ..............................................................................................34

3.4.1 Use Case Name: VIEW BOOKING: ..............................................................................35

3.4.2 Use Case Name: VIEW USER MESSAGES: .................................................................36

3.5.1 Use Case Name: Get Register: ..........................................................................................37

3.5.2 Use Case Name: VIEW Bus Schedules: ..........................................................................38

3.5.4 Use Case Name: CONTACT US: ....................................................................................38

3.6 Use Case Diagrams for Registered User: ...........................................................................39

3.6.1 Use Case Name: Log In: ...............................................................................................40

3.6.3 Use Case Name: Contact Us: ........................................................................................41

3.6.4 Use Case Name: VIEW BUS SCHEDULES: ...............................................................42

3.7 USE CASE DIAGRAM FOR ADMIN: .............................................................................43

3.7.1 USE CASE NAME: VIEW USER: ...............................................................................44

3.7.2 USE CASE NAME: DELETE USER: ..........................................................................45

3.8 ENTITY RELATIONSHIP DIAGRAM: .............................................................................46

 Brief Description of ERD: ......................................................................................................29

4 Database Design: ....................................................................................................................30

Table Name: Admin: ................................................................................................................30

Table Name: Booking: .............................................................................................................30

Indexes: .....................................................................................................................................31

Table Name: Buses: .................................... …………………………………………………..31

Table Name: Contact: .................................. …………………………………………………..32

Table Name: User: ......................................................................................................................34

5 Sequence Diagrams for Proposed System: ...............................................................................35

5.1 Add New Bus: ......................................................................................................................35

5.2 Delete Bus: ...........................................................................................................................37

5.3UpdateBus: ...............................................................................................................................38

5.4 View Bus: ........................................……………………………………………………….39

5.8 Bus Schedule: .................................... …………………………………………………….46

5.9 Contact: …………………………………………………………………............................47

5.1 Software Testing: …………………………………………………………….......................49

Admin Login Page: ……………………………………………………………........................49

User’s Messages and Feedbacks: ………………………………………………………...........50

Add Bus: …………………………………………………………………................................51

View, Delete, Update Buses: ………………………………………………………….............53

View Booking: …………………………………………………………..................................54

6 Conclusion: ………………………………………………………………..............................55

References: ……………………………………………………………….................................55
 1 System Planning

1.0 Overview
The aim of this chapter is to describe the project scope, project objectives, problem statements,
project background and expected outputs of the system. The project is an online bus ticketing
system. Since the manual work of the system had many problems and was unable to provide
efficient facilities to the customers so the need of this computer system arose. The current system
enables the customers to find their required information regarding booking of tickets, sitting at the
ccomfort of their homes. The new system extends the customers the facility of making online bus
ticket booking without wasting a lot of time, standing in the queue at the bus terminals.

customers can also find relevant information by visiting the site, acquainting about various bus
routes places in different cities and bus fare.

1.1 Problem statements:

The existing system is totally dependent on manual paper work and a lot of manual work has to
be done. This manual work increases exponentially with the increase of buses in the company.
Such a huge amount of manual work needs quite a lot of staff members and extra attention from
the company maintenance department. The company was is unable to attract more customers since
there is no source to communicate effectively with them hence it is difficult raising awareness
relating new various packages and discounts. The customers also face many problems in the
existing system. The usual norm being, they must go to the bus terminal for the booking of the
ticket, unable to know the exact time of the bus. Sometimes the person has to wait for hours in
order to start his or her journey. This inconveniencing for customers and causes the company to
lose a lot of both money and customers hence a loss of money, causing the company to crumble
economically. To avoid such undesirable scenarios, the online bus ticket booking system is the
basic need of the company.

1.0.2 Aims and Objectives:

The main purpose of our online ticketing system is to provide the customers with ease of
booking/management with an alternative way. Our proposed system is very simple both for the
customers and admins. The system requires very low resources and works in all configurations.
Our proposed system has the following features:
1.0.3 Database Structure and Management:
The backbone of the system is a robust and well-structured database. The design and architecture
of this database play a pivotal role in ensuring data accuracy. A well-organized database schema,
with properly defined relationships and constraints, contributes to the reliability of the stored
information.

1.0.4 Data Validation Mechanisms:

Implementing effective data validation mechanisms is crucial to maintaining accuracy. This
involves setting up rules and checks at various entry points to ensure that only valid and properly
formatted data is accepted. This can include checks for data types, range validations, and
consistency checks.

1.0.5 Error Handling and Reporting:

The system should be equipped with robust error handling mechanisms. When errors occur,
whether during data entry or processing, the system should promptly identify and report these
issues. This allows for quick resolution and prevents the propagation of inaccurate data.

1.3.1 Quality Assurance and Testing:

Regular quality assurance and testing procedures should be in place to validate the accuracy of the
system. This includes both functional testing of system features and scenarios, as well as testing
specific to data accuracy, such as stress testing and boundary testing.

1.3.2 Increased income:

Online bus booking attracts more customers because this system can facilitate them in ways
the previous manual system was unable to. The customers can get any kind of information
relating to the company.

1.3.3 Bus schedule and ticket information:

The customers can see the seats and choose for the available ones. All the ticketing information
is also available to the customers and in case of any confusion, the customers can ask questions
along with the option of leaving comments. The customers can make a decision about the trip
while sitting at home. The customers can also remove any confusion without having any in-
person conversation, providing relief to the ladies.
1.3.4 Project Scope:
The online ticketing system is very easy to use both for the customers and the staff. Before
booking, the customers must register as members. Customers can check the availability of tickets
and the availability of different buses. The customers simply fill the form requesting the departure
city, arrival city, date of departure and bus time. Filling out this form on the system automatically
issues a ticket number to the customers which enables them to print the ticket. Customers also
have the ability to cancel the ticket in case of any problem. Ladies can also select the seat of their
own choice without any difficulty. Now the customers do not need to stand in the queue for a
long time, wasting their precious time. Unregistered users also have the facility to check the bus
schedules and other information regarding the company, but are unable to book the tickets.
Besides the customers, there is also another user of the system which is the administration.
The administration can upload different information relative to the company. Maintenance of
the system is the main purpose of the administration.

1.3.5 Project Methodology:

Our project uses waterfall model. The waterfall model is a sequential software development model
in which we can see the development slowly through a number of phases. The structure of waterfall
model is easy and comprehensive. Waterfall model has different phases. You cannot move to the
next phase until the preceding phase is completed. Waterfall model moves from top to bottom as
the name waterfall suggests.
Image Name: Methodology

Waterfall model and its different phases

Brief descriptions of various phases of waterfall model

1.3.6 Requirement Analysis:

All the possible requirements are gathered in this phase. The requirements are gathered from
the end users; those who would use the system. These requirements have been analysed. After
gathering these requirements, we move on to the next phase.

1.3.7 Design:
Before going to the literal coding, it is very important to know the requirements of the end users
and also to comprehend that how an end product should look like precisely. The software
requirements for the first phase are thoroughly studied here with the system design prepared.
The system design aids in overall system acritude. This phase works as an input for the next
phase.
1.3.8 Implementation:
After completing the design phase, actual coding starts in this phase. The coding of the system
has to be done, keeping in mind the design and requirements of the end users and the above two
phases.

1.3.9 Testing:
Once the code is completed, it is tested. Testing is done in order to check that implementation
matches the design and the requirements of the users. Testing is done on individual modules
and then on the whole system. In the testing phase, the outcome of the
system is checked.

1.3.10 Maintenance:
Once the project is passed through the testing phase, it is handled over to the user. Since the user
requirements change with the passage of time, so the project needs to be maintained keeping in
view the users need. Changes in requirements may need the whole process from the start to be
repeated. Hence maintenance of the project is highly encouraged.

1.4.1 System Analysis

System Overview:

The online bus booking system serves as a comprehensive platform facilitating the reservation of
bus tickets for passengers. The system connects users with various bus operators, offering a
seamless and efficient booking experience.

1.5.2 User Roles:

The system involves distinct user roles:
Customers: Users searching and booking bus tickets.
Bus Operators: Entities managing bus schedules, availability, and seat allocations.
Administrators: Oversee and manage the entire system, including user accounts and system
configurations.

1.5.3 Functional Requirements:

User Registration and Authentication: Customers and bus operators register and log in
securely.
Bus Search and Selection: Users can search for available buses based on criteria such as origin,
destination, date, and time.
Seat Reservation: Customers select preferred seats and reserve them.
Payment Integration: Secure payment gateway for online transactions.
Booking Confirmation: Automated confirmation of bookings via email or SMS.
Cancellation and Refund: Users can cancel bookings, and the system handles refunds as per
policies.
Bus Operator Management: Bus operators manage bus schedules, seat availability, and pricing.
Reporting and Analytics: Generate reports on bookings, revenue, and user statistics for
analysis.

1.5.4 Non-functional Requirements:

Performance: Ensure quick response times, even during peak booking periods.
Scalability: The system should scale to accommodate increased user and transaction loads.
Security: Implement robust encryption for user data and secure payment transactions.
User-Friendly Interface: Intuitive design for easy navigation and booking.
Reliability: Minimal downtime, with regular backups and recovery mechanisms.

1.5.5 Data Flow and Storage:

Data Flow: Users input travel details, search results are displayed, reservations are made, and
payments are processed.
Data Storage: Securely store user profiles, booking history, bus schedules, and transaction
records.

1.5.6 Integration:
Payment Gateway Integration: Connect the system with reputable payment gateways for secure
transactions.
SMS and Email Integration: Automated notifications for booking confirmations, updates, and
alerts.

1.5.7 Constraints:
Regulatory Compliance: Adherence to legal and regulatory requirements in the regions served.
Network Dependency: Users need reliable internet connectivity for accessing and using the
system.

1.5.8 Risks and Mitigation:

Security Risks: Implement robust security measures, including encryption and regular security
audits.
Transaction Failures: Provide clear error messages and prompt customer support to address
transaction failures promptly.

1.5.9 System Prototypes:

Develop prototypes for user interfaces and conduct usability testing to refine the design.

2.1 Introduction:
System analysis involves studying and analysing the ways of an organization currently processing
the data to produce information. Analysing the problem thoroughly forms the vital part of the
systematic study. In system analysis, prevailing problem is carefully examined by breaking them
into sub problems. Problem areas are identified and information is collected. Data gathering is
essential to any analysis of system. System analysis includes fact finding, development
environment, operating environment software, hard requirements and functional requirements.

2.2 Fact Finding:

It is the process of collecting information about system problems, opportunities, solutions
and priorities. Fact gathering is one of the most important phases of system analysis. Fact
gathering is done through different ways.

2.2.1 Research:
It is one of the best ways of fact gathering. I have thoroughly searched and studied many websites
of the online bus ticket reservation system to gather some useful information for my project so that
I can produce a system which meet the needs of the user and improve the company economy.

2.2.2 Interviews:
Interview is one of the techniques for information gathering during the system analysis phase
of a project. An interview gives some concrete information about the system because it is a
face-to-face conversation. I also conducted some interviews asking different questions from
different types of people. In this way, I got some valuable and beneficial information about my
system.
2.2.3 Observation
Since buying ticket manually is very common in Pakistan. During this phase I have observed
the tasks performed by different people to know which difficulties they commonly face.
Since we pass through the bus stand daily due to our transit, so it is very easy to evaluate and
observe their tasks. For me this was a relatively easy task with huge benefits to the proposed
system development.

2.3 Feasibility:
Feasibility study provides enough information to decide:
Whether the project is possible?
Whether it will benefit its intended users?
What are the alternative solutions to the projects and which are beneficial? Feasibility has
different types

2.3.1 Technical feasibility:

Technical feasibility deals with the solution of technical problems and the technical expertise
to design and build the problem solution. Since our system is an online ticketing system so we
need some expertise to handle the database and server of the system. This technical staff is
responsible for handling the problems and for their best solution. The admin should know how
to deal with the problems and promptly find a solution so that the customers are not confused,
assuring that there is no loss of the company. All the staff must be given some basic knowledge
about the system and its use. Admin is the person responsible for the whole system.

2.3.2 Operational feasibility:

It deals whether the system fulfills the user’s requirements and if the answer is in the
affirmative, then to what extent? Our system is very feasible, both for the company and users.
The current system is inefficient because the customers have to wait for a long time to get the
ticket only after they get to the bus terminal once. This is a redundant process and customers
dislike it because nowadays time is more precious, more than anything else.

The proposed system facilitates the staff. The company will arrange a few basic classes for the
staff to get them acquainted regarding the use of the proposed system. The proposed system
enables the customers to provide useful feedback which help improve the performance in the
future. Customers have the opportunity to find their desired service and give beneficial
suggestions. both for the customers and the company. In this way, the company know what to
do in the future and how to gain more profit by attracting more customers.

The purpose of this new bus ticketing system is to bring more benefits to the customers as well
as the staff during the business operation of the company. So during this phase, the customers and
staff opinions really matter because the new system is based on the user’s requirements to improve
performance and increase the services rendered for the customers.

2.3.3 Economic Feasibility:

Economic feasibility deals with some of the basic questions such as:

Is the project possible in the given cost constraints?

What is the minimum cost to attain the proposed system?

Since my system is not specific to any precise company and is a general-purpose project.
Therefore, I cannot arrange my economic feasibility but it will be cost minimizing, to say the
least.
3 System Design

3.1 Introduction
In this chapter, we discuss the design of the system which includes use cases, sequence diagram
entity relationship diagram.

3.2 Use case diagram for bus module:

3.2.1 Use Case Name: ADD BUS
Brief Description: This use case allows the administrator to add new buses for the
company. Actor: ADMIN
Preconditions: Admin must be logged in to the system.
Post Conditions: The database must be connected.
Success end condition: Bus Added Successfully.
Failure end condition: Database Not Connected, Please Fill out the Blank spaces. Main
flow:
Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “BUSES” button

4. Display ADD BUS button

5. Click “Add ” button

6. Display ADD BUS form

7. Enter Bus Details

8. Click “Add” button

9. Prompt “Bus Added successfully”

10. Save Record in Database

3.2.2 Use Case Name: VEW BUS

Brief Description: This use case allows the administrator to view the buses already working
for the company.
Actor: Admin
Preconditions: Admin must be logged in to the system.
Failure end condition: Database Not Connected. The database must be connected.
Main flow:

Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “BUSES” button

4. Display VIEW BUS button

5. Click “VIEW ” button

6. Display already added buses

3.2.3 USE CASE NAME: DELETE BUS

Brief Description: This use case allows the administrator to delete buses from the company,
s profile.
Actor: Admin
Preconditions: Admin must be logged in to the system. The database must be
connected. Post Conditions:
Success end condition: Bus Deleted
Failure end condition: Database Not Connected, Buses not available. Main
flow:
Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “BUSES” button

4. Display VIEW BUS button

5. Click “VIEW BUS” button

6. Display BUSES from the database

7. Click “DELETE” button

8. Prompt “Bus Deleted successfully”

9. Save changes in the Database

3.2.4 USE CASE NAME: UPDATE BUS

Brief Description: This use case allows the administrator to update the available buses in
the company.
Actor: ADMIN
Preconditions: Admin must be logged in to the system. The database must be connected,
buses must be available.
Post Conditions:
Success end condition: Bus Updated
Failure end condition: Database Not Connected, Buses not available. Main
flow:
Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “BUSES” button
4. Display VIEW BUS button

5. Click “VIEW BUS” button

6. Display BUSES from the database

7. Click “UPDATE” button

8. Prompt “Bus Updated successfully”

9. Save changes in the Database

Failure end condition: Database Not Connected, Please Fill out the Blank spaces. Main
flow:
3.4.1 USE CASE NAME: VIEW BOOKING:

Brief Description: This use case allows the administrator to view the booking done by
registered users.
Actor: ADMIN
Preconditions: Admin must be logged in to the system. The database must be connected,
Booking must be done by the users.
Post Conditions:
Failure end condition: Database Not Connected, No booking is available.
Main flow:

Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “BOOKING” button

4. Display bookings information

5. Click “SEND EMAIL” button

Display form containing

user’s information
7. Click “SEND” button
8. An email is sent to the user

3.4.2 USE CASE NAME: VIEW USER MESSAGES

Brief Description: This use case allows the administrator to view the messages and
feedback sent by the users.
Actor: ADMIN
3.5 Use Case Diagram for Unregistered User:
3.5.1 Use Case Name: Get Register
Brief Description: This use case allows the user to get registered for booking a ticket
Actor: Unregistered User
Preconditions: The database must be connected Post
Conditions:
Success end condition: You have successfully registered.
Failure end condition: Database Not Connected, Please Fill out the Blank spaces
Main flow:

Admin System

1. Visit the website

2. Display main navigation menu

3. Click “REGISTRATIN” button

4. Display Register button

5. Click “Register ” button

6. Display Registration form

7. The user enters his Details

Click “Register” button

Prompt “You have successfully registered”

10. Save Record in the Database

3.5.2 Use Case Name: VIEW Bus Schedules

Brief Description: This use case allows the user to view the schedules of different buses for
different cities.
Actor:UnregisteredUser
Preconditions: The database must be connected.
Post Conditions:
Success end condition:Display schedules for the desired cities.
Failure end condition: Database Not Connected, Please select departure and destination,
No service is available.
Main flow:

Admin System

1. Visit the website

2. Display main navigation menu

3. Click “SCHEDULE” button

4.Display Arrival and Departure drop down
menu
5. Select Arrival and Departure from the
drop down list
6. Click on the Search Button 6.
7. Display schedules of different buses in
the selected cites

Success End Condition: Your message has sent successfully.

Failure End Condition: Database not connected, Fill in the blank space.

MainFlow:
Admin System
1. Visit the website
2. Display main navigation menu
3. Click “CONTACT” button
4. Display contact form
5. Fill the contact form
6. Click on the SEND button
7. Prompt message has sent
Use Case Diagrams for Registered User:

3.6.1 Use Case Name: Log In

Brief Description: This use case allows the user to log in to the system to book a ticket
Actor: Registered User
Preconditions: The database must be connected; the user must be registered before log in.
Post Conditions:
Success end condition: You have successfully log in.
Failure end condition: Database Not Connected, Please register yourself before logging
in.
3.6.2 Use Case Name: book Ticket
Brief Description: This use case allows the user to reserve a ticket
Actor: Registered User
Preconditions: The database must be connected; the user must be logged in.
Post Conditions:
Success end condition: You have successfully reserved your ticket.
Failure end condition: Database Not Connected, Seat not available. Main
flow:
Admin System

1. Visit the website

2. Display main navigation menu

3. Click on “BOOK” button

4. Display a bus schedule for different cities

5. Click on Book button of your desired bus

6. Display drop down list of seats

7. The user selects his seat.

9. Click on Confirm Button

10. You reserved your ticket

3.6.3 Use Case Name: Contact Us

Brief Description: This use case allows the user to contact the admin of the company.
Actor: Registered User
Preconditions: The database must be connected Post
Conditions:
Success end condition: You have successfully sent your message.
Failure end condition: Database Not Connected, Please Fill out the Blank spaces. Main
flow:
Admin System

1. Visit the website

2. Display main navigation menu

3. Click “CONTACT” button

4. Display contact form

5. Fill the contact form

6. Click on the SEND button

7. Prompt message has sent

3.6.4 Use Case Name: VIEW BUS SCHEDULES

Brief Description: This use case allows the user to view the schedules of different buses for
different cities.
Actor: REGISTERED USER
Preconditions: The database must be connected.
Post Conditions:
Success end condition: Display schedules for the desired cities.
Failure end condition: Database Not Connected, please select departure and destination, No
service is available.
Main flow:
Admin System
1. Visit the website
2. Display main navigation menu
3. Click “SCHEDULE” button
4.Display Arrival and Departure drop down
menu
5. Select Departure and Arrival form drop
down menu
5. Click on the SEARCH button
Display schedule of different cities in the
selected cities
USE CASE DIAGRAM FOR ADMIN:

3.7.1 USE CASE NAME: VIEW USER

Brief Description: This use case allows the administrator to
view the users registered.
Actor:Admin
Preconditions: Admin must be logged in to the system.
The database must be connected, Users must be
registered. Post Conditions:
Failure end condition: Database Not Connected, No record
found.
Admin System

1. Log in to the system.

2. Display Admin Maintenance Menu

3. Click “USERS” button

4. Display registered users

5. View users

3.7.2USE CASE NAME: Delete User

Brief Description: This use case allows the administrator to
delete the registered users .
Actor:Admin
Preconditions: Admin must be logged in to the system.
The database must be connected, Users must be
registered.
Post Conditions:
Failure end condition: Database Not Connected, No
record found. Main flow:

Admin System

1. Log in to the system.

2. Display Admin Maintenance
Menu
3. Click “USERS” button
4. Display registered users
5. Click DELETE button
6. Delete a user from the database

7. Prompt “User deleted”

8. Save changes in the database
ENTITY RELATIONSHIP DIAGRAM:
Brief Description of ERD:
The above ERD shows that user can make many bookings. First user will get registered and then
he can make one or many bookings. The user can also contact the admin and gives feedback about
the company.
The admin can perform different tasks such as manage hotel’s information, update, delete, add,
edit etc. manage social networking websites such as Facebook, twitter, Google plus etc. Admin can
also add, delete and update buses schedules.

The relationship between user and booking is one to many, which means, a single user can book
many seats. Similarly, the relationship between user and admin is many to one, that is, many users
can contact with one admin. The relationship between admin and bus booking system is one to
many. The same way, one admin can manage several socials networking websites, that is
Facebook, twitter LinkedIn etc. which is one to many relationships.

Database Design:

Table Name: Admin

Column Type Null Default Comments MIME

ad_id int(11) No primary key

username varchar(40) No

password varchar(40) No
Table Name : Booking

Column Type Null Default Comments MIME

bok_id int(11) No primary key

usr_id int(11) No Foreign key

bus_id int(11) No Foreign key

fares int(255) No

seat_no int(11) No

Indexes

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE Yes No bok_id 11 A No

Table Name: Buses

Column Type Null Default Comments MIME

bus_id int(11) No primary

key

no_seats int(11) No

from1 varchar(255) No

to1 varchar(255) No

date date No

time varchar(44) No

fares int(255) No

Indexes:

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE Yes No bus_id 2 A No

Table Name: Contact

Column Type Null Default Comments MIME

cont_id int(11) No primary

key

name varchar(255) No

message varchar(255) No

email varchar(255) No

Indexes:

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE Yes No cont_id 2 A No

Table Name: select seats

Column Type Null Default Comments MIME

res_id int(11) No primary key

bus_id int(11) No Foreign key

usr_id int(11) No F

fares int(255) No

Indexes:

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE Yes No res_id 23 A No

Table Name: User:

Column Type Null Default Comments MIME

usr_id int(11) No primary key

name varchar(255) No

username char(255) No

password char(255) No

address varchar(255) No

contact varchar(244) No

email varchar(255) No

Indexes:

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE Yes No usr_id 1 A No

. Sequence Diagrams for Proposed System:

5.1 Add New Bus:

41

.2 Delete Bus:
42

3 Update Bus:
43

.4 View Bus:
44

.:
45
 46

.8 Bus Schedule:
47

9 Contact:
48

Software Testing:

Admin Login Page:

Brief Description:
By giving wrong password Admin is prompted that either your password or username is wrong

Brief Description:
Giving the right password admin is logged into the system.
49

Add Bus:

Brief Description:
By clicking on the Buses Button Drop down buttons are shown. On clicking the Add button, the
Add Bus form is displayed.
50

Brief Description:
Filling the form and giving the correct data in the form, bus is added to the database with the
success message. By leaving any field blank, a message is given “Please fill out the missing
field”.
51

View,Delete,Update Buse:

Brief Description:
By clicking the Buses button, a drop-down menu is shown. On clicking the View Button different
buses are shown in the table. Now you can delete or update these buses. Clicking the Edit button,
a form is displayed, in which you can edit the bus information. After editing the bus information
click the Update button at the bottom which result the form being updated. Similarly, you can also
delete the bus from the table by clicking on the Delete button.
View Booking:

Brief Description:
After booking/reservation of seats by user, admin can view the bookings by clicking on the
booking button.
52

Conclusion:

A lot of hard work, time and effort has been put into making the proposed system a reality. While
it may seem an easy task apparently, but it sure is not. Although the system is fully functional, but
there is still room for a lot of improvement, which would be done systematically and in times to
come, keeping in mind what the user demands and the restrictions at hand. In the near future, I
look forward to putting an online video chat system which would give ultimate ease to the
customers and an increase in the system contribution and generation of the company along with
cargo shipping and management. Furthermore, membership cards would be introduced with
magnetic chips that would enable people to pay through ATMs and POS terminals along with the
perks of extended discount schemes and membership benefits.

Not only this, but I am entirely open to suggestions and innovative ideas in making the proposed
system a better one since I firmly believe that perfection does not exist, especially if you ever stop
improvising. From fact finding to the coding, it has been a tedious task but nonetheless challenging
and I am content to deliver, promising the same in the future. In the end, let me conclude by making
it clear that none of this would have been possible without the grace of the Almighty Allah and my
ever-supporting supervisor, teachers and people who helped me overcome what seemed at the
horizon, thank you.
53

References:

Website Template:
1.http://www.infiniteskills.com/training/learning-bootstrap-3.html

Drawing Diagrams software used:

1.http://www.yworks.com/en/products/yfiles/yed/.
2.http://www.cadifra.com/download/.

Images Used:

1. https://www.google.com.pk/search?q=methodology&biw=1024&bih=667&source=lnms
&tbm=isch&sa=X&ei=w3lPVfC3EMmpuwTB9YHwCg&ved=0CAYQ_AUoAQ#imgdii
=FLWS
W4240xzZSM%3A%3BFLWSW4240xzZSM%3A%3BY52LWdJirHiX3M%3A&imgrc
=FLWSW
4240xzZSM%253A%3B4iIBHST7E8rVDM%3Bhttp%253A%252F%252Fwww.acendio
n.co
m%252Fimages%252Fdevelopment_methodology.jpg%3Bhttp%253A%252F%252Fww
w. acendion.com%252Fdevelopment_methodology.php%3B400%3B279.

Learning website:

1. http://www.w3schools.com/php/
2. http://getbootstrap.com/getting-started/.
3. http://www.tutorialrepublic.com/php-tutorial/.