Course End Project Report
Submitted in the Partial Fulfillments of the Requirements
for the Course
Relational Database Management System(A7610)
Submitted By
G Santosh 23885A0204
K Praveen 23885A0207
S Srinivas 23885A0222
Under the Esteemed Guidance of
Mr. Mohammad Bilal J Assistant
Professor
DEPARTMENT OF INFORMATION TECHNOLOGY
VARDHAMAN COLLEGE OF ENGINEERING
(AUTONOMOUS)
(Affiliated to JNTUH, Approved by AICTE and Accredited by NBA)
Shamshabad, Hyderabad-501218
NOV
2023 -2024
Table of Contents
SNO Chapter Name Page No
1. ABSTRACT 1
2. INTRODUCTION 2-3
3. SOURCE CODE 4-9
4. SAMPLE OUTPUT 10-11
5. SCHEMA REFINEMENT 12
6. OUTCOMES 13-14
REQUIREMENT ANALYSIS
1. MY SQL DATA BASE
2. XAMPP CONTROL PANEL
3. Vs Code
• HTML Javascript
• PHP Language
4. COMMAND PROMPT
1. ABSTRACT
The "Bus Booking Management System" is a database-driven project developed to
streamline the process of bus ticket booking and management. The system leverages
DBMS/SQL technologies to efficiently handle essential operations such as user
registration, bus schedule management, seat availability tracking, and ticket booking.
This project aims to provide a comprehensive solution for managing bus transportation data
while ensuring accuracy, reliability, and ease of access. The database is designed to store
and retrieve data related to buses, routes, passengers, and ticket reservations.
Key functionalities include:
• Dynamic seat allocation to prevent double bookings.
• Automated fare calculation based on travel distance.
• Real-time updates on bus schedules and availability.
• User-friendly SQL queries for data retrieval and management.
By implementing normalized tables and structured queries, the system minimizes data
redundancy and enhances performance. This project serves as an efficient, scalable, and
secure platform for managing bus ticket booking operations, demonstrating the practical
application of database management principles in real-world scenarios.
1. INTRODUCTION
The Bus Booking Management System is a database management project developed to
simplify and automate the process of managing bus ticket bookings. The project is designed
to cater to the needs of administrators and passengers by providing an efficient, reliable,
and user-friendly interface for handling tasks such as bus schedule management, seat
availability tracking, and ticket reservations.
This system uses a structured MySQL database to store and manage data for various
entities involved in the booking process, including buses, schedules, locations, users, and
booked tickets. The database ensures data integrity and supports real-time updates for
seamless operations.
Key objectives of the project include:
• Enhancing the efficiency of bus ticket booking operations.
• Providing secure and centralized data management.
• Offering a user-friendly platform for managing and retrieving relevant information.
The system incorporates multiple database tables, each designed to store specific
information, such as:
• Booked Table: To record ticket booking details.
• Bus Table: To store details of buses, including their name and operational status.
• Location Table: To manage terminal locations and their corresponding cities and
states.
• Schedule List Table: To maintain schedules for bus routes, departure times, and
seat availability.
• Users Table: To manage user credentials and roles.
This report presents a detailed overview of the system's design, implementation, and
functionality. It highlights how SQL queries are used to interact with the database and
ensure efficient data management. The project demonstrates the practical application of
Database Management Systems (DBMS) concepts in real-world scenarios, showcasing
its importance in modern transportation services.
ER DIAGRAM
3. SOURCE CODE
-- Database: `bus_booking`
--
-- --------------------------------------------------------
--
-- Table structure for table `booked`
--
CREATE TABLE `booked` (
`id` int(30) NOT NULL,
`schedule_id` int(30) NOT NULL,
`ref_no` text NOT NULL,
`name` varchar(250) NOT NULL,
`qty` int(11) NOT NULL,
`status` tinyint(1) DEFAULT 0 COMMENT '1=Paid, 0- Unpaid',
`date_updated` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `booked`
--
INSERT INTO `booked` (`id`, `schedule_id`, `ref_no`, `name`, `qty`, `status`, `date_updated`)
VALUES
(1, 1, '202009091727', 'John Smith', 1, 1, '2020-09-09 10:29:44'),
(2, 1, '202009091626', 'Sample', 2, 0, '2020-09-09 09:34:28'),
(3, 1, '202009099953', 'asdasd asdasd', 27, 0, '2020-09-09 09:53:09');
-- --------------------------------------------------------
--
-- Table structure for table `bus`
--
CREATE TABLE `bus` (
`id` int(30) NOT NULL,
`name` varchar(250) NOT NULL,
`bus_number` varchar(50) NOT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1 COMMENT '0 = inactive, 1 = active',
`date_updated` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `bus`
--
INSERT INTO `bus` (`id`, `name`, `bus_number`, `status`, `date_updated`) VALUES
(3, 'Economy', '5001', 1, '2020-09-08 13:54:42');
-- --------------------------------------------------------
--
-- Table structure for table `location`
--
CREATE TABLE `location` (
`id` int(30) NOT NULL,
`terminal_name` text NOT NULL,
`city` varchar(250) NOT NULL,
`state` varchar(250) NOT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1 COMMENT '0= inactive , 1= active',
`date_updated` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `location`
--
INSERT INTO `location` (`id`, `terminal_name`, `city`, `state`, `status`, `date_updated`)
VALUES
(1, 'Sample Terminal Name', 'Sample City', 'Sample', 1, '2020-09-08 14:23:36'),
(2, 'South Sample Terminal', 'South City', 'Sample', 1, '2020-09-08 14:33:04');
-- --------------------------------------------------------
--
-- Table structure for table `schedule_list`
--
CREATE TABLE `schedule_list` (
`id` int(30) NOT NULL,
`bus_id` int(30) NOT NULL,
`from_location` int(30) NOT NULL,
`to_location` int(30) NOT NULL,
`departure_time` datetime NOT NULL,
`eta` datetime NOT NULL,
`status` tinyint(4) NOT NULL DEFAULT 1,
`availability` int(11) NOT NULL,
`price` text NOT NULL,
`date_updated` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `schedule_list`
--
INSERT INTO `schedule_list` (`id`, `bus_id`, `from_location`, `to_location`, `departure_time`,
`eta`, `status`, `availability`, `price`, `date_updated`) VALUES
(1, 3, 1, 1, '2020-09-11 16:00:00', '2020-09-12 02:00:00', 1, 30, '250', '2020-09-08 07:49:57'),
(2, 3, 2, 1, '2020-09-12 02:45:00', '2020-09-12 05:00:00', 1, 30, '250', '2020-09-08 07:37:52');
-- --------------------------------------------------------
-- Table structure for table `users`
--
CREATE TABLE `users` (
`id` int(30) NOT NULL,
`name` varchar(150) NOT NULL,
`user_type` tinyint(1) NOT NULL DEFAULT 1 COMMENT '1 = admin, 2= faculty , 3 =
student',
`username` varchar(25) NOT NULL,
`password` varchar(25) NOT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1 COMMENT ' 0 = incative , 1 = active',
`date_updated` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `users`
--
INSERT INTO `users` (`id`, `name`, `user_type`, `username`, `password`, `status`,
`date_updated`) VALUES
(1, 'Administrator', 1, 'admin', 'admin123', 1, '2020-09-08 16:42:28'),
(2, 'John Smith', 1, 'jsmth', 'admin123', 1, '2020-09-08 16:13:53');
--
-- Indexes for dumped tables
--
--
-- Indexes for table `booked`
--
ALTER TABLE `booked`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `bus`
--
ALTER TABLE `bus`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `location`
--
ALTER TABLE `location`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `schedule_list`
--
ALTER TABLE `schedule_list`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `booked`
--
ALTER TABLE `booked`
MODIFY `id` int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
--
-- AUTO_INCREMENT for table `bus`
--
ALTER TABLE `bus`
MODIFY `id` int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
--
-- AUTO_INCREMENT for table `location`
--
ALTER TABLE `location`
MODIFY `id` int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `schedule_list`
--
ALTER TABLE `schedule_list`
MODIFY `id` int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `users`
--
ALTER TABLE `users`
MODIFY `id` int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
COMMIT;
4. SAMPLE OUTPUT
SCHEMA REFINEMENT
5. OUTCOMES
The Bus Booking Management System project achieves
several outcomes, demonstrating the effective application of
database management concepts and practical problem-solving
skills. Below are the key outcomes:
1. Streamlined Ticket Booking Process
The project simplifies and automates the process of
booking bus tickets by maintaining real-time updates on
schedules, seat availability, and payments.
2. Efficient Data Management
o Centralized storage of data for buses, locations,
schedules, and users.
o Reduction in data redundancy through normalization
techniques.
3. Real-Time Updates
The system dynamically updates critical information such
as:
o Changes in bus schedules.
o Seat availability after each booking.
o Payment statuses for tickets.
4. Enhanced User Experience
By providing a reliable and user-friendly system,
administrators and passengers can easily manage bookings
and retrieve required information with minimal effort.
5. Secure Data Storage
o User information, such as login credentials and
booking details, is securely stored.
o Role-based access ensures that sensitive operations are
restricted to authorized personnel.
6. Cost and Time Efficiency
The system significantly reduces manual effort, improving
operational efficiency and saving time for both passengers
and administrators.
7. Scalability and Extendibility
o The database structure supports scalability to
accommodate additional buses, routes, and users.
o It can be extended with additional features like online
payment integration and advanced analytics.
8. Practical Application of DBMS Concepts
The project demonstrates the implementation of core
DBMS principles, such as:
o Designing normalized database tables.
o Writing optimized SQL queries for CRUD (Create,
Read, Update, Delete) operations.
o Using indexes and keys for efficient data retrieval.
9. Improved Decision-Making for Administrators
With comprehensive data about bus operations, seat usage,
and revenue, administrators can make data-driven decisions
to optimize resources and schedules.
This project provides a robust framework for managing bus
transportation data and serves as a foundation for developing
more advanced transportation management systems.
