GUJARAT TECHNOLOGICAL UNIVERSITY

Chandkheda,
Ahmedabad Affiliated

SAL INSTITUTE OF TECHNOLOGY &

ENGINEERING RESEARCH
A Report on

(Bus Reservation system)

Under subject of
DESIGN ENGINEERING – 2A (3150001)
B. E. III, Semester – V
COMPUTER ENGINEERING DEPARTMENT

Submitted by:
Group:

Sr. Name of student Enrolment No.

1. Zala kaival 210670107105
2. Patel zeel 210670107094
3. Manvar Tilak 210670107082
4. Jagani Sarthak 210670107078
5. Kanani Ridham 210670107072
6. Renish Vekariya 210670107114

Komal Thummar Prof. Neha Minocha

(Faculty Guide) (Head of the Department)

Academic year(2023-2024)
 ACKNOWLEDGEMENT

When we reach the compliment of the project giving credit becomes a must, as without the
support of the other so many people’s help and guidance this project could not be completed
successfully.

We would like to thank Asst. Prof. Komal Thummar for guiding us and showing their views
on the project for framing the realistic picture of the requirement and involved needed in this
project. They were always there with their great ideas and suggestions whenever we needed.
They took a great deal of interest in our work and encouraged us to outperform ourselves.
They believed in us and were a pillar of strength for us.

We would like to thank to help us prepare this project. We would also appreciate their
guidance and technical knowledge they gave us regarding this project.

Last but not least, our heartfelt appreciation goes to all those not named here, but who have
rendered their co-operation, little or more, directly or indirectly in the course of development
of this Decolourisation of Dye waste water by adsorption on Alumina Adsorbent.

Thanking All.

Yours Truly:

Zala kaival(210670107105)
Patel zeel(210670107094)
Manvar Tilak(210670107082)
Jagani Sarthak(210670107078)
Kanani Ridham(210670107072)
Renish Vekariya(210670107114)
 ABSTARCT

Online Bus Ticket Reservation System is a Web based application that works within a centralized
network. This project presents a review on the software program "Online Bus Ticket Reservation
System" as should be used in a bus transportation system, a facility which is used to reserve seats,
cancellation of reservation and different types of route enquiries used on securing quick
reservations.

OBTRS is built for managing and computerizing the traditional database, ticket booking and
tracking bus and travel made. It maintains all customer details, bus details, reservation details. In
order to achieve the design, I mo Transport Company (ITC) was chosen as a case study because of
its strategic importance to I mo State. Structured Systems Analysis and Design Methodology
(SSADM) was adopted. In addition, PHP Hypertext Preprocessor (PHP) language was used for the
front-end of the software while the back end was designed using MySQL.

The software achieved is capable of improving the customer hand and relationship management in
ITC operations. It is recommended that despite the present functionality of the designed software,
an additional functionality such as the use of E-mail to send tickets and notifications to the
customer and an online payment using credit cards/debit cards should be implemented into the
system.
Furthermore, other operations carried by ITC such as the courier services should also be integrated
in order to enhance the system.

I
 Table of Content

Completion Certificate
Abstract I
List of Figures II
List of Tables III
Symbols And Abbreviations IV

Chapter 1 Introduction
1.1 About Domain/Area 1
1.2 About the Definition 1
1.3 Users 1
1.4 Modules and Functionalities 2

Chapter 2 Literature Review

2.1 Observation on Domain 3
2.2 Literature review related to your definition 3
2.3 Problem Summary 4

Chapter 3 Design Consideration to detail design Part

3.1 Functional Requirement 5
3.2 Non- Functional Requirement 6
3.3 Design For Cost/Environment 8
3.4 Tools & Technology 8
3.5 LNM 9

Chapter 4 Design
4.1 Use Case Diagram 10
4.2 Sequence Diagram 11
4.3 Activity Diagram 12
4.4 Data Flow Diagram 13
4.5 E R Diagram 14
4.6 Class Diagram 15
4.7 Data Dictionary 16

Chapter 5 Simulation & analysis

