Darshan University

A Project Report on

“Taxi Management System”

Under the subject
Software Engineering (2301CS405)

B. Tech, Semester – IV

Computer Science & Engineering Department

Submitted By
Student Name: Nadiyapara Jatin Shailesh Enrollment No.:23010101172
Academic Year
(2024-2025)
Internal Guide Dean-DIET
Prof. R. B. Gondaliya Dr. Gopi Sanghani
Darshan University Darshan University
 SRS – “Taxi Management System”

Computer Science & Engineering

Department
Darshan University

DECLARATION

We hereby declare that the SRS, submitted along with the Software
Engineering (2301CS405) for entitled “Taxi Management System” submitted
in partial fulfilment for the Semester-5 of Bachelor Technology (B. Tech) in
Computer Science and Engineering (CSE) Department to Darshan University,
Rajkot, is a record of the work carried out at Darshan University, Rajkot under
the supervision of R. B. Gondaliya and that no part of any of report has been
directly copied from any students’ reports, without providing due reference.

Jatin Nadiyapara

Student’s Signature

Date: __________

23010101172 Jatin Nadiyapara i

 SRS – “Taxi Management System”

Computer Science & Engineering

Department
Darshan University

CERTIFICATE

This is to certify that the SRS on “Taxi Management System” has been
satisfactorily prepared by Nadiyapara Jatin S. ( 23010101172) under my
guidance in the fulfillment of the course Software Engineering (2301CS405)
work during the academic year 2024-2025.

Internal Guide Dean-DIET

Prof. R. B. Gondaliya Dr. Gopi Sanghani
Darshan University Darshan University

23010101172 Jatin Nadiyapara ii

 SRS – “Taxi Management System”

ACKNOWLEDGEMENT
I wish to express my sincere gratitude to my project guide Prof. R. B. Gondaliya and all
the faculty members for helping me through my project by giving me the necessary
suggestions and advices along with their valuable co-ordination in completing this work.

I also thank my parents, friends and all the members of the family for their precious
support and encouragement which they had provided in completion of my work. In
addition to that, I would also like to mention the Darshan University personals who gave
me the permission to use and experience the valuable resources required for the project
from the University premises.

Thus, in conclusion to the above said, I once again thank the faculties and members of
Darshan University for their valuable support in completion of the project.

Thanking You
Jatin Nadiyapara

23010101172 Jatin Nadiyapara iii

 SRS – “Taxi Management System”

ABSTRACT
The Taxi Management System (TMS) is designed to simplify and improve taxi services
using a computerized system. This system makes it easy for passengers to book rides,
view ride details, and track their taxi in real-time. Passengers can also manage their
accounts and see their ride history.

For drivers, TMS provides tools to manage their work, accept or reject ride requests, and
see their earnings. The system helps dispatch taxis efficiently, reducing waiting time and
finding the best routes.

Administrators have a special panel to manage everything, including user accounts and
system performance. They can also generate reports on ride details, driver
performance, and earnings.

The main goal of TMS is to make the process of booking and managing taxi rides easier
for everyone, reducing the need for manual work and improving overall efficiency.

23010101172 Jatin Nadiyapara iv

 SRS – “Taxi Management System”

Table of Contents
List of Figures.......................................................................................................................................................I
List of Tables .......................................................................................................................................................II
1 Introduction................................................................................................................................................1
1.1 Product perspective ...........................................................................................................................1
1.2 Product features .................................................................................................................................1
1.2.1 There are four different users who will be using this product: ...................................................1
1.2.2 The features that are required for the Admin are: ......................................................................1
1.2.3 The features that are required for the Manager are: ...................................................................1
1.2.4 The features that are required for the Driver are: .......................................................................1
1.2.5 The features that are required for the Customer are: ..................................................................2
1.3 Functional Requirement .....................................................................................................................2
1.3.1 Admin .........................................................................................................................................2
1.3.2 Manager .....................................................................................................................................2
1.4 Non-Functional Requirement .............................................................................................................3
1.4.1 Usability: .....................................................................................................................................3
1.4.2 Accuracy: ....................................................................................................................................3
1.4.3 Availability: .................................................................................................................................3
1.4.4 Maintainability: ..........................................................................................................................3
1.4.5 Response Time: ..........................................................................................................................3
1.4.6 Data Protection: .........................................................................................................................3
2 Design and Implementation Constraints....................................................................................................4
2.1 Use case diagram................................................................................................................................4
2.2 Activity diagram and Swimlane diagram ............................................................................................6

23010101172 Jatin Nadiyapara v

 SRS – “Taxi Management System”

List of Figures
Figure 2.1-1 Use case diagram for Taxi management System ...........................................................................4

