BUS RESERVATION SYSTEM

MINOR PROJECT REPORT

By

SUGANTH P.V (RA2211027010249)

MAHESH. A (RA2211027010249)

SANTHOSH K.R (RA2211027010251)

Under the guidance of

Mrs. Sri Vidhya

In partial fulfilment for the Course

Of

21CSC205P – DATA BASE MANAGEMENT SYSTEMS

in Department of Data Science and Business Systems.

FACULTY OF ENGINEERING AND TECHNOLOGY

SCHOOL OF COMPUTING

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

KATTANKULATHUR

MAY 2023
 ABSTRACT

The proposed Database Management System (DBMS) for bus reservation stands as a crucial
tool for enhancing the efficiency and effectiveness of managing bus-related information.
With its relational database structure, the system ensures seamless integration and retrieval
of data, promoting consistency and accuracy in bus reservation records and reducing the
chances of errors.

The interconnected tables in the system offer a comprehensive overview of reservation

details, allowing for meaningful connections between passenger information, bus schedules,
and ticketing details. This holistic approach not only simplifies operational processes but
also encourages collaboration among stakeholders, enabling real-time sharing of data for
more informed decision-making in the realm of bus reservations.

In essence, the suggested DBMS serves as a powerful and essential resource, significantly
elevating the accessibility, utility, and security of bus reservation information. This, in turn,
contributes to a more streamlined and successful management of bus services.
 SCOPE

Effortlessly retrieve essential information related to bus reservations from any location,
ensuring prompt decision-making and responsiveness to passenger requirements.

Enhance the efficiency of bus operation tasks to boost productivity and minimize
operational costs, ultimately optimizing the overall effectiveness of managing bus services.

Implement systematic workflows in bus reservation processes to accelerate booking

procedures, diminish delays, and enhance outcomes, thereby conserving valuable
resources.

Digitize document management in the realm of bus reservations, eliminating the constraints
of physical paperwork. This promotes eco-friendly practices while significantly improving
organizational efficiency in handling reservation-related documents.
 OBJECTIVE

1. Bus Reservation Data Modelling and Design:

• Create a robust data model that effectively captures the relationships between various
entities within the bus reservation system, including passengers, routes, and bookings.

• Streamline the database schema to maximize efficiency in storing and retrieving critical
information associated with bus reservations.

2. Data Security and Access Control:

• Employ encryption protocols to secure and maintain the confidentiality of critical data,
ensuring compliance with security standards and safeguarding passenger details from
unauthorized access or breaches.

3. Scalability:

• Architect the database for scalability in the bus reservation system, enabling it to
effectively manage a growing number of bookings, passengers, and users.
• Enhance performance optimization strategies to accommodate an expanding volume of
data, ensuring that the system functions efficiently even as the number of reservations and
users increases, without experiencing substantial performance degradation.

4. Data Integrity and Validation:

• Uphold data integrity in the bus reservation system by employing constraints, triggers, and
validation rules.
• Institute checks within the system to guarantee that only valid and accurate data is input,
maintaining the reliability and correctness of information related to bus reservations.

5. Normalization:

• Implement normalization techniques in the bus reservation system to eradicate data

redundancy and enhance overall database efficiency.

6. Indexing and Query Optimization:

• Develop pertinent indexes within the bus reservation system to expedite data retrieval
operations.
• Streamline queries and enhance overall database performance to guarantee swift
response times for users, ensuring efficient and timely access to information related to bus
reservations.
 ER DIAGRAM EXPLANATION

ENTITY LIST:
 User
 Admin
 Reservation
 Payment
 Bus

ATTRIBUTE LIST:

1. User entity
 Username
 Age
 Date of Birth
 User id
 Mobile
 Email
 Gender
 Address

2. Reservation entity

 Reservation id
 Date
 Time
 No. of seats
 Type
 Seat No
 Bus Id
 Source
 Destination
 3. Admin Entity

 Admin Username
 Admin Password

4. Bus Entity

 Source
 Destination
 Bus Type
 Bus Id

5. Payment Entity

 Transaction id
 Payment status
 Payment mode
 Ticket Price
 TYPES OF ATTRIBUTES

1) Simple attribute:

1. User entity:

 Age
 Date of Birth
 User id
 Mobile
 Gender
 Address

2. Reservation entity

 Reservation id
 Date
 Time
 No. of seats
 Type
 Seat No
 Bus Id
 Source
 Destination

3. Admin Entity

 Admin Username
 Admin Password
4. Bus Entity

 Source
 Destination
 Bus Type
 Bus Id

5. Payment Entity:

 Transaction id
 Payment status
 Ticket Price

2) Multivalued attribute:

1. User entity :

 Email

3) Composite attribute:

1. User entity

 Username

2. Payment Entity

 Payment mode
 CARDINALITIES AND RELATIONSHIPS

1) One to One:

 Reservation – Payment: One reservation has one payment.

2) One to Many:

 User – Reservation: One user can process many reservations.

 Admin – Bus: One admin can manage many buses.

3) Many to One:
 Reservation – Bus:
 SCHEMA REPRESENTATION

User Table:
Attributes: user_id (Primary Key), first_name, last_name, dob, mobile, gender,
address

New User Table:

Attributes: user_id (Primary Key), email

Bus Table:
Attributes: bus_id (Primary Key), source, destination, type

Reservation_Has Table:
Attributes: r_id (Primary Key), r_date, time, type, seat_no, source, destination, bus_id
(Foreign Key referencing Bus)

Reservation_Process Table:
Attributes: r_id (Primary Key), date_reserve, type, time, seat_no, bus_id (Foreign Key
referencing Bus), source, destination, user_id (Foreign Key referencing User)

Reservation_Email Table:
Attributes: r_id (Primary Key), email