5.1 Software Process Model 17
5.2 Homepage Design of Project Definition 18

Chapter 6 Conclusion & Future Work

6.1 Conclusion 19
6.2 Future Work 19

References 37

II
 LIST OF FIGURES

Fig. Name Pg No.

1 LNM 10
2 Use Case Diagram 11
3 Activity Diagram 13
4 Data Flow Diagram 14
5 Software Process Model 19
6 Homepage Design of Project Definition 20
7 Observation Through AEIOU Framework 23
8 Interaction 25
9 Empathy Making Canvas 26
10 Ideation Canvas 30
11 Product Development Canvas 33
12 Mind Mapping Canvas 36
13 Prototype 39

II
 LIST OF TABLES

Table Table Name Pg No.

1 admin 19
2 customer 19
3 Route detail 19
4 ticket 20
5 rent 20
6 payment 20
7 Book detail 21
8 Password update 21
9 Contact us 21
10 Time-table 22
11 Bus detail 22

I
 SYMBOLS AND ABBREVIATIONS

Name Notation Description

System The scope of a system can be represented by a system

boundary boundary. The use cases of the system are placed inside
the system boundary, while the actors who interact with
the system are put outside the system. The use cases in
the system make up the total requirements of the
system.

Use Cas A use case represents a user goal that can be achieved
by accessing the system or software application.

Actor Actors are the entities that interact with a system.

Although in most cases, actors are used to represent the
users of system, actors can actually be anything that
needs to exchange information with the system. So an
actor may be people, computer hardware, other systems,
etc. Note that actor represent a role that a user can play,
but not a specific user.
Association Actor and use case can be associated to indicate that the
actor participates in that use case. Therefore, an
association corresponds to a sequence of actions
between the actor and use case in achieving the use
case.
Generalization A generalization relationship is used to represent
inheritance relationship between model elements of
same type.

Include An include relationship specifies how the behaviour for

the inclusion use case is inserted into the behaviour
defined for the base use case.

Extends An extend relationship specifies how the behaviour of

the extension use case can be inserted into the
behaviour

1
 defined for the base use case.

Constraint Show condition exists between actors an activity.

Interface is used to connect package and use-case. Head

Interface
is linked with package and tail linked with use-case.
Anchor is used to connect a note the use case in use case
Anchor
diagram.

2
 CHAPTER : 1

INTRODUCTION

1.1 ABOUT DOMAIN :-

Domain Name :- Bus Reservation system

Purpose:- The purpose of the provide customers with a personalized easy-to-utilize user experience for
booking and purchasing tickets online

1.2 ABOUT THE DEFINATION:-

A bus reservation system is a mobile or web software solution designed to provide customers with
personalized easy-to-utilize user experience for booking and purchasing tickets online. It stores
customers' personal data records, scheduled routes, frequent trips, drop points, and other information.

1.3 USERS :-

 Passenger
Bus
 repairing
Travel
 agency
 Advertisement group

1.4 MODULES AND FUNCTIONALITIES

Modules:

1 .Customer profile
2. Add Buses
3. Inquiry
4. Booking
5. Payment

6. Facilities

3
1.5 Functionalities:

1. High automation of bus ticket booking

2. 24/7 availability for customers
3. Instant and contact-free payments
4. Self-service capability
5. Real-time passenger information

4
 CHAPTER : 2

LITERATURE SURVEY

2.1 Observation on Domain:

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 a ticket, or cancel a ticket 24X7. The online system is available to
use anytime. The user doesn’t require to visit any office.

2.2 Literature review related to your definition:

A literature review for a bus reservation system project involves exploring existing research, academic
articles, and publications related to similar systems, technology, user experience, and relevant theories.
Here's an example of how you might structure your literature review section for a bus reservation
system project:

1) Historical Development of Reservation Systems : Discuss the evolution of reservation systems,

starting from manual methods to computer-based systems. Highlight key milestones and
technological advancements that have shaped modern reservation systems.

2) Technological Aspects: Explore literature on the technologies commonly used in bus reservation
systems, such as database management systems, web development frameworks, and mobile
applications. Discuss the advantages and limitations of different technologies in the context of
reservation systems.

