ADVANCE SOFTWARE

ENGINEERING

“City Taxi”

Group Member

Shobikah Karthigaiselvan – 23039179

Vivekan Rasukumaran – 23039169

Puwaneshwaram Chathurangani - 23039175

Chathuragani - 23039175
Table of Content

Abstract .............................................................................................................................. 11

Introduction ........................................................................................................................ 12

Objective ............................................................................................................................ 13

Goal .................................................................................................................................... 14

Non-Functional / Operational Requirements ................................................................. 15

Functional Requirements ............................................................................................... 17

System Design ................................................................................................................... 20

UML Diagram ................................................................................................................ 20

Use case Diagram ...................................................................................................... 20

ER-Diagram ............................................................................................................... 22

Dataflow Diagram ...................................................................................................... 23

Activity Diagram ....................................................................................................... 24

Class Diagram ............................................................................................................ 25

Architecture Diagram................................................................................................. 26

Sequence Diagram ..................................................................................................... 27

Admin sequence diagram ....................................................................................... 27

Customer Sequence Diagram ................................................................................. 29

Hiring Cab Sequence Diagram .............................................................................. 32

Flowchart ................................................................................................................... 34

Admin .................................................................................................................... 34
 Operator ................................................................................................................. 35

Customer ................................................................................................................ 36

Driver ..................................................................................................................... 37

Pseudocode ................................................................................................................ 38

Database ......................................................................................................................... 40

Wireframe ...................................................................................................................... 44

Homepage .................................................................................................................. 45

Customer Register form ............................................................................................. 47

Customer login ........................................................................................................... 48

Customer dashboard................................................................................................... 49

Customer booking form ............................................................................................. 50

Admin and Operator login form ................................................................................ 51

Admin dashboard ....................................................................................................... 52

Admin cab category ................................................................................................... 53

Admin cab category (add new category) ................................................................... 54

Operator dashboard .................................................................................................... 55

Operator taxi reservation form ................................................................................... 56

Interface ......................................................................................................................... 57

Function of the system ................................................................................................... 76

Implementing the system ................................................................................................... 78

Implementation code .......................................................................................................... 79

 Customer Login ............................................................................................................. 79

Insert Cab code .............................................................................................................. 79

Insert cab category code................................................................................................. 80

Insert booking code ........................................................................................................ 81

Insert Reservation code .................................................................................................. 81

Collaboration tools ............................................................................................................. 82

Critical assessment ............................................................................................................. 83

Component clarification..................................................................................................... 84

Test plan for City Taxi ....................................................................................................... 87

Test Case for City Taxi ...................................................................................................... 90

Future recommendation ................................................................................................... 106

Reference ......................................................................................................................... 107

Table of Figures

Figure 1: Incremental model .............................................................................................. 19

Figure 2: Use Case diagram ............................................................................................... 22

Figure 3: ER-Diagram........................................................................................................ 23

Figure 4: Data Flow Diagram ............................................................................................ 24

Figure 5: Activity Diagram ................................................................................................ 25

Figure 6: Class Diagram .................................................................................................... 25

Figure 7: Architecture Diagram ......................................................................................... 26

Figure 8: Admin Sequence Diagram .................................................................................. 28

Figure 9: Customer Sequence Diagram ............................................................................. 31

Figure 10: Hiring Cab sequence diagram .......................................................................... 33

Figure 11: Admin flowchart............................................................................................... 34

Figure 12: Operator flowchart ........................................................................................... 35

Figure 13: Customer flowchart .......................................................................................... 36

Figure 14: Driver flowchart ............................................................................................... 37

Figure 15: Admin database ................................................................................................ 40

Figure 16: Booking database ............................................................................................. 40

Figure 17: Cab database ..................................................................................................... 41

Figure 18: category database ............................................................................................. 41

Figure 19: Customer_Registration database ...................................................................... 42

Figure 20: Location database ............................................................................................. 42

Figure 21: Operator database ............................................................................................. 42

Figure 22: rating database .................................................................................................. 43

Figure 23: Reservation database ........................................................................................ 43

Figure 24: UnRegisteredcustomer_Reserve database ........................................................ 44

Figure 25: Homepage ......................................................................................................... 45

Figure 26: Customer register page ..................................................................................... 47

Figure 27: Customer login ................................................................................................. 48

Figure 28: Customer dashboard ......................................................................................... 49

Figure 29: Customer booking form.................................................................................... 50

Figure 30: Admin and operator login................................................................................. 51

Figure 31: Admin dashboard ............................................................................................. 52

Figure 32: Admin cab category.......................................................................................... 53

Figure 33: Admin cab category (add new category) .......................................................... 54

Figure 34: Operator dashboard .......................................................................................... 55

Figure 35: Operator taxi reservation form ......................................................................... 56

Figure 36: Homepage ......................................................................................................... 57

Figure 37: Service page ..................................................................................................... 57

Figure 38: Contact page ..................................................................................................... 58

Figure 39: Customer login ................................................................................................. 58

Figure 40: Customer register ............................................................................................. 59

Figure 41: Customer dashboard ......................................................................................... 59

Figure 42: Customer booking ............................................................................................ 60

Figure 43: Customer Hire Cab ........................................................................................... 60

Figure 44: Customer see booking ...................................................................................... 61

Figure 45: Customer Reservation ...................................................................................... 61

Figure 46: Customer rate Driver form ............................................................................... 62

Figure 47: Customer view reservation ............................................................................... 62

Figure 48: Customer rate driver ......................................................................................... 63

Figure 49: Admin login form ............................................................................................. 63

Figure 50: Admin dashboard ............................................................................................. 64

Figure 51: Admin manage the cab category ...................................................................... 64

Figure 52: Admin manage cab category (Add new customer) .......................................... 65

Figure 53: Admin manage cab ........................................................................................... 65

Figure 54: Admin manage cab (Add new cab) .................................................................. 66

Figure 55: Admin manage location.................................................................................... 66

Figure 56: Admin manage location (Add new location) ................................................... 67

Figure 57: Admin view reservation ................................................................................... 67

Figure 58: Admin view booking ........................................................................................ 68

Figure 59: Admin registered customer .............................................................................. 68

Figure 60: Admin manage users ........................................................................................ 69

Figure 61: Admin manage users (Add new users) ............................................................. 69

Figure 62: Admin booking report ...................................................................................... 70

Figure 63: Admin booking report ...................................................................................... 70

Figure 64: Admin reservation report.................................................................................. 71

Figure 65: Admin reservation report.................................................................................. 71

Figure 66: Admin reservation report.................................................................................. 72

Figure 67: Operator dashboard .......................................................................................... 72

Figure 68: Operator reserve taxi ........................................................................................ 73

Figure 69: Operator reserve a vehicle ................................................................................ 73

Figure 70: Operator see available driver ............................................................................ 74

Figure 71: Driver login form.............................................................................................. 74

Figure 72: Driver dashboard .............................................................................................. 75

Figure 73: Driver booking ................................................................................................. 75

Figure 74: Driver managing Status .................................................................................... 76

Figure 75: Add a new category in the Admin form ........................................................... 76

Figure 76: Delete a cab category in the admin form .......................................................... 77

Figure 77: Customer hiring a cab....................................................................................... 77

Figure 78: Customer login code ......................................................................................... 79

Figure 79: Insert cab code 1 ............................................................................................... 79

Figure 80: Insert cab category code ................................................................................... 80

Figure 81: Insert cab code 2 ............................................................................................... 80

Figure 82: Insert booking code .......................................................................................... 81

Figure 83: Insert reservation code...................................................................................... 81

Table of Table

Table 1: Team Confirmation .............................................................................................. 83

Table 2: Component 1 ........................................................................................................ 84

Table 3: Component 2 ........................................................................................................ 84

Table 4: Component 3 ........................................................................................................ 85

Table 5: Component 4 ........................................................................................................ 86

Table 6: Test plan............................................................................................................... 87

Table 7: Test case 1............................................................................................................ 90

Table 8: Test case 2............................................................................................................ 91

Table 9: Test case 3............................................................................................................ 92

