Data Base Management System
II BCA I Semester (2023-24)
Department of Information Technology,
Vignan's Foundation for Science, Technology & Research (Deemed to be University),
Guntur, Andhra Pradesh, India
221FJ01071- Suraj Kumar Singh
Title : Ride-Sharing System or Carpooling Platform
1. Question :-
Objective : The objective of this case study is
to design a real-time ride-sharing system. The
system will connect passengers with drivers in
real-time, allowing them to request and
provide rides efficiently. The real-time ride-
sharing system aims to provide a platform
where passengers can request rides and drivers
can offer their services. The system will match
passengers with available drivers based on
their location, preferences, and availability.
Requirements:
1. The system should support multiple users,
including passengers and drivers.
2. Passengers should be able to create
accounts, log in, and manage their personal
information.
3. Passengers can request a ride by specifying
their pick-up location, destination, and
preferred ride type (e.g., economy, premium,
etc.).
4. Drivers can create accounts, log in, and
manage their personal information, including
their vehicle details.
5. Drivers should be able to update their
availability status (e.g., available,
unavailable).
6. The system should have real-time tracking
functionality to track the location of drivers
and
display it to passengers during the ride.
7. The system should calculate and display the
estimated fare for each ride, based on factors
such as distance, ride type, and any additional
charges.
8. Passengers should be able to rate drivers
after completing a ride, and drivers should be
able to rate passengers as well.
9. The system should maintain a history of
past rides for both passengers and drivers.
10. The system should have an admin panel to
manage user accounts, handle complaints, and
monitor system performance.
Tasks:
a) Identify Entity sets and design an E-R
schema for this application.
b) Specify key attributes of each entity type,
attribute type and structural constraints on
each relationship type.
c) Based on the Designed E-R Diagram,
design corresponding Schema Diagram
d) Discuss any assumptions you made and
justify your E-R design choices.
e) Create the tables & implement Primary
keys, Foreign keys for the above scenario.
f) Insert related data into the above created
tables accordingly.
2. Abstract:
This case study outlines the creation of a real-
time ride-sharing system, aiming to seamlessly
connect passengers and drivers for efficient
transportation. The system facilitates user
registration, ride requests, driver availability
updates, fare estimation, real-time tracking,
and user ratings. An admin panel ensures
effective management. The design employs an
Entity-Relationship schema, identifying
entities, attributes, and relationships, UserID (Primary Key)
culminating in a Schema Diagram.
Username
Assumptions align with industry practices.
Implementation includes table creation, Password
primary and foreign keys, and data insertion.
This system innovatively addresses First Name
contemporary transportation needs.. Last Name
3. Introduction: Email
The proliferation of urbanization has brought Phone
forth transportation challenges like traffic
congestion and environmental degradation. In Role (Passenger/Driver)
response, ride-sharing systems have emerged  Passenger :
as a promising solution. This case study delves
into the design of a real-time ride-sharing PassengerID (Primary Key, Foreign Key
system, aiming to connect passengers with referencing User)
drivers efficiently. The system's core UserID
objectives encompass user registration, ride
requests, real-time tracking, fare calculation, Address
and user feedback. Employing Entity-  Driver :
Relationship modeling, the study outlines the
system's architecture, including key entities, DriverID (Primary Key, Foreign Key
attributes, and relationships. By doing so, the referencing User)
study contributes to the discourse on
Vehicle Type
innovative transportation solutions, catering to
the demands of modern urban living. Vehicle Plate Number
Availability Status
(Available/Unavailable)
4. SOLUTION :-
 Ride :
a) Entity-Relationship (E-R) Schema RideID (Primary Key)
Design:
 Entities :- PassengerID (Foreign Key referencing
Passenger)
User (Generalization of Passenger and
Driver) DriverID (Foreign Key referencing Driver)

Passenger Pickup Location

Driver Destination

Ride Ride Type (e.g., economy, premium)

RideType Ride Status

(Requested/Ongoing/Completed)
Rating
Fare Amount
b) Specify key attributes of each entity
type, attribute type  Rating :
RatingID (Primary Key)
RatedUserID (Foreign Key referencing
User, either Passenger or Driver)
 Attributes:
 User :
 RatedByUserID (Foreign Key referencing
User, either Passenger or Driver)
Rating Value (Numeric value representing
the rating)
c) Relationship :-
Relationships:
User-Passenger (One-to-One)
One User can be associated with one
Passenger.
 User-Driver (One-to-One)
One User can be associated with one Driver.
 Driver-Vehicle (One-to-One)
One Driver can have one Vehicle.
 Driver-Ride (One-to-Many)
One Driver can be associated with multiple
Rides, but each Ride is associated with one
Driver.
 Passenger-Ride (One-to-Many)