3) User Experience and Interface Design: Examine research articles on user experience (UX) design
principles and interface design specifically related to reservation systems. Discuss how intuitive
interfaces, user feedback mechanisms, and accessibility considerations contribute to a positive user
experience.

4) Challenges and Solutions in Reservation Systems: Review studies that identify challenges faced
by bus reservation systems, such as security concerns, data management issues, and scalability
problems. Analyze proposed solutions and best practices suggested in the literature.

5) Integration of Mobile Applications: Explore literature related to the integration of mobile

applications in reservation systems. Discuss how mobile apps enhance user convenience, increase
accessibility, and improve overall system efficiency.

6) Data Security and Privacy: Examine scholarly articles addressing data security and privacy
concerns in reservation systems. Discuss encryption techniques, authentication methods, and legal
regulations (such as GDPR)related to user data protection.

5
 2.3 Problem Summary:

Issues commonly associated with bus reservation system systems include:

1. Ticket Booking and Reservation:

 - Passengers need a convenient and user-friendly platform to book bus tickets.
 - The system should support one-way and round-trip ticket reservations.
 - It must allow passengers to select their preferred bus routes, departure times, and seat preferences.

2. Seat Availability Management:

 - The system needs to keep track of available seats on each bus for different routes and dates.
 - Passengers should be able to view real-time seat availability and choose their preferred seats.

3. Payment Processing:
 - The system should offer secure payment processing options, including credit/debit card
payments, mobile wallets, and cash transactions.
 - Passengers should receive electronic tickets or booking confirmations upon successful payment.

4. Admin Management:
 - Administrators require access to an admin panel for managing routes, buses, and schedules.
 - They should be able to add new buses, update schedules, and view booking details.

5. Cancellation and Refunds:

 - Passengers may need to cancel their bookings, and the system should support cancellation requests.
 - Refund policies and processes must be defined and implemented.

6. Reporting and Analytics:

 - The system should provide insights and reports for bus operators to analyze booking trends,
revenue, and passenger demographics.

6
7. Mobile Accessibility:
 - The system should be accessible through mobile applications, allowing passengers to book tickets
on the go.

8. Customer Support:
 - Passengers may need assistance or support, so the system should provide a mechanism for
contacting customer service.

9. Security:
 - Security measures should be in place to protect sensitive passenger information, payment data, and
the integrity of the system.

7
 CHAPTER 3:

DESIGN CONSIDERATION TO DETAIL DESIGN PART

I. FUNCTIONAL REQUIREMENT :-

Functional requirements for a biometric facial check-in system typically include specific features and
capabilities that the system must possess in order to effectively perform its intended functions. Here
are some common functional requirements for such a system:

1) Registration:-There are two kinds of users Existing members would log in andnew ones will sign
up.
 INPUT :- The existing user must input the following.
 Login name/Email Id / Mobile
Number
 Password

2) search for bus :- User have to give the journey route,time &category.
3) seat selection:- User can select the available sets.

4) payment Gateway:- User get into the payment page. Here User have to pay the fare to reserve
the selected seat.

8
II. Non- Functional Requirement:

1) Correctness Requirement:-

All the different requirements specified in the document have been correctly implemented. It covers
all the requirements that are expected from the Online Matrimonial Portal.

2) Efficiency Requirement:-
The software is highly efficient and various tasks in its various modules simultaneously. Even if the
system fails,the system will be recovered back up within an hour or less.

3) Maintainability Requirement:-
A commercial database is used for maintaining the database and the application server takes care of the
site. In case of failure, a re-initialization of the program will be done. Also,the software design is being
done with modularity in mind so that its maintainability can be done efficiently.

4) Re usability Requirement:-

The system should be available at all times, meaning the user can access it using a web browser, only
restricted by the downtime of the server on which the system runs. In case of a hardware failure or
database corruption, backups of the database should be retrieved from the server and saved by the
administrator. Then the service will be restarted. It means 24 X 7 availability.

