INTRODUCTION OF ONLINE BUS BOOKING SYSTEM:

Are you looking for Online bus booking system for your final year project? We are here to help you. You can contact us

Online Bus Booking System cloud based online software. This system would help customers to book a seat for their journey, book bus. This system would also help the owner to manage the coaches, employees, clients, services etc.

Bus Reservation System will increase the booking process faster, convenient, and comfortable. Customers can book their desired seats. They can check the availability of posts on a specific date. The customer can check availability, book ticket, or cancel ticket 24X7. The online system is available to use anytime.

User doesn’t require to visit any office. They just need internet and device to use our system. They can check route, price, class etc.

They can pay fare using a credit card, debit card, internet banking, online wallet like Paytm and cash too. Managing buses, employees, and salary would be very comfortable using this system.

This is a safe and secure way to expand the business. System decreases the human efforts and increases customer satisfaction.

MODULES OF ONLINE BUS BOOKING SYSTEM:

There are several modules required to complete this system. Here we are discussing the main modules or core modules of the system.

Admin Profile:

Admin is super user of our system. Admin can view all data in the system. Admin must log in to the system then there is authentication process. Admin view bus details verified the bus details, check the employee data.

Customer Profile:

The customer is the end user of our system. The customer can see bus details, check availability, book the ticket, make an enquiry, and make payment to confirm a seat. At any point of time before boarding of bus customer has all right to cancel tickets.

Employee Profile:

Employees are basically helping hands in bus reservation system. Employees have many profiles like managers, accountant, drivers, field employee etc. The manager would manage the business in such a way that everyone does their job. Manager manages proper work distributions.

Add Buses:

This module would help to add new bus details. Bus details include Bus Number, Model Number, Numbers of seats, Type of bus, the condition of the bus.

Availability:

This module would help to search the bus and find availability of seats. The customer can check bus availability anytime. Desired available seats can be booked by the client using this system.

Enquiry:

Any question can be made using email id or filling website form. Customer care representatives will reach you with solutions. Any question about bus timing, the system can do seat availability with human interaction.

Cancel:

At any point of time before boarding of bus customer has all right to cancel tickets. The money will be credited to a customer account as per bank policy and timing.

Booking:

If customer finds the desired bus and available seats. The customer can book the seats using this module. The booking process is entirely computerized. Real time seat availability. Once a place has been locked it can’t be available for booking.

Payment:

Payment can be made using a credit card, debit card, internet banking, online wallet like Paytm and cash too. Payment portal is highly secure and trusted.

Notification and messages:

This system has a fully automated process of information. Customer will get notifications of their booking, payments, inquiry response. The employee would get notifications about their jobs. Example driver will get the text for bus boarding.

Facilities:

Printouts:

Details of the case can be printed, and hard copy can be used to distribute.

PDF File:

Pdf can be utilized as soft copy.

Email:

Every information in the system can send via email.

Sorting:

Information can be sorted on the basis of many information.

Backup:

Backup is being taken every day.

Recovery:

Any failure then backup can be restored.

SYSTEM DESIGN OF ONLINE BUS BOOKING SYSTEM:

The system basically needs very simple architecture. This is system are there primary three users i.e. Admin(Advocate), Client, Employee.

Use cases for Admin of online bus booking system:

system design of admin of online bus booking system

Admin is a most famous person of this scheme. Admin is superuser of this Bus Reservation System. Admin needs to log in to system using appropriate credentials. Once admin has logged in the system, admin can do following things.

Once an admin has logged in the system, admin can do following things.
Now, the admin has complete access into the system. Admin can add buses, edit, update Bus details. Admin can manage the employee details, their salary, work assignment. Admin has the power to view all booking, see payment made to the system. Admin also administers the client details. Admin has only right to verify the customer profiles.

Admin can add buses, edit, update Bus details. Admin can manage the employee details, their salary, work assignment. Admin has the power to view all booking, see payment made to the system.

Admin also administers the client details. Admin has only right to verify the customer profiles.

Use cases for Employee of online bus booking system:

system design of employee of online bus booking system

Employees are man power in offices. An employee can register to the system. Admin would get a notification.When admin would verify the employee identity only then the employee would able to access the system.

After successful registration, the employee needs to log in and authentication process does occur. Employee arranges Bus departure.An employee can receive payment from customer in cash or via debit cards/credit cards and confirm their seats.

They can update the Bus information like departure date, time, route etc. They can contact to the client and provide the bus status as well as solve the query related to the customer. They can contact to them using phone or email.

Use cases for Clients of online bus booking system:

system design of client of online bus booking system

The client is the end user of the system. Before doing anything, the user needs to register with the system. Admin would verify the customer details. Once the customer is verified. Clients can log in to the system.