Table 10: Test case 4.......................................................................................................... 93

Table 11: Test case 5.......................................................................................................... 94

Table 12: Test case 6.......................................................................................................... 95

Table 13: Test case 7.......................................................................................................... 96

Table 14: Test case 8.......................................................................................................... 97

Table 15: Test case 9.......................................................................................................... 98

Table 16: Test case 10........................................................................................................ 99

Table 17: Test case 11...................................................................................................... 100

Table 18: Test case 12...................................................................................................... 101

Table 19: Test case 13...................................................................................................... 102

Table 20: Test case 14...................................................................................................... 103

Table 21: Test case 15...................................................................................................... 104

Table 22: Test case 16...................................................................................................... 105

Abstract

The primary goal of "The City Taxi" is to establish a reliable, accessible, and affordable
transport service that caters specifically to the transportation needs of low to mid-income
passengers. By focusing on this demographic, the service aims to address the challenges
faced by individuals with constrained financial resources, providing them with a convenient
and cost-effective solution for their mobility requirements.

Implemented using a robust 3-tier architecture, the system integrates a backend database, a
middle tier utilizing XAMPP and PHP, and a front-end client accessible through a web
browser.

This project adopts a multi-tiered architecture, leveraging server and client-side scripting
techniques, and employing cutting-edge implementation technologies, including PHP
(Object-Oriented Programming), jQuery, Bootstrap, HTML5, and relational databases like
MySQL.

The project’s objective is to provide a reliable and cost-effective transport service tailored
to the transportation needs of low to mid-income passengers. The focus is on offering an
accessible and convenient mobility solution, enhancing the overall quality and affordability
of transportation for individuals within this income demographic.
Introduction

In the rapidly changing urban environment, where mobility is a key determinant of

accessibility and opportunity, "The City Taxi" emerges as a purposeful solution designed
to cater specifically to the transportation needs of low to mid-income passengers.
Navigating through the complexities of contemporary city living, this transport service is
not merely a conveyance, but a strategic response to the challenges faced by individuals
with constrained financial resources. With a commitment to affordability, reliability, and
inclusivity, The City Taxi seeks to redefine urban mobility, providing a reliable and cost-
effective transportation option for those who often find themselves underserved in the
current transportation landscape. As we embark on an exploration of this initiative, it
becomes clear that at its core, "The City Taxi" is a transformative force, aiming to enhance
the daily lives of individuals within the low to mid-income brackets through accessible and
efficient transportation services.

Our service is not merely about reaching a destination; it’s about the journey itself. City
taxi leverages cutting- edge technology to offer a seamless and user-friendly experience.
The intuitive mobile application empowers passengers to effortlessly book a taxi, track its
real time location, and experience a level of transparency that in stills confidence. We
understand that time is of the essence, and our commitment to prompt service ensures that
our passengers reach their destination on time and every time.

This online platform facilitates seamless interactions between passengers and vehicle
owners/drivers, providing an array of features for a user-centric and efficient taxi service.
During registration, both passengers and vehicle owners/drivers receive a personalized
login, enhancing the security and accessibility of the system. Passengers can effortlessly
reserve taxis through the user-friendly website, receiving detailed information about the
assigned driver and vehicle via SMS, ensuring transparency and peace of mind. Drivers
maintain real-time connectivity through the web-based system on their smartphones,
always ready for service unless marked 'BUSY.' The platform encourages passenger
feedback, allowing them to rate drivers based on their travel experiences, fostering a culture
of accountability and service improvement.
Passengers can choose drivers from a list of those closest to their location, a feature that
enhances efficiency and reduces waiting times. Simultaneously, drivers can update their
availability status, ensuring accurate representation on the available drivers' list. For
unregistered passengers, a telephone operator facilitates manual reservations, ensuring
inclusivity. While customer details remain private during phone bookings, essential
information is recorded in the system, and confirmation SMS messages are sent.

Utilizing advanced relocation technology, the system automatically retrieves and displays
the closest drivers to passengers, optimizing the matching process. The same technology
allows the precise setting of passenger locations when reserving a taxi, either by the
passenger or the operator. The system calculates journey payments automatically, allowing
passengers to pay securely through the platform, providing a seamless and cashless
transaction experience. Drivers receive instant notifications of successful payments,
ensuring a streamlined and efficient financial process. Finally "The City Taxi" transforms
urban transportation by seamlessly integrating technology, efficient operations, and
passenger-focused features, ultimately creating a reliable and accessible transport service
tailored to the unique needs of low to mid-income passengers.

Objective

The user-oriented objective for "The City Taxi" transport service, within the context of
developing the project using a PHP web application, is to create a seamless and accessible
platform for low to mid-income passengers. The thesis aims to develop a user-friendly PHP
web application that prioritizes affordability, reliability, and convenience in urban
transportation. Users anticipate a hassle-free experience, from registering and reserving
taxis effortlessly to receiving timely SMS notifications with driver details. The goal is to
provide passengers with a technologically advanced and cost-effective solution,
emphasizing a user-centric design that enhances the overall quality of their commuting
experience. Through the development of this PHP web application, the thesis endeavours
to contribute to the optimization of urban transportation for the target demographic,
aligning with the unique needs and preferences of low to mid-income passengers.
Goal

The goals for "The City Taxi" transport service, with a focus on targeting low to mid-
income passengers, encompass various aspects to ensure the provision of an inclusive,
reliable, and affordable urban transportation solution. The City Taxi aims to establish itself
as a socially responsible, technologically advanced, and user-focused transport service,
ultimately enhancing urban mobility for low to mid-income passengers.

The goal of this application is to:

 Provide cost-effective transportation options to accommodate the financial

constraints of low to mid-income passengers, making the service accessible to a
broader demographic.
 Ensure a reliable and punctual transport service to meet the daily commuting needs
of passengers, building trust and confidence in the service's consistency.
 Develop user-friendly interfaces, both on the web and mobile applications, to make
booking taxis and accessing information straightforward for passengers with
varying levels of technological familiarity.
 Integrate innovative technologies such as real-time tracking, automated payment
processing, and efficient route planning to enhance the overall user experience and
stay competitive in the market.
 Prioritize passenger satisfaction by implementing features such as driver ratings,
ensuring accountability and continuous improvement in service quality.
 Address the needs of unregistered passengers through manual reservations
facilitated by telephone operators, ensuring that those without access to the online
system can still avail of the service.
 Establish efficient communication channels, including SMS notifications for
booking confirmations and driver details, enhancing transparency and keeping
passengers informed.
 Utilize geolocation technology to optimize the matching process, allowing
passengers to select drivers from a list of those closest to their location, reducing
waiting times and improving efficiency.
  Explore eco-friendly transportation practices to contribute positively to
environmental sustainability, aligning with the growing emphasis on responsible
and green initiatives.
 Ensure transparent and straightforward payment processes, with automated
calculations of journey costs, providing passengers with clear information and
reducing potential sources of friction.
 Recognize the social and economic impact of transportation services on
communities, striving to contribute positively to the well-being and accessibility of
individuals within the low to mid-income brackets.

Non-Functional / Operational Requirements

Non-functional requirements define the attributes that characterize the overall behaviour
and performance of a system rather than specific features.

Performance: The system should be capable of handling a high volume of simultaneous

users, ensuring optimal performance during peak hours. Response times for user
interactions, such as booking a taxi or viewing driver availability, should be minimized to
enhance user experience.

Reliability: The system must have a high level of reliability, ensuring minimal downtime
for maintenance or unexpected issues. Backup and recovery mechanisms should be in place
to safeguard against data loss and system failures.

Security: Passenger and driver data must be securely stored and encrypted to protect
against unauthorized access and data breaches. Secure communication channels, such as
HTTPS, should be implemented to protect sensitive information during data transmission.

Scalability: The system should be scalable to accommodate a growing user base and
increasing demand for the service over time. Scalability considerations should extend to
both the backend infrastructure and the user interface.

Usability: The user interfaces, both on the web and mobile applications, should be designed
for ease of use, catering to passengers with varying levels of technological proficiency.
Accessibility features should be implemented to ensure inclusivity for users with
disabilities.