One Passenger can be associated with multiple
Rides, but each Ride is associated with one
Passenger.
 Ride-RideType (Many-to-One)
Many Rides can have the same RideType, but
each Ride is associated with one RideType.
 User-Rating (One-to-Many)
One User can give multiple Ratings, and one
User can receive multiple Ratings.
d) Assumptions and Justifications:
I assume that each ride can have only one
passenger and one driver.
A user can be both a passenger and a
driver, which is why I used a
generalization for the User entity.
RideType entity is used to categorize
different types of rides (e.g., economy,
premium) with varying fare structures.
The Rating entity allows both passengers
and drivers to rate each other after a
completed ride.
e) Table Creation and Primary/ Foreign
Keys:
 User :-
CREATE TABLE Users (
UserID INT PRIMARY KEY,
Username VARCHAR(55),
Password VARCHAR(55),
FirstName VARCHAR(55),
LastName VARCHAR(55),
Email VARCHAR(55) UNIQUE,
Phone VARCHAR(20),
Role ENUM('Passenger', 'Driver')
);
INSERT INTO Users (UserID,Username,
Password, FirstName, LastName, Email,
Phone, Role)
VALUES
(1,'user1', 'ABC1', 'Suraj', 'Singh',
'Suraj@gmail.com', '1234567890',
'Passenger'),
(2,'user2', 'ABC2', 'Raja', 'Kumar',
'Raja@gmail.com', '9876543210', 'Driver'),
(3,'user3', 'ABC3', 'Ankit', 'Kumar',
'Ankit@gmail.com', '5551234567',
'Passenger'),
(4,'user4', 'ABC4', 'Rahul', 'Kumar',
'Rahul@gmail.com', '5559876543',
'Driver'),
(5,'user5', 'ABC5', 'Eva', 'Kumar',
'Eva@gmail.com', '7771112222',
'Passenger'),
(6,'user6', 'ABC6', 'David', 'Kumar',
'David@gmail.com', '3334445555',
'Driver'),
(7,'user7', 'ABC7', 'Neeraj', 'Kumar',
'Neeraj@gmail.com', '8889990000',
'Passenger'),
(8,'user8', 'ABC8', 'Dhiraj', 'Kumar',
'Dhiraj@gmail.com', '2223334444',
'Driver'),
(9,'user9', 'ABC9', 'Om', 'Kumar',
'Om@gmail.com', '1112223333',
'Passenger'),
(10,'user10', 'ABC10', 'Ashif','Kumar',
'Ashif@gmail.com', '6667778888',
'Driver');
OUTPUT :-
 Passenger :-
CREATE TABLE Passenger (
PassengerID INT PRIMARY KEY,
UserID INT UNIQUE,
Address VARCHAR(200),
FOREIGN KEY (UserID) REFERENCES
User(UserID)
);
INSERT INTO Passenger (PassengerID,
UserID, Address)
VALUES
('P1', 1, 'Parmanadpur'),
('P2', 2, 'Murthan'),
('P3', 3, 'Harpunand'),
('P4', 4, 'Vadlamudi'),
('P5', 5, 'Patna'),
('P6', 6, 'Chapra'),
('P7', 7, 'Sonpur'),
('P8', 8, 'Hajipur'),
('P9', 9, 'Guntur'),
('P10', 10, 'Naya Gaon');
select *from Passenger
OUTPUT :-
 Driver :-
CREATE TABLE Driver (
DriverID INT PRIMARY KEY,
UserID INT UNIQUE,
VehicleInfo VARCHAR(100),
AvailabilityStatus BOOLEAN,
FOREIGN KEY (UserID) REFERENCES
User(UserID)
);
INSERT INTO Driver (DriverID,
UserID, VehicleInfo, AvailabilityStatus)
VALUES
('D1', 1, 'Maruti', TRUE),
('D2', 2, 'Honda ', TRUE),
('D3', 3, 'Ford ', FALSE),
('D4', 4, 'Maruti AC', TRUE),
('D5', 5, 'Altima', FALSE),
('D6', 6, 'Hyundai', TRUE),
('D7', 7, 'Kia Optima', FALSE),
('D8', 8, 'Volkswagen Passat', TRUE),
('D9', 9, 'BMW', TRUE),
('D10', 10, 'RR', FALSE);
(14, 'Senior Citizen', 9.00),
(15, 'Student', 8.50);
select *from RideType
OUTPUT :-

select *from Driver;

OUTPUT :-

 RideType