Figure 2.1-2 Use case diagram for Taxi management System ...........................................................................5

Figure 2.2-1 Activity diagram for taxi booking .................................................................................................. 6

Figure 2.2-2 Activity diagram for profile edit.....................................................................................................7

Figure 2.2-3 Swimlane diagram for taxi booking .............................................................................................. 8

Figure 2.2-4 Swimlane diagram for profile edit................................................................................................. 9

23010101172 Jatin Nadiyapara Page |I

 SRS – “Taxi Management System”

List of Tables
Table 3.1-1 Screen element of Registration form ............................................... Error! Bookmark not defined.
Table 3.2-1 Screen element of Login form .......................................................... Error! Bookmark not defined.
Table 3.3-1 Screen element of Add borrower book ............................................ Error! Bookmark not defined.
Table 4.1-1 Table: Book ....................................................................................... Error! Bookmark not defined.
Table 4.1-2 Table: Borrower ................................................................................ Error! Bookmark not defined.
Table 4.1-3 Table: Staff........................................................................................ Error! Bookmark not defined.
Table 4.1-4 Table: Student .................................................................................. Error! Bookmark not defined.

23010101172 Jatin Nadiyapara P a g e | II

 SRS – “Taxi Management System”

1 Introduction
1.1 Product perspective

This project updates traditional taxi services into an internet-based system, making it easier for both drivers
and passengers to use. It allows passengers to book taxis, track their rides, and manage their accounts online.
For drivers, it provides tools to manage their schedules, accept ride requests, and track their earnings.

1.2 Product features

1.2.1 There are four different users who will be using this product:
• Admin
• Manager
• Driver
• Customer

1.2.2 The features that are required for the Admin are:
• User Management: Add, edit, and delete users; assign roles (admin, manager, driver, customer).
• System Configuration: Set up system preferences including pricing, service areas, and vehicle options.
• Financial Oversight: Process payments, handle refunds, and monitor financial transactions.
• Monitoring and Reporting: Generate reports, track vehicle status, and oversee the system dashboard.
• Complaint Resolution: Address and resolve customer complaints and issues.
• Promotions: Create and manage promotional offers and discounts.
• Compliance: Ensure adherence to local regulations and data protection rules.
• Data Management: Perform system backups and restore the system when needed

1.2.3 The features that are required for the Manager are:
• Driver Scheduling: Assign shifts and plan work schedules for drivers.
• Trip Monitoring: Track the status of ongoing trips and assist with issues.
• Routing: Provide drivers with optimized routes considering traffic conditions.
• Performance Tracking: Monitor and evaluate driver performance based on trip completion and
ratings.
• Customer Assistance: Help customers with issues during their trips.
• Vehicle Dispatch: Assign vehicles to drivers as per requirements.
• Revenue Analysis: Review revenue data and assess profitability.
• Feedback Review: Look at customer feedback for service quality improvements.

1.2.4 The features that are required for the Driver are:
• Trip Management: Accept or decline ride requests and navigate using maps.
• Status Updates: Change availability status (available, on trip, offline).
• Payment Collection: Collect payments through various methods from customers.
• Customer Communication: Contact customers for trip details and updates.
• Vehicle Inspection: Check the vehicle's condition before starting trips.
• Emergency Handling: Access emergency contacts and instructions.
• Performance Tracking: View personal performance metrics and customer ratings.

23010101172 Jatin Nadiyapara Page |1

 SRS – “Taxi Management System”

1.2.5 The features that are required for the Customer are:
• Ride Booking: Request and book taxis via app, website, or phone.
• Tracking: Track the taxi's location and estimated arrival time.
• Fare and Payment: Get fare estimates and pay securely using various methods.
• Profile Management: Update personal details and preferences in their profile.
• Trip History: View details of past trips and payments.
• Feedback and Ratings: Rate drivers and provide feedback on trips.
• Discounts and Offers: Apply promo codes and discounts for rides.

1.3 Functional Requirement

1.3.1 Admin
• Add Users: Add new users like drivers, managers, and customers.
• Edit Users: Edit details of existing users.
• Delete Users: Remove users from the system.
• Set Roles: Assign roles (admin, manager, driver, customer) to users.
• View Dashboard: Access a main dashboard with key metrics and system status.
• Configure Settings: Set up system preferences like pricing, service areas, and vehicle options.
• Generate Reports: Create reports on bookings, revenue, and user activity.
• Track Vehicles: Monitor vehicle status, including availability and condition.
• Handle Payments: Oversee financial transactions, including processing payments and refunds.
• Respond to Complaints: Address and resolve customer complaints and issues.
• Create Promotions: Develop and activate promotional offers and discounts.
• Ensure Compliance: Verify adherence to local regulations and data protection rules.
• Backup Data: Perform regular system backups to prevent data loss.
• Restore System: Use backups to restore system functionality if needed.