Availability: The service must be available 24/7, allowing passengers to book taxis at any
time, reflecting the dynamic nature of urban transportation needs.

Maintainability: The system should be designed for ease of maintenance, allowing for
updates, bug fixes, and feature enhancements without significant downtime. Codebase
documentation and commenting should be thorough to facilitate ongoing development and
maintenance.

Interoperability: The system should be interoperable with various devices and operating
systems to cater to a diverse user base. Integration with third-party services, such as
payment gateways and mapping services, should be seamless and efficient.

Compliance: The system must comply with relevant data protection and privacy
regulations, ensuring the secure handling of personal information. Adherence to
transportation industry standards and local regulations should be considered.

Environmental Considerations: If applicable, the system should support eco-friendly

initiatives, such as encouraging the use of electric vehicles or implementing route
optimization for fuel efficiency.
Functional Requirements

Functional requirements describe the specific features and capabilities that a system must

Admin Dashboard: An admin dashboard should provide an overview of system activities,

including ride statistics, driver management, and financial data.

Driver Allocation: Efficient algorithms should be in place to allocate drivers based on

proximity, availability, and passenger preferences. Drivers should have the option to accept
or reject ride requests.

User Registration and Authentication: Users should be able to create accounts securely.
The system should authenticate users to ensure secure and personalized access.

Booking System: The application should allow users to book a taxi easily through a user-
friendly interface. Users should be able to specify pick-up and drop-off locations.

Fare Calculation: The application should calculate fares accurately based on distance,
time, and any additional charges. Transparent fare structures should be communicated
clearly to the users.

Manual Reservation by Operator: Operators should be able to manually reserve drivers

for passengers through a web-based system. This option is provided for unregistered
passengers using a telephone operator.

Payment Integration: Passengers should be able to make payments for rides through the
system using various payment methods. Drivers should receive payment confirmation
notifications.

Review and Rating System: Passengers should be able to provide feedback and ratings
for drivers and the overall service. Drivers should have access to their ratings and reviews
to improve their service.
Taxi Reservation System: Passengers should be able to reserve taxis through the website
or mobile app. Reservation details should include pickup and drop-off locations, date, and
time preferences.

Design and Development Environment

 HTML
 Adobe XD
 Edraw max
 JQuery
 PHP
 MySQL
 Adobe Photoshop

System Requirements

Hardware Requirements

Server side

Desktop Server PC with:

 1TB Hard Disc

 Core i7 (3.0 GHz) Processor
 32GB Ram
 Network Card
 High Bandwidth Internet Connection.

Client side

Admin/Customer – Any type of device with the internet connection and web browsers like
Laptop, PC, and Tab
Software Requirements

Server side

 Windows Server 2019 Operating system

 Xampp Server
 MySQL server with recent version
 Apache with PHP 5.0

Client side

Driver/ Customer– Any operating system with Windows, Android, IOS, Any device with
a high speed internet connection

Any type of device with internet connection and web browsers like chrome, safari, Firefox
and opera.

System Methodology

The SDLC (Software development lifecycle) is a process to develop a system. A variety of

models are used to create the software development life cycle. However, each offers unique
benefits and teachers. SDLC includes four basic models: waterfall, incremental, prototype,
and spiral.

Requirements

Operator Additional
User Login & Location and Payment and Final
management Features and
Registration Driver rating Deployment
and Taxi Testing
management
reservation

Customer Operator Driver Additional Final

Payment
registration Management management features deployment

Taxi Location Rating driver Testing

User login
reservation

Admin
dashboard

Figure 1: Incremental model

The incremental model is develop with a way to success is achieved through multiple
development cycles. We can refer to this model as a incremental model. Cycles are
separated into smaller, more manageable iterations. Iteration occurs throughout the
requirements, design, implementation, and testing phases. The first iteration creates a
functional adaptation of software, resulting in running software early in the software life
cycle.

System Design

The system design is the process of the art of the defining the architecture, component,
modules, interfaces and the system to satisfy the requirement. The system architecture
creates the blue print for the design with the necessary specification for the hardware,
software; people and data resources. In the many cases, multiples architecture are evaluated
before one is selected.

UML Diagram

The Unified Modelling Language (UML) is a general-purpose modelling language. The

primary goal of UML is to define a standard way to visualise how a system has been
designed. It is very similar to blueprints used in other areas of engineering. UML is not a
programming language, but rather a visual one (geeksforgeeks, 2020).

Use case Diagram

In a user case diagram for "The City Taxi" transport service targeting low to mid-income
passengers, the relationships between the admin, driver, customer, and operator can be
illustrated to provide a visual representation of their interactions and system functionalities.

Admin: The admin has the authority to manage and oversee the entire system. This includes
functionalities such as user management, system configuration, and access to analytical
data. The admin can view and modify driver and customer details, ensuring the smooth
operation of the service.

Driver: Drivers interact with the system primarily through a mobile application. They have
functionalities such as updating their availability status ('AVAILABLE' or 'BUSY'),
receiving ride requests, and accessing navigation information. The driver's interactions are
crucial for efficient service delivery and real-time communication.

Customer: Customers access the system through a web or mobile application to perform
various actions. This includes functionalities such as booking a taxi, viewing available
drivers, providing feedback, and making payments. The customer's interactions focus on
creating a seamless and user-friendly experience throughout the transportation process.

Operator: Operators assist unregistered passengers in making reservations manually,

offering an alternative for those without access to the online system. They enter customer
details into the system, ensuring that bookings are recorded, and confirmation SMS
messages are sent. The operator's role enhances inclusivity for all passengers.

Relationships in the User Case Diagram:

 The admin oversees and manages both drivers and customers, ensuring the overall
functionality and efficiency of the system.
 Drivers interact directly with customers when accepting ride requests, creating a
direct relationship between these two entities.
 Customers have a direct relationship with the system, booking rides and providing
feedback on their experiences.
 The operator facilitates manual reservations, linking unregistered passengers with
the system and ensuring a smooth booking process.

In this user case diagram, the relationships and interactions between the admin, driver,
customer, and operator are visually depicted, providing a comprehensive overview of the
roles and functionalities within "The City Taxi" transport service.
 City Taxi PVT LTD

Login

Add Pickup Location Customer

<<Includes>>
Admin

Manage Taxi
Enter username & Password

Manage Reservation

Rate Driver
Manage Location

Manage payment

Driver
Show Driver Availability
View Avaliable Driver details

Manage Taxi location

& pickup location

Operator

Reserver Taxi/Driver

Enter Credential <<Includes>> Register

Figure 2: Use Case diagram

ER-Diagram

The above shown image is the ER diagram. An ER diagram is a visual representation that
the data in a database design to shown the relationships between entities. The enterprise
schema, which is specified by the ER data model, graphically depicts the entire logical
structure of a database. It serves as the foundation for building a database. ER diagram
outline entities as rectangles and their attributes as ovals, and relationships as lines,
providing a concise overview of data structure and connections. Primary keys serve as
unique identifiers for entities, establishing the foundation for a well-organized and
streamlined database structure. Their role is essential in ensuring the uniqueness of each
record, contributing to efficient data management within the database schema.
 Figure 3: ER-Diagram

Dataflow Diagram

A Data Flow Diagram (DFD) for "The City Taxi" transport service targeting low to mid-
income passengers provides a visual representation of how data flows within the system. It
illustrates the processes, data stores, external entities, and data flows that constitute the
overall operation of the system.
 Reserve Taxi Check the Booking

Manage
Operator Admin Booking
Handle
Request Details Request
Details Request
Manage Details
Operator Details Admin Details Booking Details
Taxi
Control

Request
Details
Driver
Reservation
View driver details Taxi Details Manage

Request
Details
Request
Details supervise
Driver Details
Reservation Check
Details
Location Payment
Manage the Taxi location and pickup location

Customer Request Request

Details
Details
Location Payment
Details Details
Request
Details

Customer details
Client Booking Taxi

Client make payment

Figure 4: Data Flow Diagram

Activity Diagram