Clients can search the availability of seats using check availability modules. If customer finds the seats available for them. They can book the ticket, make payment, and confirm their booking.

Sometimes due to some personal reason client wants of canceling the card. They can cancel the ticket. The client is the end user of the system. Before doing anything, the user needs to register with the system.

Admin would verify the client details. Once the client is verified. Clients can log in to the system. Clients can search the availability of seats using check availability modules. If customer finds the seats available for them.

They can book the ticket, make payment, and confirm their booking. Sometimes due to some personal reason client wants of cancel the ticket. They can cancel the ticket.

USER INTERFACE (UI) OF ONLINE BUS BOOKING SYSTEM:

The user interface is very important part of the system. A good and user-friendly interface attracts the user toward it. Whereas a bad one makes the user experience bad and they never return to the system. As we have shown several use cases in this system

We have developed these interfaces to interact with the system.

Login Page:

Admin, client, and employee need to log in using login id and password. The system authenticates every user. The only valid user can access the data.

Admin Page:

This page is dedicated to a senior employee of the organisation. This page contains the link to add buses link to employees, link to client’s details. This page also shows to highlighted bookings, ongoing buses, newly added Buses.

Client Page:

This page shows the client details. Clients can access recommended buses as per their last searched in this system. Clients can view the case update using this interface. This page would help the customer to check the availability.

Reservation page:

This page is used for making the online bus booking system reservation. The customer would have redirected to this page after checking the availability. They need to fill the personal details. After filling the details, payment gateway page would come up. Once payment is done. They would get confirmation on email as well as on screen.

Employee Page:

This interface helps the employee to view their work, notification, manage buses update Buses, etc.

ER-DIAGRAM OF ONLINE BUS BOOKING SYSTEM

ERD of online bus booking system

 

There are mainly Seven Entities Admin, Manager, Employee, client, Bus, Payment, book. These Seven entities would manage the whole system. There are mainly Seven Entities Admin, Manager, Employee, client, Bus, Payment, book. These Seven entities would manage the whole system.

Admin:

Admin is a super user of the system. Admin has all right to view and modify the data in the system. Admin has followings attributes.

AdminID:

This is numeric 14 digits number which is unique to every admin. AdminID is the primary key to admin table in the database.

Name:

This attribute would hold the name of Admin. The name is varchar type variable which holds the data length up to 250 characters.

Email:

This is an essential attribute of the table. Every Admin must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

Contact: 

This is multi valued attributes which mean every owner can have more the one mobile number in database. Address: This attribute would hold the address of Admin. Each employee must provide the address.

Manager:

The manager is a secondary user of the system. The manager can view Bus details, manage employee, booking, solve client’s problem. The manager has followings attributes.

ManagerID:

This is numeric 14 digits number which is unique to every Manager. ManagerID is the primary key to Manager table in the database.

Name:

This attribute would hold the name of the manager. The name is varchar type variable which holds the data length up to 50 characters.

Email:

This is an essential attribute of the table. Every Manager must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

Contact: 

This is multi valued attributes which mean every manager can have more the one mobile number in database.

Address:

This attribute would hold the address of admin. Each employee must provide the address. Admin address is verified via Human resource team.

Employee: 

The employee is another user of the system. An employee can view Bus details, confirm the online booking of seat availability for clients. The employee has followings attributes.

EmpID:

This is numeric 14 digits number which is unique to every Employee. EmpID is the primary key to Employee table in the database.

Name:

This attribute would hold the name of Employee. The name is varchar type variable which holds the data length up to 50 characters.

Email:

This is an essential attribute of the table. Every employee must have a working email id to keep in contact with staff. This field has validation only email formatted values will be stored.

Contact:

This is multi valued attributes which mean every employee can have more the one mobile number in database.

Address:

This quality would hold the address of the employee. Each employee must provide the address.

Client: 

The client is the primary end user of our system most of the business is done through them. Clients would book the desired seats. The client would provide the feedback. The client has following attributes.

ClientID:

This is numeric 14 digits number which is unique to every Client. ClientID is the primary key to client table in the database.

Name:

This attribute would hold the name of customers. The name is varchar type variable which holds the data length up to 50 characters.

Email.:

This is an essential attribute of the table. Every client must have a working email id. This field has validation only email formatted values will be stored

Address:

This attribute would hold the address of clients. Address of clients would help us to connect with them and visit the location. This would provide better services.

Bus:

Every Bus registered with the system has the information in this entity. Buses are the main concern of system.

BusID:

This is numeric 14 digits number which is unique to every Bus. BusID is the primary key to case table in the database. Each Bus is uniquely identified using this id.

Bus Number:

This attribute holds the bus number of the bus. The bus number is the number given by Government to every vehicle on the road.

No of seats:

Every bus has many seats. To make it easy for the customer and check availability no. of seats should be in the database.

Type:

This attribute would hold the type of bus. The bus can be AC, non-AC, Nonstop AC, Nonstop non-AC etc.• Book: Before going to book any seat. The client should check the availability. If the desired seat is available. They can book it.

Book:

Before going to book any seat. The client should check the availability. If the desired seat is available. They can book it.

BookID:

This is numeric 14 digits number which is unique to every Booking. BookID is the primary key to case table in the database. Each Payment is uniquely identified using this id.

Seat no:

Concerning Bus, booking must have a seat no.

Journey Date:

This would hold the date of Journey.

Bus Number:

For further reference to the customer. The bus number is added to every booking.

Payment:

Payment Entity store the data about pay. Every payment data is here. Any conflict can be resolved by looking to this.

PaymentID:

This is numeric 14 digits number which is unique to every Payment. PaymentID is the primary key to payment table in the database. Each Payment is uniquely identified using this id.

BookingID:

This is a reference to a booking. This would help the admin to find this payment is against booking.

Date:

This would hold the time of the transaction.

Transaction No.:

The transaction number is reference no given by the bank.

Status:

Status of every transaction either it would be pending or confirm is being updated in this field.

DESIGN DATA DICTIONARY FOR ER-DIAGRAM OF ONLINE BUS BOOKING SYSTEM:

The data dictionary is useful in case of development.

Table Name: AdminMaster

Primary Key: AdminID

Description: To store the details of admin

Serial No. Fields Datatype Description
1. AdminID Integer Primary key
2. Name varchar
3. EmailID varchar
4. Contact. Integer Multiple contacts can exist for single admin
 

5.

Address varchar

 

Table Name: ManagerMaster

Primary Key: ManagerID

Description: To store the details of General Manager

Serial No. Fields Datatype Description
1. ManagerID Integer Primary key
2. Name Varchar
3. Email Varchar
4. Contact. Integer Multiple contacts can exist for single admin
5. Address varchar

 

Table Name: EmployeeMaster

Primary Key: EmpID

Description: To store the details of Employee Details

Serial No. Fields Datatype Description
1. EmpID Integer Primary key
2. Name varchar
3. Email varchar
4. Contact. Integer Multiple contacts can exist for single admin
5. Address varchar

 

Table Name: ClientMaster

Primary Key: ClientID

Description: To store the details of Clients

Serial No. Fields Datatype Description
1. ClientID Integer Primary key
2. Name varchar
3. Email varchar Multiple contacts can exist for single client
4. Address varchar

 

Table Name: BusMaster

Primary Key: BusID

Description: To store the details of Property

Serial No. Fields Datatype Description
1. BusID Integer Primary key
2. BusNumber Varchar
3. No. of seats Integer
4. Type Varchar

 

Table Name: BookMaster

Primary Key: BookID

Description: To store the details of Payment

Serial No. Fields Datatype Description
1. BookID Integer Primary key
2. SeatNo. Integer
3. Journey Date date
4. Bus Number varchar

 

Table Name: PaymentMaster

Primary Key: PaymentID

Description: To store the details of Payment

Serial No. Fields Datatype Description
1. PaymentID Integer Primary key
2. BookID Integer Foreign key to BookMaster
3. Date date
4. Transaction No. varchar
5. Status varchar

BUS TICKET RESERVATION SYSTEM:

CONCLUSION OF ONLINE BUS BOOKING SYSTEM:

Finally, in Online Bus Booking System, we have developed a secure, user-friendly Bus Reservation System.This Project basically provides a Bus information and regarding bus information.First of all, in our website any user or visitors view our system and search the bus and how many seats are available in our buses.

The user can also register its own seats in the bus this website.The user can post a comment on different Bus Services.But user can compulsory registered first in the system.Search Bus category wise. This system has automated process to alert employee as well as customers who have booked their seats with the system.

This is the cloud based online system. Therefore, to access this system you only need a web browser, internet connection. This is the 24X7 available system.  We observed the working of the Bus reservation system and after going through it, we get to know that there are many operations, which they have to do manually.

It takes a lot of time and causing many errors while data entry. Due to this, sometimes a lot of problems occur and they were facing many disputes with customers. To solve the above problem, and further maintaining records of passenger details, seat availability, price per seat, bill generation and other things, we are developed computerized reservation system.

By using this software, we can reserve tickets, through telephone lines, via the internet. The customer can check the availability of bus and reserve selective seats. The project provides and reviews all sorts of constraints so that user does give only user data and thus validation is done in an efficient manner.