1.3.2 Manager
• Assign Shifts: Schedule drivers for specific shifts.
• Monitor Trips: Keep an eye on ongoing trips and their statuses.
• Provide Routes: Give drivers optimized routes considering traffic conditions.
• Track Performance: Check driver performance, like how well they complete trips and their ratings.
• Help Customers: Assist customers with issues during their trips.
• Dispatch Vehicles: Assign vehicles to drivers based on needs.
• Plan Schedules: Create and adjust driver work schedules.
• View Feedback: Look at customer feedback and ratings for quality improvements.
• Resolve Issues: Address complaints from customers regarding service or billing.
• Check Revenues: Review revenue data and profitability for different areas.

1.3.3 Driver
• Accept Trips: Accept or decline ride requests.
• Use Navigation: Access maps and directions for efficient travel.
• Update Status: Change status to show availability (available, on trip, offline).
• Collect Payments: Take payments from customers through various methods.
• Communicate with Customers: Contact customers for trip details and updates.
• Inspect Vehicle: Check vehicle before starting trips for safety.

23010101172 Jatin Nadiyapara Page |2

 SRS – “Taxi Management System”

• Set Availability: Update availability for taking rides.

• Handle Emergencies: Access emergency contacts and instructions.
• View Feedback: See customer ratings and comments.
• Track Own Performance: View personal performance data like trip completion and ratings.

1.3.4 Customer
• Request Rides: Book a taxi using the app, website, or phone.
• Track Taxi: See the taxi’s location and estimated arrival time.
• Get Fare Estimate: See an estimated fare before booking.
• Pay for Rides: Pay securely using various methods like cards or mobile wallets.
• Cancel Rides: Cancel a booking within a given time frame without charges.
• Rate Drivers: Provide ratings and feedback on drivers and trips.
• Edit Profile: Update personal details and preferences in their profile.
• Receive Notifications: Get alerts for booking confirmation, taxi arrival, and trip updates.
• Use Accessibility Features: Access options for special needs like wheelchair access.
• View Trip History: Check details of past trips and payments.
• Apply Discounts: Use promo codes and discounts when booking rides.
• Schedule Rides: Schedule rides for future dates and times.
• Contact Driver: Communicate with the driver directly through the app.
• Choose Vehicle Type: Select preferred vehicle type if available.
• Save Locations: Save frequently used locations like home or work.
• View Driver Details: See driver’s name, photo, and vehicle information before the ride.

1.4 Non-Functional Requirement

1.4.1 Usability:
The UI should be simple enough for everyone to understand and get the relevant information without
any special training. Different languages can be provided based on the requirements.
1.4.2 Accuracy:
The data stored about the books and the fines calculated should be correct, consistent, and reliable.
1.4.3 Availability:
The System should be available for the duration when the library operates and must be recovered
within an hour or less if it fails. The system should respond to the requests within two seconds or less.
1.4.4 Maintainability:
The software should be easily maintainable and adding new features and making changes to the
software must be as simple as possible. In addition to this, the software must also be portable.
1.4.5 Response Time:
The system should respond to user queries and actions (e.g., booking a taxi, viewing available
taxis) within 2 seconds under normal load conditions.
1.4.6 Data Protection:
All user data, including payment information and personal details, must be encrypted in transit
(using TLS) and at rest (using AES-256 encryption).

23010101172 Jatin Nadiyapara Page |3

 SRS – “Taxi Management System”

2 Design and Implementation Constraints

2.1 Use case diagram

Figure 2.1-1 Use case diagram for Taxi management System

23010101172 Jatin Nadiyapara Page |4

 SRS – “Taxi Management System”

Figure 2.1-2 Use case diagram for Taxi management System

23010101172 Jatin Nadiyapara Page |5

 SRS – “Taxi Management System”

2.2 Activity diagram and Swimlane diagram

Figure 2.2-1 Activity diagram for taxi booking

23010101172 Jatin Nadiyapara Page |6

 SRS – “Taxi Management System”

Figure 2.2-2 Activity diagram for profile edit

23010101172 Jatin Nadiyapara Page |7

 SRS – “Taxi Management System”

Figure 2.2-3 Swimlane diagram for taxi booking

23010101172 Jatin Nadiyapara Page |8

 SRS – “Taxi Management System”

Figure 2.2-4 Swimlane diagram for profile edit

23010101172 Jatin Nadiyapara Page |9