The activity diagram provides a visual guide to the dynamic flow of activities within "The
City Taxi" system, outlining the processes involved in customer booking, driver response,
ride execution, payment processing, and operator-assisted reservations. This diagram aids
in understanding the sequential interactions between various entities and the system in the
context of the taxi service.
 Admin Operator Customer Driver

Reserve Taxi Hire Taxi

Receive Customer
details

Check Available
Receive Customer
driver for specific details
pickup location

Pickup customer

Payment Drop at destination

Receive Payment Receive payment

from customer for the ride

Payment
confirmation SMS

Figure 5: Activity Diagram

Class Diagram

A fundamental visual representation in object-oriented modelling and design is the class

diagram. It shows a system's static structure by presenting classes, their attributes, their
methods, and the connections between them. Developers can use this diagram as a
blueprint for understanding the general architecture and interconnections of the software
system.
Driver

+Driver_Id: Int
+Email: String
+driver_contant: int
+driver_address: String
0..* 1

+Login();
+Register();
+pickup(); 1
1
+Drop();
Admin +manage status();
Customer +logout();
+Admin_Id: Int
+Customer_Id: Int +username: String
+first_name: String +Password: int
+middle_name: String Operator
+last_name: String +Login(); +operator_Id: Int
+Gender: String
+manage cab_category(); +username: string
+Contact_number: Int +manage cab();
1 0..* +password: string
+address: String +manage location();
+email: String Name
+manage user(); 1 1 +login();
+ Password: String +manage registered_customer(); +reserve_taxi();
+view_reservation(); +view_avaliable_driver();
Name 1
+login(); +generate_Report(); +View_reservation();
+signup(); 1
1 1 1 1
+Book_cab();
+Reserve_Cab();
+Logout();
1 1

0..* 1 0..* 0..* 0..* 0..* 0..* 0..*

Taxi Payment Location Reservation Booking

+Reservation_Id: Int 1 +Booking_Id: Int
+Taxi_Id: Int +Payment_Id: Int +Location_Id: Int
+Date: date +Date: date
+Model: String +Amount: float +location_name: String
+Time: time +Time:time
+Quality: String +Date: date +Description: String
+Brand: String +Time: time
+pickup_location();
-calamount(); +drop_location();
0..*

Figure 6: Class Diagram

Architecture Diagram

The process of breaking down a large, complex system into smaller subsystems is known
as architectural design. An architecture diagram for "The City Taxi" transport service
targeting low to mid-income passengers provides a high-level view of the system's overall
structure and how its components interact. The purpose of these subsystems is to provide
some related services.

Book via
class

Driver
Operator
Avaliable Reserve Taxi
make booking
location

Customer 5 seater van

Admin Server

Mini bus

Book via
online

10 seater bus
Figure 7: Architecture Diagram
Sequence Diagram

A sequence diagram for "The City Taxi" transport service targeting low to mid-income
passengers depicts the interactions and flow of messages between different components or
objects over a period of time.

Admin sequence diagram

An Admin Sequence Diagram for "The City Taxi" transport service, targeting low to mid-
income passengers, would depict the interactions and message flow between the admin and
the system components.

Admin Logs In: The sequence begins with the admin logging into the system. The message
flows from the admin object to the authentication component, verifying the admin's
credentials.

System Authenticates Admin: The system authenticates the admin's credentials, ensuring
secure access. This involves interactions between the admin, authentication component,
and potentially the user database.

Admin Accesses Dashboard: Upon successful authentication, the admin accesses the
system dashboard. The message flows from the admin object to the dashboard component,
initiating the display of relevant information.

Admin Manages Users: The admin interacts with the system to manage users, including
customers and drivers. This may involve actions such as viewing user details, modifying
information, or deactivating accounts. Interactions occur between the admin, user
management component, and user database.

Admin Analyses System Data: The admin utilizes the system to analyse data, such as ride
statistics, user feedback, or financial reports. Interactions occur between the admin,
analytics component, and the database.

Admin Configures System Settings: The admin configures system settings, potentially
adjusting parameters related to pricing, promotions, or general system behaviour.
Interactions take place between the admin, configuration component, and the system
settings.
Admin Logs Out: The sequence concludes with the admin logging out of the system. The
message flows from the admin object to the logout component, ensuring a secure
termination of the admin session.

This Admin Sequence Diagram illustrates the dynamic interactions between the admin and
various system components, showcasing how the admin navigates, manages users, analyzes
data, configures settings, and securely logs out of the system in the context of "The City
Taxi" transport service.

Admin Sequence
Diagram

Login Verify
Form Database
admin

Admin

Click on the login button

Varify Username and
Username and password
password
matched

Successfully verify
Message: Login Admin login successfully
successfully

Figure 8: Admin Sequence Diagram

Customer Sequence Diagram

A Customer Sequence Diagram for "The City Taxi" transport service, targeting low to mid-
income passengers, would illustrate the interactions and message flow between the
customer and various system components.

Customer Opens the App: The sequence begins with the customer opening the taxi
service application (web or mobile). The message flows from the customer object to the
application component.

Customer Logs In: The customer logs into the system by providing their credentials. The
message flows from the customer object to the authentication component for verification.

System Authenticates Customer: The system authenticates the customer's credentials to

ensure secure access. This involves interactions between the customer, authentication
component, and possibly the user database.

Customer Requests a Ride: The customer initiates a ride request through the application,
selecting pickup and drop-off locations. The message flows from the customer object to the
ride request component.

System Validates Ride Request: The system validates the ride request, checking factors
like driver availability and location. Interactions occur between the customer, ride request
component, and the system.

System Notifies Available Driver: If the ride request is valid, the system notifies an
available driver. This involves interactions between the system, the driver, and potentially
the ride object to update the ride status.

Driver Accepts the Ride: The driver, upon receiving the notification, accepts the ride
request. The message flows from the driver object to the system, confirming the acceptance.

System Confirms Ride and Provides Details: The system confirms the ride, providing
details such as the driver's name, vehicle information, and estimated arrival time. This
involves interactions between the system, ride object, and the customer.

Ride in Progress: The sequence moves into the ride execution phase, where the driver
picks up the customer, and the ride progresses to completion. Continuous interactions occur
between the customer, the driver, and the system to update the ride status, location, and
other relevant details.
Payment Process Initiation: After the ride is completed, the system initiates the payment
process. Interactions occur between the customer, the ride object, and the system to
calculate the fare and verify payment details.

Payment Verification: The system verifies the payment details, ensuring the accuracy and
security of the transaction. Interactions involve the system, the payment gateway (external
service), and the customer.

Notification of Successful Payment: Upon successful payment verification, the system

notifies the customer about the completed transaction. This involves interactions between
the system and the customer.

Customer Logs Out: The sequence concludes with the customer logging out of the
application. The message flows from the customer object to the logout component, ensuring
a secure termination of the customer session.

This Customer Sequence Diagram illustrates the dynamic interactions between the
customer and various system components, demonstrating how the customer logs in,
requests a ride, completes the ride, makes a payment, and securely logs out within "The
City Taxi" transport service.
 Customer

System Web-Browser Database

Customer

Open the website

Select login / sign-up Request login information

Login page load

Register

Transfer register data

Save the register data
Login
verify the data
Verify the data

Return the data

Login

Figure 9: Customer Sequence Diagram

Hiring Cab Sequence Diagram

A "Hiring a Cab" Sequence Diagram for "The City Taxi" transport service, targeting low
to mid-income passengers, illustrates the interactions and message flow between a user
hiring a cab and various system components. Here's an explanation of the key components
and interactions in a Hiring a Cab Sequence Diagram:

User Requests a Cab: The sequence begins with the user initiating a request for a cab
through the taxi service application (web or mobile). The message flows from the user
object to the ride request component.

System Validates Ride Request: The system validates the ride request, checking for
factors like driver availability, location, and other relevant criteria. Interactions occur
between the user, ride request component, and the system.

System Notifies Available Driver: If the ride request is valid, the system notifies an
available driver about the request. This involves interactions between the system, the driver,
and potentially the ride object to update the ride status.