9
III. Design For Cost/Environment :-
Designing a biometric facial check-in system with a focus on cost-effectiveness and environmental
considerations involves integrating efficient components and implementing sustainable practices. Here
are some design considerations to achieve cost and environmental efficiency.

1) Energy-Efficient Hardware Selection :

- Choose energy-efficient cameras and hardware components that consume minimal power during
operation. - optfor devices with power-saving modes to reduce energy consumption during idle periods.

2) Cloud-Based Architecture: -

Implement a cloud-based architecture to reduce the need for on-site hardware infrastructure, leading to
lower hardware and maintenance costs. - Utilize cloud-based storage for biometric data, reducing the
energy consumptionand maintenance costs associated with physical servers.

3) use of open-source software:

Utilize open-source facial recognition software to minimize licensing costs and enable flexibility forsystem
customization and upgrades.
- Leverage open-source community support for troubleshooting and updates, reducing the need for
costly technical support

10
4) Uprimized Data Managemaent:-

Implement efficient data management practices to reduce storage costs and optimize data retrieval
processes.- Utilize data compression techniques to minimize storage requirements and improve
overall system performance.

5) Tools & Technology:-

 Hardware Requirement:
 A device (Computer/ laptop/ android/ IOS) with atleast 2 GB RAM

 Hard disk space required - 250 MB

 Minimum snapdragon 600 series/ i3 8th gen/ applea11 bionic.3.1.2.

 Software Requirement:

 A database like DBMS (MySQL) to store the details

 A web browser like Chrome, Mozilla, Firefox, etc.
 Operating System - At least Windows 7 64-bit, Mac10.11, android OREO (8) and IOS 11

 FORNTEND

 HTML
 CSS

 BACKEND

 SQL
 DBMS
 JAVASCRIPT
 PHP

11
3.2Security LNM :-

12
 CHAPATER 4 : DESIGN

4.1 Use case diagram:

13
4.2 Sequence Diagram :

14
4.3 Activity Diagram :

15
4.4 Data Flow Diagram :

Level 0:

Level 1:

16
4.5 ER Diagram :

17
4.6 Class Diagram :

18
4.7 Data Dictionary :

19
20
21
22
 CHAPTER 5 : SIMULATION & ANALYSIS

5.1 Software Process Model :

23
5.2 Homepage Design of Project Definition :

24
25
26
 CHAPTER 6 : CONCLUSION & FUTURE WORK

6.1 Conclusion :

In conclusion, a bus reservation system is a crucial component of modern transportation services,

streamlining the process of booking bus tickets for travelers. It simplifies the steps from searching for
available buses to confirming bookings and ticket generation. This system enhances the customer
experience and provides efficient management of bus seat inventory for bus operators. Additionally,
it can offer features like seat selection, passenger details entry, and secure payment processing.
Overall, a well- designed bus reservation system benefits both customers and bus companies by
making the booking process more convenient and organized

6.2 Future Work :

To solve these problems they required a computerized system to handle all the works. They required a
web based application that will provide a working environment that will be flexible and will provide
ease of work and will reduce the time for report generation and other paper works.The main purpose
behind the proposed system is to provide a comprehensive computerized system,which can capture,
collate and analyze the data from these wards and evaluate the impact of the program.We can also
provide SMS based alert and email notifications for bookings.

The Wallet can be developed to handle discounts on the point’s basis. It can also be used to provide
referral codeoncept for referring friends.Chat features can be included in the application to chat with
customer care. We can come with a feature that will allow the customer to save favorite routes and
provide discounts for same.Introduce coupon management for providing which customers can use to
avail discounts

27
  Observation through AEIOUFramework

Activities:

 User registration

 Ticket booking

 Seat availability

 Waiting

28
Environment:

 Crowd

 noisy

 Cloudy

User:

 Passenger

 Bus repairing

 Travel agency

 Advertisement group

Interactions:

 Passenger to passenger

 Passenger to bus Conductor

 Driver to conductor

Object:

 Buses

 Platforms

 Display boards

 Ticket window

 Toilet