CREATE TABLE RideType (
RideTypeID INT PRIMARY KEY,
TypeName VARCHAR(50) NOT NULL,
BaseFare DECIMAL(10, 2) NOT NULL
);
INSERT INTO RideType (RideTypeID,
TypeName, BaseFare)
VALUES
(6, 'Express', 15),
(7, 'Standard', 12.00),
(8, 'Deluxe', 35.00),
(9, 'Airport Shuttle', 18.00),
(10, 'Business', 40.00),
(11, 'Family', 22.00),
(12, 'Electric', 27.00),
(13, 'Sports Car', 50.00),
 Ride :-
CREATE TABLE Ride (
RideID INT PRIMARY KEY,
PassengerID INT,
DriverID INT,
PickupLocation VARCHAR(200) NOT
NULL,
Destination VARCHAR(200) NOT
NULL,
RideTypeID INT,
EstimatedFare DECIMAL(10, 2),
Status VARCHAR(20) NOT NULL,
FOREIGN KEY (PassengerID)
REFERENCES Passenger(PassengerID),
FOREIGN KEY (DriverID)
REFERENCES Driver(DriverID),
FOREIGN KEY (RideTypeID)
REFERENCES RideType(RideTypeID)
);
INSERT INTO Ride (RideID, Comment TEXT,
PassengerID, DriverID, PickupLocation,
FOREIGN KEY (RideID) REFERENCES
Destination, RideTypeID, EstimatedFare,
Ride(RideID),
Status)
FOREIGN KEY (RatedUserID)
VALUES
REFERENCES User(UserID)
(1, 'P1', 'D1', 'Parmanandpur', 'Digha',
);
'RI1', 25, 'Completed'),
INSERT INTO Rating (RatingID,
(2, 'P2', 'D2', 'Murthan', 'Apshaid','RI2', 30,
RideID, RatedUserID, Stars, Comment)
'Completed'),
VALUES
(3, 'P3', 'D3','Sonpur', 'Muzafferpur', 'RI3',
20, 'In Progress'), ('RT1', 1, 1, 5, 'Great ride!'),
(4, 'P4', 'D4','Vadlamudi', 'Sitamadhi', ('RT2', 2, 2, 4, 'Good experience.'),
'RI4', 35, 'Completed'),
('RT3', 3, 3, 3, 'Average ride.'),
(5, 'P5', 'D5', 'Naya Gaon', 'Madhubani',
'RI5', 15, 'Completed'), ('RT4', 4, 4, 5, 'Excellent driver.'),

(6, 'P6', 'D6', 'Patna', 'Purnia', 'RI6', 28,
'Completed'),
(7, 'P7', 'D7', 'Chapra', 'Parmanandpur',
'RI7', 22, 'In Progress'),
(8, 'P8', 'D8', 'Gandhi Chawk', 'Hajipur',
'RI8', 32, 'Completed'),
('RT5', 5, 5, 2, 'Not satisfied.'),
('RT6', 6, 6, 4, 'Friendly driver.'),
('RT7', 7, 7, 5, 'Smooth ride.'),
('RT8', 8, 8, 1, 'Terrible experience.'),
('RT9', 9, 9, 3, 'Okay ride.'),

(9, 'P9', 'D9', 'Sitabganj', 'Nijam chawk', ('RT10', 10, 10, 4, 'Good Ride');
'RI9', 18, 'Completed'),
(10, 'P10', 'D10', 'Purnia', 'Hajipur', 'RI10', SELECT *FROM Rating;
37, 'Completed');
select *FROM Ride;

OUTPUT :-

OUTPUT :-

 Rating :-
CREATE TABLE Rating (
RatingID INT PRIMARY KEY,
RideID INT UNIQUE,
RatedUserID INT,
Stars INT,
5. SCHEMA DIAGRAM :-
7. REFERENCES
1. JavaTpoint
https://www.javatpoint.com/dbms-sql -
command
2. LucidChart
https://www.lucidchart.com/pages/er-
diagrams::text=A

6. CONCLUSION
This case study outlines the design and
development of a real-time ride-sharing
system, aiming to revolutionize the way
passengers and drivers connect for efficient
transportation. By seamlessly connecting
passengers with available drivers, the system
streamlines the process of requesting and
providing rides. Key objectives include user
registration, ride request handling, real-time
driver availability updates, fare estimation,
real-time tracking, and user rating feedback.
The system is designed to accommodate
various user roles, including passengers and
drivers, with functionalities tailored to their
specific needs. Passengers can create accounts,
request rides by specifying pickup and
destination details, and choose preferred ride
types. On the other hand, drivers can register,
manage their vehicle information, update their
availability status, and offer rides to
passengers. The system’s real-time tracking
feature ensurestransparency and safety by
allowing passengers to monitor their ride’s
progress. The estimated fare calculation takes
into account factors such as distance, ride
type, and additional charges, providing
passengers with an accurate expectation of
costs.