Driver Accepts the Ride: The driver, upon receiving the notification, accepts the ride
request. The message flows from the driver object to the system, confirming the acceptance.

System Confirms Ride and Provides Details: The system confirms the ride, providing
details such as the driver's name, vehicle information, and estimated arrival time. This
involves interactions between the system, ride object, and the user.

Ride in Progress: The sequence transitions into the ride execution phase, where the driver
picks up the user, and the ride progresses to completion. Continuous interactions occur
between the user, the driver, and the system to update the ride status, location, and other
relevant details.

Payment Process Initiation: After the ride is completed, the system initiates the payment
process. Interactions occur between the user, the ride object, and the system to calculate the
fare and verify payment details.

Payment Verification: The system verifies the payment details, ensuring the accuracy and
security of the transaction. Interactions involve the system, the payment gateway (external
service), and the user.
Notification of Successful Payment: Upon successful payment verification, the system
notifies the user about the completed transaction. This involves interactions between the
system and the user.

User Provides Rating and Feedback: After the ride, the user has the option to provide a
rating and feedback on the driver and the overall experience. Interactions occur between
the user, feedback component, and the system.

Sequence Conclusion: The sequence concludes with the completion of the hiring process,
payment, and user feedback. The objects involved include the user, driver, ride, payment
gateway, and feedback component.

This "Hiring a Cab" Sequence Diagram illustrates the dynamic interactions between the
user and various system components, demonstrating how a user hires a cab, completes the
ride, makes a payment, provides feedback, and receives notifications within "The City
Taxi" transport service.
Hire Taxi

Sign-in Web-Browser Vehicle Location Reservation Operator

Taxi
Customer driver
Login in the system
open the website
Select vehicle
Select location
Hire a taxi
Contact operator
Request a Taxi check Available driver

Customer requested to hire a taxi

Request accepted Request accepted

Select the pickup and drop location Assign driver

location confirmation

Send vehicle information

Confirm the ride

Booking Confirmation

Pick-up customer

Change status to "BUSY"

Payment for the ride

Change status to
"availability"

Figure 10: Hiring Cab sequence diagram

Flowchart

Admin

A flowchart for the admin functionalities in "The City Taxi" transport service targeting low
to mid-income passengers can provide a visual representation of the step-by-step process
involved in admin tasks. The flowchart is designed to be sequential, guiding the admin
through the logical steps of their tasks. Decision points are used to account for different
outcomes, such as successful or unsuccessful login attempts. Each step in the flowchart
corresponds to a specific action or decision the admin can take within the system. This
flowchart provides a visual overview of the administrative processes within "The City
Taxi" transport service, outlining the steps an admin would follow to manage users, analyze
data, configure settings, and log out of the system.

Admin

Start

Input username and

password

Admin Receive information

Verify the received

information

If the information NO Request for more

is correct Information

Yes
Assign Task to the
Department
Update the received
information

Update the task

Generate report

END

Figure 11: Admin flowchart

Operator

This flowchart provides a visual overview of the operator's processes within "The City
Taxi" transport service, outlining the steps an operator would follow to handle phone
reservations, manage tasks, and log out of the system.

Operator

Start

Input username and

password

Access the Dashboard

Reserve a Taxi

View the list of avaliable drivers

Select the Driver

If the reservation is NO
confirm Reconfirm by the customer

YES

Send driver and vehicle

details to customer via
SMS

End

Figure 12: Operator flowchart

Customer

This flowchart provides a visual overview of the customer's processes within "The City
Taxi" transport service, outlining the steps a customer would follow to request a ride,
complete the ride, make a payment, provide feedback, and log out of the system.

Customer

Start

Register for the service

Input Email and

password

Get assess for dashboard

Reserve a taxi and Driver

Add a pickup location

Chosen taxi driver with

contact details

Rate the ride

End

Figure 13: Customer flowchart

Driver

This flowchart provides a visual overview of the driver's processes within "The City Taxi"
transport service, outlining the steps a driver would follow to log in, manage availability,
accept/reject ride requests, complete rides, and log out of the system.

Driver

Start

Register for the service

Input Email and

password

Get assess for dashboard

If driver is available NO Status "BUSY"

YES
Automatically added to available
drivers list

Receive reservation request

Accept Reservation

Change the status to

"BUSY"

Reach to the customer

pickup location

Start Trip

Reach Destination

Calculate the charge

amount

Automated payment

Receive Payment
confirmation

End

Figure 14: Driver flowchart

Pseudocode

Admin
Start
Input username and password
Admin receive information
Verify the received information
If (If the information is correct)
Assign task to the department
Else
Request for more information
Update the received information
Endif
Update the task
Generate report
End

Operator
Start
Input username and password
Access the dashboard
Reserve a taxi
View the list of available drivers
Select the driver
If (If the reservation is confirm)
Send driver and vehicle details to customer via email
Else
Reconfirm by the customer
Endif
End
Customer
Start
Register for the service
Input email and password
Get access for dashboard
Reserve a taxi and driver
Add and pickup location
Chosen taxi driver with contact details
Rate the driver
End

Driver
Start
Register for the service
Input email and password
Get access for dashboard
While
If (driver is available)
Automatically added to available driver list
Receive reservation request
Accept reservation
Else
Status “BUSY”
Endif
Change the status to “BUSY”
Reach to the customer pickup location
Start Trip
Reach destination
Calculate the charge amount
Automated payment
 Receive payment confirmation
End while loop
End

Database

Admin

Figure 15: Admin database

Booking

Figure 16: Booking database

Cab

Figure 17: Cab database

Category

Figure 18: category database

Customer_Registration

Figure 19: Customer_Registration database

Location

Figure 20: Location database

Operator

Figure 21: Operator database

Rating

Figure 22: rating database

Reservation

Figure 23: Reservation database

UnRegisteredcustomer_Reserve
 Figure 24: UnRegisteredcustomer_Reserve database

Wireframe

A wireframe for the homepage of "The City Taxi" transport service targeting low to mid-
income passengers serves as a skeletal representation of the webpage's layout and structure.
Wireframes focus on the arrangement of elements, without detailed design elements.
Wireframes are intentionally basic and lack detailed design elements.

They focus on layout, structure, and functionality. The wireframe serves as a blueprint for
the homepage design, allowing designers and stakeholders to visualize the overall structure
before detailed design work begins. The actual wireframe may vary based on specific
design decisions, user interface considerations, and branding elements for "The City Taxi"
transport service.
Homepage

Figure 25: Homepage

This is the site's wireframe view, which displays the homepage to users. The logo may be
seen on the top left of the border and navigation menu is placed. Beneath the header, the
wireframe may show a navigation menu with links to key sections such as Home, Service,
Featured car, new car, Brand, Contact and Log in. Slider with photos connected to cars is
in the middle design.

The hero section is a prominent area at the top of the homepage, often featuring a large
image or illustration related to taxi services. It may include a headline, a brief tagline, and
a call-to-action button encouraging users to explore the services.
A wireframe may include sections that briefly outline the key services provided by "The
City Taxi," such as reliable transportation for low to mid-income passengers. This section
could be accompanied by simple icons or illustrations.

An essential feature, the wireframe might display a simplified booking widget that allows
users to enter their pickup and drop-off locations, select ride preferences, and initiate a ride
request. This could include placeholders for text input and a 'Book Now' button.

To inform users about the availability of drivers, a wireframe might include a section
displaying the real-time status of drivers (e.g., 'Available,' 'Busy'). This section could be
designed as a dynamic element that updates in real-time.

Testimonials or reviews from satisfied customers could be included in the wireframe to

build trust and credibility. This section might feature brief quotes and star ratings.

A brief section about the company, its mission, and values may be included in the
wireframe to give users more information about "The City Taxi."

The wireframe concludes with a footer section that typically includes links to important
pages (Privacy Policy, Terms of Service), contact information, and possibly social media
icons. The actual wireframe may vary based on specific design decisions, user interface
considerations, and branding elements for "The City Taxi" transport service.
Customer Register form