29
 Empathy Making Canvas:

30
 Empathy Making Canvas:

User:
 Search and booking

 Seal selection

 Booking conformation

 cancellation

 Refunds

Stakeholders:
 passenger

 Bus operator

 Developer

Activities:

 User registration

 Bus selection

 Seat selection

 Booking

Story Boarding:

Happy boarding happy:

I really used the bus reservation system for my trip.and I couldn’t be happier with the experience are some
of the highlights that made my journey smooth and enjoyable.

31
Happy :

User friendly interface : the website and mobile app are incredibly user friendly.finding and booking a
bus was a breeze. The layout is intuitive and Iappreciate the clean design.

Secure payment : the payment process was seamless and secure. I appreciate the various payment
options available,including credit cards andmobile wallets.

Sad :

1) User interface(UI) :

 Cluttered layout and difficult navigation

 Confusing or design elements

2) booking experience :

 Complicated booking process

 Errors during ticket booking and payment

 Limited payment optio

32
Sad :
1) Customer service :
 Slow response from customer support

 Unhelpful or unresponsive customer service representation

2) Mobile responsiveness :
 Poor performance on mobile devices including slow loading andlayout

33
 Ideation Canvas:

34
People:

 Customer

 Bus driver

 Stakeholder

 Developer

 Admin

 Designer

Activities:

 Future and functionality

 Value proposition

 Information architecture

 Monetization strategy

 Problem definition

 User personas

Situation/Context/Location:

 Features

 User needs

 Target audience

 Revenue model

35
Props/Possible Solutions:

 Feedback

 Security and privacy

 Marketing

 Promotion

 Competitive

36
 Product Development Canvas:

37
Purpose:

 Visibility on web

 Safety

 Security

 24*7 service

 Tracking

Product Experience:

 User friendly

 Time saving

 Customer support

 responsive

Product Functions:

 Seat selection

 Passenger information

 Reservation

 Bus schedule information

38
Product Features:

Some of the features of the web-site are:

 Live tracking

 Accessibility

 Multiple language support

 Search and filter

Components:

Components Used in this web-site are:

 User interface

 HTML

 CSS

 Database management system

 Vs code

 Java script

 DJANGO

39
 People:

People included in this area are:

 passengers

 Ticket checker

 Bus driver

 Admin

 tester

Customer re validation :

 Data privacy

 Identification document

 Login requirement

Reject, Redesign, Retain :

 Ticket modification and cancellation

 Review personal information

40
 Learning Needs Matrix :

41
 1) Middle-Top-right quadrant identified the learning requirement regarding applicable
standards, design specification, exploration and understanding of scientific principles and
identification of different types of experiment to be performed over a period of time.
 World Wide Web
2) Middle-Top-left quadrant suggests making identification of learning the use of various
tools, processes, methods of application, the ories to apply tools involved.

 Programming Languages3)
3) Middle lower-left quadrant contains identified needs for learning of software, simulation
techniques, skills, mathematical learning requirements and so on
4)
 Local Hosts
 Text Editors4)
5) Middle lower-right quadrant shall have the needs identified pertaining ton understanding
of various alternative materials, its strength and other properties, standards, as well as its testing
requirements, depending upon envisaged quality.

 Electronic Devices5)
6) Top-left quadrant suggest that which programming languages are we using

 HTML
 CSS
 BOOTSTRAP
 SQL
 DJANGO
 PYTHO

42
7) Top-left quadrant suggest that which programming languagesare we using

 CSS
 BOOTSTRAP
 SQL
 DJANGO
 PYTHON

8) Top-Right quadrant suggest that which standard versionare we using

 PYTHON

 DJANGO

43
 MIND MAPPPING Canvas:

44
 The context of this web-site is to provide :-

 Bus listings
 Seat selection
 User registration
 Booking conformation
 Mobile friendly
 Search functionality

45
Prototype:

46
Reference :

1. Redbus:- https://www.redbus.in/
2. Abhibus:- https://www.abhibus.com/
3. GSRTC:- https://gsrtc.in/site/

47