This is the customer registration form for "The City Taxi" transport service for create a
new account, is a crucial element for on boarding new users. The top of the registration
form may feature a header with the taxi service's logo and a concise tagline or description
to reinforce the brand identity. A title such as "Customer Registration" is typically placed
at the top of the form to clearly indicate its purpose. Next to fill out the basic personal
information such as First Name, Middle Name (optional), Last Name, Gender and contact
information. Then the Fields for contact details are crucial for communication and account
verification to fill the Email Address and Address Details. Finally to create a password for
the secure the user’s account and a prominent "Register" button to submit the form once all
required fields are filled and if have any issue click the “back to home” button.

Figure 26: Customer register page

Customer login

The Customer login form for “The City Taxi” transport service, is a key element for users
to access their accounts. A tittle such as “Customer Login” is typically placed at the top of
the form to clearly indicate its purpose. Next to fill out the fields for users to enter their
login credentials such as Email Address and password and a prominent “Sign In” button to
submit the form after users enter their credentials. There is a link to the “Forget Password”
page or functionality, providing users with a way to reset their password if forgotten. There
is a way for going back to the previous page such as “Back to Home” button. There is also
a button to create or register a new account for users.

Figure 27: Customer login

Customer dashboard

The customer dashboard for "The City Taxi" transport service, serves as a centralized hub
where users can manage their rides, preferences, and account details. The top of the
dashboard often features a header with the taxi service's logo and a navigation menu
providing quick access to essential sections. A well-designed customer dashboard
contributes to user satisfaction, making it easy for passengers to manage their rides,
preferences, and account details within "The City Taxi" transport service.

Figure 28: Customer dashboard

Customer booking form

A wireframe for the customer booking form in "The City Taxi" transport service, serves as
a skeletal representation of the form's layout and structure. Wireframes focus on the
arrangement of elements without detailed design elements. This wireframe provides a
visual blueprint for the customer booking form, allowing designers and stakeholders to
visualize the form's structure and layout before detailed design work begins. This wireframe
provides a visual blueprint for the customer booking form, allowing designers and
stakeholders to visualize the form's structure and layout before detailed design work begins.

Figure 29: Customer booking form

Admin and Operator login form

A wireframe for the Admin and Operator login forms in "The City Taxi" transport service
is a simplified visual representation that outlines the layout and structure of the login forms.
Wireframes focus on the arrangement of elements without including detailed design
aspects. A title, such as "Admin Login," is placed at the top of the wireframe to clearly
indicate the purpose of the form. There are two buttons such as admin and for operator
login. There are two fields such as Username or Email Address and password to login. A
prominent “Login” button is included to submit the form after the admin enters their
credentials. These wireframes provide a visual blueprint for the Admin and Operator login
forms, allowing designers and stakeholders to visualize the forms' structure and layout
before detailed design work begins.

Figure 30: Admin and operator login

Admin dashboard

A wireframe for the Admin Dashboard in "The City Taxi" transport service, is a simplified
visual representation that outlines the layout and structure of the dashboard. Wireframes
focus on the arrangement of elements without including detailed design aspects. This
wireframe serves as a visual guide for the Admin Dashboard, enabling designers and
stakeholders to visualize the dashboard's structure and layout before detailed design work
begins.

Figure 31: Admin dashboard

Admin cab category

A wireframe for the Admin Cab Category section in "The City Taxi" transport service is a
simplified visual representation that outlines the layout and structure of the interface where
administrators can manage and categorize different types of cabs. Wireframes focus on the
arrangement of elements without including detailed design aspects. This wireframe
provides a visual guide for the Admin Cab Category section, enabling designers and
stakeholders to visualize the structure and layout before detailed design work begins.

Figure 32: Admin cab category

Admin cab category (add new category)

A wireframe for the "Add New Category" page in the Admin Cab Category section of "The
City Taxi" transport service is a simplified visual representation outlining the layout and
structure for creating a new cab category. Wireframes focus on the arrangement of elements
without including detailed design aspects. This wireframe serves as a visual guide for the
"Add New Category" page, allowing designers and stakeholders to visualize the structure
and layout before detailed design work begins.

Figure 33: Admin cab category (add new category)

Operator dashboard

A wireframe for the Operator Dashboard in "The City Taxi" transport service, targeting
low to mid-income passengers, is a simplified visual representation outlining the layout and
structure of the interface where operators can manage and oversee the taxi service
operations. Wireframes focus on the arrangement of elements without including detailed
design aspects. This wireframe serves as a visual guide for the Operator Dashboard,
enabling designers and stakeholders to visualize the structure and layout before detailed
design work begins.

Figure 34: Operator dashboard

Operator taxi reservation form

A wireframe for the Operator Taxi Reservation Form in "The City Taxi" transport service
is a simplified visual representation outlining the layout and structure of the interface where
operators can manage taxi reservations initiated by customers. Wireframes focus on the
arrangement of elements without including detailed design aspects. This wireframe serves
as a visual guide for the Operator Taxi Reservation Form, enabling designers and
stakeholders to visualize the structure and layout before detailed design work begins.

Figure 35: Operator taxi reservation form

Interface

Home
The page shows a front displays and about us and carries user & admin to login

Figure 36: Homepage

Service
The page which is shows about system details and contacts.

Figure 37: Service page

Contact page
The contact helps to be connected to the system and new customer get to know more about
City taxi.

Figure 38: Contact page

Customer login

For new customers registration here we designed a form for collect details

Figure 39: Customer login

Customer register
New customer register into the system for the more flexibility.

Figure 40: Customer register

Customer dashboard
The customer dashboard, where it contain all the information of the specific customer with
their booking, reservation and rating the driver after each ride.

Figure 41: Customer dashboard

Customer booking
Customer booking form is where the passenger can hire taxi driver for their ride

Figure 42: Customer booking

Customer Hire Cab

Customer hire taxi with the pickup and drop location and with the date of the ride as well.

Figure 43: Customer Hire Cab

Customer see booking
Customer have the access to view at their booking list so far.

Figure 44: Customer see booking

Customer reservation
If customer want to reserve cab for their upcoming event, can visit to the reservation form
to reserve the Cab.

Figure 45: Customer Reservation

Customer rate the driver
After the ride the customer can give rating for the driver with the option of poor to excellent.

Figure 46: Customer rate Driver form

Customer see reservation

Customer can view at their overall reservation with the status of accepted, pending and
cancelled.

Figure 47: Customer view reservation

Customer rate driver
Customer have to option to give rating for the driver, even after days of the ride.

Figure 48: Customer rate driver

Admin login
Admin login form with the username and password

Figure 49: Admin login form

Admin dashboard

Admin can view at the dashboard after entering the correct username and password.

Figure 50: Admin dashboard

Admin manage cab category

Admin manage the cab category with the status of the active or inactive.

Figure 51: Admin manage the cab category

Admin manage cab category (Add new customer)

Admin can add new category after clicking the button of “ADD NEW CATEGORY”

Figure 52: Admin manage cab category (Add new customer)

Admin manage cab

Admin have the access to manage the cab where it contain the details of the driver and taxi
details.

Figure 53: Admin manage cab

Admin manage cab (Add new cab)

Admin have the access to manage the cab, like adding a new cab details into the system.

Figure 54: Admin manage cab (Add new cab)

Admin manage location

Admin manage the location details that customer select for their ride

Figure 55: Admin manage location

Admin manage location (Add new location)
Admin can add new location by click on the button of “ADD NEW LOCATION”.

Figure 56: Admin manage location (Add new location)

Admin view reservation

Admin can view at the reservation list with the customer details, location and assigned
driver.

Figure 57: Admin view reservation

Admin view booking

Admin have the access to view at the booking list with the customer details and the status
of pending, accepted or cancelled.

Figure 58: Admin view booking

Admin registered customer

Admin register customer with their personal details.

Figure 59: Admin registered customer

Admin manage users
Admin the manage the users with the personal details

Figure 60: Admin manage users

Admin manage users (Add new users)

Admin can add new user for the system, by clicking on the button”ADD NEW
CUSTOMER”.

Figure 61: Admin manage users (Add new users)

Admin booking report

Admin will manage the report of booking, by giving on the data of pickup and drop, can
view at the report.

Figure 62: Admin booking report

Admin booking report

After giving the date of pickup and drop, admin can view at the overall booking report.

Figure 63: Admin booking report

Admin reservation report
Admin will manage the report of reservation, by giving on the data of pickup and drop, can
view at the report.

Figure 64: Admin reservation report

Admin reservation report

After giving the date of pickup and drop, admin can view at the overall reservation report.

Figure 65: Admin reservation report

Operator Login
Operator login form with the username and password

Figure 66: Admin reservation report

Operator dashboard

After entering the correct username and password, operator get access to the dashboard

Figure 67: Operator dashboard

Operator reserve taxi

Operator reserve the task for the customer

Figure 68: Operator reserve taxi

Operator reserve a vehicle

Operator get access to this from by clicking on to the button of reserve a vehicle in the
reserve a taxi form.

Figure 69: Operator reserve a vehicle

Operator see available driver

The operator can view at the available driver with the status of active of available and
inactive means busy.

Figure 70: Operator see available driver

Driver Login form

Driver login form with the username and password

Figure 71: Driver login form

Driver dashboard
Driver get access for the dashboard after entering the correct username and password

Figure 72: Driver dashboard

Driver Booking
Driver receive the booking from the operator with the customer details of pickup and drop
location.

Figure 73: Driver booking

Driver managing Status
Driver managing the status by “BUSY” and “AVALIABLE”.

Figure 74: Driver managing Status

Function of the system

Add a new category in the Admin form

Figure 75: Add a new category in the Admin form

Admin adding a new category of cab in the cab category form by clicking on “ADD NEW
CATEGORY”.
Delete a cab category in the admin form

Figure 76: Delete a cab category in the admin form

Deleting an unwanted category details from the cab category from by clicking the button
on delete.

Customer Hiring a Cab

Figure 77: Customer hiring a cab

Customer book a cab by entering the pickup and drop location, and the date and time of
pickup.
Implementing the system

 Customer Booking a CAB:

Customer can hire the cab by inserting the pickup and drop location, and selecting
the cab in their preference.
 Login Process:
There are four type of users who has the login form, they are admin, operator,
customer and driver. The users give out the username and password, then only they
can be logged in. The username and password given by the admin, customer, driver
and operator are being checked from the database that stored all the data.
 Admin process:
Admin have the fully access of the system, can manage the customer, payment, cab,
location, and reservation. Admin can insert details of the cab, customer and cab
category.
 Operator process:
The operator in charge of the reservation, if unregistered contact the operation and
book a taxi, operator will manage the operation.
 Driver process:
Driver will receive the customer with their pickup location and drop them to the
dropping location. Driver will receive payment.
 Customer process:
Registered customer book through online, where the hire a diver is available in the
system. if unregistered customer contact the operator to book a cab for them.
Implementation code

Customer Login

Figure 78: Customer login code

Insert Cab code

Figure 79: Insert cab code 1

 Figure 81: Insert cab code 2

Insert cab category code

Figure 80: Insert cab category code

Insert booking code

Figure 82: Insert booking code

Insert Reservation code

Figure 83: Insert reservation code

Collaboration tools

Team collaboration tools are a set of technologies that enable one-on-one and group
communication through real-time messaging, group chat, file sharing, shared calendaring,
project coordination, and voice and video. These tools can be centrally managed in
enterprise environments, which simplifies administrative tasks (techtarget, 2023).

Trello

Trello is a popular project management tool that makes it simple to create and manage
tasks, whether they are for a team project or just an own personal list of chores. It's simple
to set deadlines, make notes on projects and tasks, and assign tasks to other project
collaborators. Trello uses a kanban board view to help to see how the project is progressing.

Trello is used a collaborating tools as the project goes on. The team member used the trello
to check on the pending work and completed one. It helps to stay up-to-date with the project
and helps to keep track on the pending works.

Figure 84: Collaboration tools

Critical assessment

The City Taxi web based system, was prepared by the three person, shobikah, vivekan and
chathuragani. The programmer for the system is Mr.Vivekan, who have done his part
perfectly by implementing the code that have been design by Miss.Shobikah and
Miss.Chathuragani. Without the support of each other; it will be impossible to complete the
system on time. The leader for the project is Mr.Vivekan, who played a major role in
completing the system by working on with the implementation and database. That language
used to implement the system is PHP (Hypertext Preprocessor), the server is XAMPP
server. Therefore, our team work closely together to give the best of the project and with
the contribution of each other made this project successful.

The team member:

[email protected]

[email protected]

[email protected]

Team confirmation

Table 1: Team Confirmation

Team Member Name Signature of Team members

Shobikah Karthigaiselvan [email protected]

Rasakumar vivekan [email protected]

Puwaneshwaram Chathurangani [email protected]

Component clarification
Table 2: Component 1

Component 1 Interfacing designing

Description Frontend/ backend interface designing

Component developer Mr. Rasakumar Vivekan

Evidence of system

Table 3: Component 2

Component 2 Database development

Description Database designing

Component Miss. Shobikah karthigaiselvan

developer
Evidence of
system

Table 4: Component 3

Component 3 Back end code

Description Coding development

Component Vivekan
developer

Evidence of
system
 Table 5: Component 4

Component 4 Testing

Description Testing and maintenance

Component Miss. Chathurangani

developer

Evidence of
system
Test plan for City Taxi
Table 6: Test plan

Test Data
City Taxi Test Duration 5 Hours
Plan

No of Test
Test Run
Vivekan, Shobikah, Chathurangani 16
by plan

Test Plan Test Plan Test Test Test Run

Number Description Input Condition Expectation By

Empty the Pop up

Username :
Empty text test field and message’Username
01 Vivekan
field submit the and Password are
Password :
button required’

Username Username Input the test

Pop up
correct :Admin2 input and
02 message’Password Vivekan
password click the
incorrect ’
incorrect Password :2564 login button

Username Username Input the test

Pop up
incorrect :admin input and
03 message’Admin Vivekan
password click the
not found ’
correct Password :12345 login button

Username Username Input the test

Pop up
and :Admin2 input and
04 message’Login Vivekan
password click the
successfull ’
correct Password :12345 login button
 Category name :7
seater
Input the
Insert Cab Pop up message
Descroption: a 7 details and
05 category “successfully Vivekan
seater vehicle click the
details added”
with a AC facility save button

Status : active

Select the
Delete Cab Pop up message
Delete the Cab delete details
06 category “Delete Vivekan
category details and click the
details successfully”
delete button

Location id :122 Input the test Pop up

Insert new input and message’location
07 Shobikah
location Location name: click the added
Atchuvely save button successfully’

Username :john Pop up

Input the test
message’operator
Insert new Password input and
08 record saved’ Shobikah
user :147963 click the
save button
Type : operator

Username :white Input the test Pop up

Insert new input and message’admin
09 Password :12345 Shobikah
user click the save record saved’

Type : admin button

Unregistered Input the Pop up

Add Customer Name: pickup and “Reservation

10 sarah drop location added” Shobikah
Reservation with date and
Pickup: Colombo
time
 Drop: kalutara

Type: Customer

Pickup: Colombo Input the Pop up

pickup and “Successfully
Drop: kalutara
drop location booking”
Insert
11 Date& Time: with date and Chathurangani
Booking time
29/02/2024,
12:12 a.m

Type: Customer

Rate: Good Input rate: Pop up

Good and “Successfully
Type: Customer
12 Rate Driver click the Rated” Chathurangani
submit
button

Click the change Click the Pop up “Do you

Change
status button change status want to change to
13 status to Chathurangani
button ON RIDE”
“BUSY” Type: Driver

Click the change Click the Pop up “Do you

Change
to status button change status want to change to Chathurangani
14 status
button Compete”
complete Type: Driver

Change Click the change Click the Pop up “Are you

status to status button change status sure, you want to
15 Chathurangani
Active from button change the status?”
Type: Driver
inactive
 Change Click the change Click the Pop up “Are you
status to status button change status sure, you want to
16 Chathurangani
Inactive button change the status?”
Type: Driver
from Active

Test Case for City Taxi

Table 7: Test case 1

Test Plan 01 Test Case Admin Login

No Description

Test Case Vivekan No of test case 16

Run

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

01 Empty text field Username Empty the Pop up Pop up

: test field message’Use message’Usernam
and submit rname and e and Password
Password :
the button Password are are required’
required’

Evidence
 Table 8: Test case 2

Test Plan 02 Test Case Login

No Description

Test Case Vivekan No of test case 16

Run

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

02 Username correct Username Input the Pop up

Pop up
password incorrect :Admin2 test input message’Passwor
message’Pass
and click d incorrect ’
word
Password the login
incorrect ’
:2564 button

Evidence
 Table 9: Test case 3

Test Plan 03 Test Case Login

No Description

Test Case Vivekan No of test case 16

Run

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

03 Username incorrect Username Input the Pop up Pop up

password correct :admin test input message’Ad message’Admin
and click min not found not found ’
Password
the login ’
:12345
button

Evidence
 Table 10: Test case 4

Test Plan 04 Test Case Login

No Description

Test Case Vivekan No of test case 16

Run

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

04 Username and Username Input the Pop up Pop up

password correct :Admin2 test input message’Log message’Login
and click in successfull successfull ’ and
Password
the login ’ and display display dashboard
:12345
button dashboard

Evidence
 Table 11: Test case 5

Test Plan 05 Test Case Insert Function

No Description

Test Case Run Vivekan No of test case 16

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

05 Category name
:7 seater
Input the
Pop up
Insert Cab Descroption: 7 details and Pop up message
message
category seater vehicle click the “successfully
“successfully
details with a AC save added”
added”
facility button

Status : active

Evidence
 Table 12: Test case 6

Test Plan 06 Test Case Delete Function

No Description

Test Case Run Vivekan No of test case 16

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

06 Delete the Select the Pop up Pop up

Delete Cab Cab category delete details message message
category details and click the “Delete “Delete
details
delete button successfully” successfully”
Type: Admin

Evidence
 Table 13: Test case 7

Test Plan 07 Test Case Insert Function

No Description

Test Case Run Shobikah No of test case 16

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

07 Location id: Pop up Pop up

Input the
122 message’loca message’location
test input
Insert New tion added added
and click
location Location
successfully’ successfully’
the save
name:
button
Atchuvely

Evidence
 Table 14: Test case 8

Test Plan 08 Test Case Insert Function

No Description

Test Case Run Shobikah No of test case 16

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

08 Username Pop up Pop up

Input the
:john message’oper message’operator
test input
Insert New ator record record saved’
Password and click
user saved’
:147963 the save
button
Type : operator

Evidence
 Table 15: Test case 9

Test Plan 09 Test Case Insert Function

No Description

Test Case Run Shobikah No of test case 16

By

Test Case Test Case Test Test Test Actual Output

Number Description Input Condition Expectation

09 Username Pop up Pop up

Input the
:john message’oper message’operator
test input
Insert New ator record record saved’
Password and click
user saved’
:147963 the save
button
Type : operator

Evidence
 Table 16: Test case 10

Test Plan 10 Test Case Insert Function

No Description

Test Case Run Shobikah No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Descriptio Input Condition Expectatio
n n

10 Unregistered Input the Pop up Pop up

Customer Name: pickup and “Reservatio “Reservation
Add
sarahPickup: Colombo drop n added” added”
Reservatio
location
n Drop: kalutaraType:
with date
Customer
and time

Evidence
 Table 17: Test case 11

Test Plan 11 Test Case Insert Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

11 Pickup: Input the Pop up Pop up

ColomboDrop: pickup and “Successfull “Successfully
kalutaraDate& drop y booking” booking”
Time: location
Insert Booking
29/02/2024, 12:12 with date
a.m and time

Type: Customer

Evidence
 Table 18: Test case 12

Test Plan 12 Test Case Rate Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

12 Rate: Good Input rate: Pop up Pop up

Good and “Successfull “Successfully
Type: Customer
Rate the driver click the y Rated” Rated”
submit
button

Evidence
 Table 19: Test case 13

Test Plan 13 Test Case Status Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

13 Click the change Click the Pop up “Do Pop up “Do

Change status status button change you want to you want to
to “BUSY” status change to change to ON
Type: Driver
button ON RIDE” RIDE”

Evidence
 Table 20: Test case 14

Test Plan 14 Test Case Status Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

14 Click the change Click the Pop up “Do Pop up “Do

Change status status button change you want to you want to
to complete status change to change to
Type: Driver
button Compete” Compete”

Evidence
 Table 21: Test case 15

Test Plan 15 Test Case Status Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

15 Click the change Click the Pop up “Are Pop up “Are

Change status status button change you sure, you sure, you
to Active from status you want to want to
Type: Driver
inactive button change the change the
status?” status?”

Evidence
 Table 22: Test case 16

Test Plan 16 Test Case Status Function

No Description

Test Case Run Chathurangani No of test case 16

By

Test Case Test Case Test Test Test Actual

Output
Number Description Input Condition Expectatio
n

16 Click the change Click the Pop up “Are Pop up “Are

Change status status button change you sure, you sure, you
to Inactive status you want to want to
Type: Driver
from Active button change the change the
status?” status?”

Evidence
Future recommendation

Above given screenshots are the implemented web based system for City Taxi. For the
front end user is customer and the back end users are admin, operator and driver. The
current implement web based system will have more feature in the future to make the
customer have friendlier interface and way more easily to handle.

 Show location via GSP for the driver to located customer.

 After booking the customer will receive a sms with the driver image and phone
number.
 Vehicle track, after customer booking, will be able to check the track of hired taxi.
Reference

Unified modeling language (UML) diagrams (2017) GeeksforGeeks. Available at:

https://www.geeksforgeeks.org/unified-modeling-language-uml-introduction/
(Accessed: February 3, 2024).

Incremental model of software development life cycle – custom web & mobile
development company – new line technologies (2018) Newline.tech. Available at:
https://newline.tech/incremental-model-of-software-development-life-cycle/ (Accessed:
February 2, 2024).

Lecture 01 requirements engineering software engineering software engineering (no

date) Slidetodoc.com. Available at: https://slidetodoc.com/lecture-01-requirements-
engineering-software-engineering-software-engineering/ (Accessed: February 2, 2024).

UML diagrams: 14 types and templates (2020) Gliffy by Perforce. Perforce. Available at:
https://www.gliffy.com/blog/uml-2-5-diagram-types-and-templates (Accessed: February
3, 2024).

SDLC vs STLC: What’s the difference? [2024] (2024) InterviewBit. Available at:
https://www.interviewbit.com/blog/sdlc-vs-stlc/ (Accessed: February 1, 2024).

What is SDLC (no date) Sitesbay.com. Available at: https://www.sitesbay.com/software-

engineering/se-what-is-sdlc (Accessed: February 1, 2024).

No title (no date) Chartexamples.com. Available at:

https://chartexamples.com/pseudocode-to-flowchart-conversion/ (Accessed: February 1,
2024).

(No date) Researchgate.net. Available at: https://www.researchgate.net/figure/Flowchart-

of-the-control-method-proposed-to-compute-VCdRef-VCqRef-13-and-iqMRef-
18_fig2_317377559 (Accessed: February 2, 2024).
Froehlich, A. and Brush, K. (2023) What are Collaboration Tools? Definition, Types and
Benefits, Unified Communications. TechTarget. Available at:
https://www.techtarget.com/searchunifiedcommunications/definition/team-collaboration-
tools (Accessed: February 3, 2024).

Gunnell, M. (2021) What is trello, and how do you use it?, How-To Geek. Available at:
https://www.howtogeek.com/751448/what-is-trello-and-how-do-you-use-it/ (Accessed:
February 4, 2024).

Make your own flow chart algorithm and pseudocode (2016) studylib.net. Available at:
https://studylib.net/doc/7156871/make-your-own-flow-chart-algorithm-and-pseudocode
(Accessed: February 5, 2024).