TRIBHUVAN U NIVERSITY

Faculty of Institute of Science and Technology

ABC COLLEGE
KATHMANDU (NEPAL)

A Project Report On
“ONLINE RIDE SHARING SYSTEM”
For

System Analysis and Design (CSC315)

5th semester Project Report submitted in the partial fulfillment of the requirements for the degree of
Bachelor of Science in Computer Science and Information Technology

Under the supervision of

xyz

Submitted By:

Submitted to:
Department of Computer Science and Information Technology
CERTIFICATE OF APPROVAL
The undersigned certify that they have read and recommended to the respective
subject teacher and external teacher for acceptance, a project report entitled “ONLINE
RIDE SHARING SYSTEM” submitted by ............. for the partial fulfillment of the
requirement for the degree of Bachelor of Science in Computer Science and
Information Technology

….…………………………..

External Examiner

Tribhuvan University

……………………………..

............................

Supervisor

i
ACKNOWLEDGEMENT

Our project is based on a Online Ride Sharing System. An optimum effort has been
placed while preparing this documentation and presenting it in front of you. We would
like to thank each and every person who directly and indirectly helped in this project.
It’s our duty to place a sincere gratitude towards Nepalaya College and administration
team for imagining beautiful environment and enriching us with equipped facilities to
convert our imagination into reality. Furthermore, we would like to thank our
supervisor ............ and other mentors for helping us with each and every problem
related to this project work.

With respect,

...............

ii
 Table of Contents

CERTIFICATE OF APPROVAL ............................................................................ i

ACKNOWLEDGEMENT .................................................................................... ii

TABLE OF CONTENTS .......................................... Error! Bookmark not defined.

CHAPTER 1: INTRODUCTION .......................................................................... 1

1.1 Background ........................................................................................................................ 1
1.2 Problem Definition ............................................................................................................. 1
1.3 Objectives .......................................................................................................................... 2
1.4 Scope ................................................................................................................................. 2
1.5 Limitations ......................................................................................................................... 2

CHAPTER 2: SYSTEM ANALYSIS ...................................................................... 4

2.1 INTRODUCTION .................................................................................................................. 4
2.2 FUNCTIONAL REQUIREMENTS ............................................................................................. 4
2.3 NON-FUNCTIONAL REQUIREMENTS..................................................................................... 5
2.4 FEASIBILITY STUDY .............................................................................................................. 6

CHAPTER 3: SYSTEM SPECIFICATIONS ............................................................ 8

3.1 SERVER REQUIREMENTS (Minimum Requirements) ............................................................. 8

CHAPTER 4- MODULES AND THEIR DESCRIPTION ........................................... 9

4.1 MAJOR MODULES ............................................................................................................... 9
4.1.1 Customer Module ........................................................................................................ 9
4.1.2 Driver Module .............................................................................................................. 9
4.1.3 Administration Module ................................................................................................ 9
4.2 SYSTEM FLOW DIAGRAM .................................................................................................. 10
4.2.1: Data Flow Diagram ....................................................................................................... 10
4.2.2: ER Diagram ............................................................................................................... 10

CHAPTER 5: SYSTEM TESTING ...................................................................... 12

5.1 INTRODUCTION ................................................................................................................ 12
5.2 TESTING METHODOLOGIES ............................................................................................... 12
5.2.1 Unit testing: ............................................................................................................... 12

iii
 5.2.2 Integration testing:..................................................................................................... 12
5.2.3 System testing:........................................................................................................... 12
5.2.4 Performance testing: .................................................................................................. 13
5.2.5 User acceptance testing:............................................................................................. 13
5.2.6 Security testing: ......................................................................................................... 13

CHAPTER 6: SYSTEM IMPLEMENTATION ...................................................... 14

6.1 PURPOSE .......................................................................................................................... 14
6.2 SYSTEM MAINTENANCE .................................................................................................... 14

CHAPTER 7- CONCLUSION AND FUTURE ENHANCEMENT ............................. 16

7.1 CONCLUSION .................................................................................................................... 16
7.2 SCOPE FOR FUTURE DEVELOPMENT .................................................................................. 16

REFERENCES ................................................................................................ 17

APPENDIX .................................................................................................... 17

iv
 CHAPTER 1: INTRODUCTION

1.1 Background
The Online Ride Sharing System has emerged as a viable alternative to traditional
transportation methods. With the increasing concern over the impact of transportation on
the environment, as well as the rising cost of gasoline and other expenses associated with
driving, many people are turning to ride sharing as a cost-effective and eco-friendly way to
get around.

The idea of ride sharing is not a new one, but the emergence of Online Ride Sharing Systems
has made it easier than ever before to find and book rides with others. These system have
become increasingly popular in recent years, as they offer a convenient and affordable way
for individuals to travel without having to rely on public transportation or their own personal
vehicles.

1.2 Problem Definition

While Online Ride Sharing Systems have become increasingly popular in recent years, there
are several safety concerns that need to be addressed to ensure the safety of drivers and
passengers.

One of the main concerns is related to the screening process for drivers. Unlike traditional
taxi services, Online Ride Sharing Systems do not typically require extensive background
checks or training for drivers. This can leave passengers vulnerable to potential safety risks,
such as reckless driving or criminal behavior.

Another concern is related to the behavior of passengers. Some users of Online Ride Sharing
Systems have reported instances of passengers engaging in inappropriate or unsafe behavior
during rides, such as harassment or physical assault.

In addition, there is a risk of accidents or other incidents occurring during rides, which can
result in injuries or property damage. While many ride sharing platforms offer insurance
coverage for drivers and passengers, there is still a risk of liability and financial loss in the
event of an accident.

To address these safety concerns, it is important for Online Ride Sharing Systems to
implement strict safety standards and protocols for both drivers and passengers. This may
include more extensive background checks and driver training programs, as well as guidelines
for appropriate passenger behavior during rides.

In addition, it may be necessary to develop new technologies or systems to enhance the

safety of rides, such as advanced driver assistance systems or real-time monitoring of rides
for potential safety risks.

1
Overall, while Online Ride Sharing Systems offer many benefits, it is important to ensure that
these platforms are safe and secure for all users. By addressing these safety concerns, we can
help ensure that ride sharing remains a viable and safe alternative to traditional
transportation methods.

1.3 Objectives
The objective of this project is to identify and address the key challenges facing Online Ride Sharing
Systems, with a focus on improving the user experience and safety of these platforms.

To achieve this objective, the project will focus on the following goals:

• Enhancing the screening process for drivers

• Developing new safety technologies and systems
• Implementing strict safety standards and protocols
• Enhancing the user experience
By achieving these goals, the project aims to make Online Ride Sharing Systems a more viable and
safer alternative to traditional transportation methods, while also improving the overall user
experience for all users.
1.4 Scope
The scope of this project includes the implementation and evaluation of safety standards and user
experience improvements in Online Ride Sharing Systems.
This project will focus on addressing the safety concerns associated with Online Ride Sharing
Systems, such as driver screening, passenger behavior, and accidents or incidents during rides. The
project will also aim to enhance the overall user experience of these platforms, by improving the
ease of use, reliability of ride information, and user convenience.
To achieve these goals, the project will involve the following activities:
• Review of existing Online Ride Sharing Systems
• Development of safety standards and protocols
• Implementation of safety standards and protocols
• Development of user experience improvements
• Evaluation of safety and user experience improvements

1.5 Limitations
• Just, individuals who are familiar with standard utilization of mobiles or PCs can work
this software.
• With huge flow in traffic the application is prone to performance issues.
• Pre-built queue management systems may not offer the customization needed for
some businesses

2
 • Implementing a queue management system can be expensive, especially for small
businesses
• Queue management systems may not be able to handle sudden increases in demand
or unexpected fluctuations in customer flow.

Here are some limitations of Online Ride Sharing System:

• Regulatory constraints: Online Ride Sharing Systems are subject to various legal and
regulatory constraints, which may limit the ability to implement certain safety standards
and user experience improvements.
• Platform provider cooperation: The implementation of safety standards and user
experience improvements in Online Ride Sharing Systems may require the cooperation of
platform providers, who may have competing priorities or may be resistant to change.
• User behavior: The safety of Online Ride Sharing Systems also depends on the behavior of
users, including both drivers and passengers. Despite the implementation of safety
standards and protocols, some users may engage in risky behavior or violate these
standards, which could compromise the safety of rides.
• Technology limitations: The implementation of new safety technologies in Online Ride
Sharing Systems may be limited by the availability or affordability of these technologies.
Additionally, some technologies may require significant investment or training to
implement effectively.
• Privacy concerns: The implementation of certain safety standards, such as real-time
monitoring of rides, may raise privacy concerns for users. Platform providers may need to
balance the benefits of enhanced safety with the privacy concerns of users.
• Geographic limitations: The implementation of safety standards and user experience
improvements may also be limited by geographic factors, such as the availability of
infrastructure or the prevalence of certain types of accidents or incidents.
• Cost limitations: The implementation of safety standards and user experience
improvements may require significant investment, which may be a challenge for smaller
platform providers or those operating in highly competitive markets.

3
 CHAPTER 2: SYSTEM ANALYSIS

2.1 INTRODUCTION
System analysis is conducted for the purpose of studying a system or its parts in order to
identify its objectives. It is a problem-solving technique that improves the system and ensures
that all the components of the system work efficiently to get their result.

The various tasks in the system analysis include the following:

• Requirement gathering: Gathering requirements from stakeholders, including drivers,

passengers, and platform providers, to understand their needs and expectations from
the system.
• Functional analysis: Identifying the functions and features required for the system to
meet the requirements gathered during the requirement gathering phase.
• Data analysis: Analyzing the data required for the system, such as user information,
ride history, and payment information.
• Process modeling: Creating process models to understand how the system works,
including how users request and accept rides, how drivers are matched with
passengers, and how payments are processed.
• Use case analysis: Identifying and analyzing the use cases of the system, including
scenarios such as passenger requesting a ride, driver accepting a ride, and payment
processing.
• Performance analysis: Evaluating the performance of the system, including its
response time, reliability, and scalability.
• Security analysis: Analyzing the security of the system, including its vulnerability to
hacking, data breaches, and other security threats.
• User interface analysis: Evaluating the usability of the system's user interfaces,
including the mobile applications used by both drivers and passengers.
• Testing: Conducting testing to identify and resolve any bugs or issues with the system's
functionality.

2.2 FUNCTIONAL REQUIREMENTS

Functional requirements are a key aspect of system analysis, defining the features and capabilities
required for the system to meet the needs of its users. For an Online Ride Sharing System, the
following functional requirements may be necessary:
• User registration and authentication: The system must allow users to create accounts,
providing basic information such as name, email, and phone number. The system must also
authenticate users to ensure that only authorized users can access the system.
• Ride request and acceptance: The system must allow passengers to request rides and
drivers to accept rides. The system must match passengers with available drivers and
provide information on the driver's location, estimated time of arrival, and vehicle details.
4
 • Payment processing: The system must process payments for rides, allowing passengers to
pay for rides using various payment methods, such as credit cards or digital wallets. The
system must also handle payment disputes and issue refunds when necessary.
• Driver and passenger ratings: The system must allow drivers and passengers to rate each
other, providing feedback on the quality of the ride and the behavior of the driver or
passenger.
• Driver and vehicle verification: The system must verify the identity of drivers and ensure
that their vehicles meet the necessary safety standards. This may include verifying the
driver's license, conducting background checks, and checking the vehicle's insurance and
registration.
• Real-time tracking and monitoring: The system must track and monitor rides in real-time,
providing updates on the ride's progress and location. The system must also be able to
detect any safety or security issues, such as accidents or suspicious behavior.
• Customer support: The system must provide customer support to users, allowing them to
report any issues or problems with the system, such as payment disputes or safety
concerns.

2.3 NON-FUNCTIONAL REQUIREMENTS

They are the quality requirements that stipulate how well web application does what it has
to do:

• Performance: The system must be able to handle a large volume of ride requests and
payments, processing them quickly and efficiently. The system must also be able to
handle high traffic and user loads, without slowing down or crashing.
• Availability: The system must be available 24/7, with minimal downtime or
disruptions. This is important for ensuring that users can access the system when they
need to, without any delays or interruptions.
• Reliability: The system must be reliable, with minimal errors or bugs. The system
should also be able to recover from any errors or failures quickly and automatically,
without causing any significant disruptions or downtime.
• Security: The system must be secure, protecting user information and payment data
from unauthorized access or breaches. This may include implementing encryption,
firewalls, and other security measures to prevent hacking and other attacks.
• Usability: The system must be easy to use, with a user-friendly interface that is easy
to navigate and understand. This is important for ensuring that users can use the
system effectively, without any confusion or frustration.
• Compatibility: The system must be compatible with various devices and operating
systems, allowing users to access the system from their preferred devices, such as
smartphones, tablets, and laptops.
• Scalability: The system must be scalable, able to handle an increasing number of users
and rides as the system grows. This is important for ensuring that the system can
continue to meet user needs and demands, even as the user base expands.

5
2.4 FEASIBILITY STUDY
It is necessary and prudent to evaluate the feasibility of a project at the earliest possible time.
There may be different ways of checking whether a system is feasible or not. The following
feasibility studies were performed to gauge the feasibility of the system.

• Operational Feasibility:
In this test, the operational scope of the system is checked. The system under
consideration should have enough operational reach. It is observed that the proposed
system is very user friendly and since the system is built with enough help, even
persons with little knowledge of windows can find the system very easy.

• Technical Feasibility:
This test includes a study of function, performance and constraints that may affect the
ability to achieve an acceptable system. This test begins with an assessment of the
technical viability of the proposed system. One of the main fusers to be accessed is
the need of various kinds of resources for the successful implementation for the
proposed system.

• Economic Feasibility:
An evaluation of development cost weighed against the ultimate income or benefit
derived from the development of the proposed system is made. The income can be in
terms of money or goodwill, since the software brings in both, the system is highly
viable.

2.5 Gantt Chart:

Task Description Start Date End Date Duration

Project Planning 01/01/2023 01/15/2023 15 days

Requirements Gathering 01/16/2023 02/05/2023 21 days

System Design 02/06/2023 02/25/2023 20 days

Front-End Development 02/26/2023 03/25/2023 28 days

Back-End Development 03/26/2023 04/25/2023 30 days

Testing and Bug Fixing 04/26/2023 05/20/2023 25 days

Deployment and Launch 05/21/2023 06/01/2023 12 days

Post-Launch Maintenance 06/02/2023 06/30/2023 29 days

Explanation:

6
 • Project Planning: During this phase, the project team will establish project goals, define
project scope, identify stakeholders, and develop a project plan.
• Requirements Gathering: During this phase, the project team will gather and document the
functional and non-functional requirements for the Online Ride Sharing System.
• System Design: During this phase, the project team will develop the system architecture,
design database schemas, and create wireframes and mockups of the user interface.
• Front-End Development: During this phase, the project team will develop the front-end
components of the system, including the user interface and user experience design.
• Back-End Development: During this phase, the project team will develop the back-end
components of the system, including the database schemas, API endpoints, and business
logic.
• Testing and Bug Fixing: During this phase, the project team will conduct system testing to
identify and resolve any bugs or issues.
• Deployment and Launch: During this phase, the project team will deploy the system to a
production environment and launch it to the public.
• Post-Launch Maintenance: During this phase, the project team will provide ongoing
maintenance and support for the system, including bug fixes, security updates, and feature
enhancements.

2.6 Decision Table

Condition Action 1 Action 2 Action 3

User is logged in Allow ride View ride history Logout

User has payment info Allow ride Prompt to add View payment info

Ride is in progress View details Contact driver End ride

Ride is completed View receipt Rate driver Book another ride

In this decision table, the conditions are listed in the left-hand column, and the possible actions are
listed in the header row. Each cell in the table represents a specific combination of conditions and
actions, and the corresponding action(s) to take based on those conditions.
For example, if a user is logged in and has payment information, they are allowed to request a
ride. If the ride is in progress, they can view the details, contact the driver, or end the ride. If the
ride is completed, they can view the receipt, rate the driver, or book another ride.
Using a decision table like this can help ensure that all possible combinations of conditions and
actions are considered and accounted for in the design and development of the Online Ride
Sharing System.

7
 CHAPTER 3: SYSTEM SPECIFICATIONS

3.1 SERVER REQUIREMENTS (Minimum Requirements)

• PHP >= 8.0

• BCMath PHP Extension
• Ctype PHP Extension
• Fileinfo PHP extension
• JSON PHP Extension
• Mbstring PHP Extension
• OpenSSL PHP Extension
• PDO PHP Extension
• Tokenizer PHP Extension
• XML PHP Extension

3.2 DEVELOPMENT TOOLS USED

• Operating System: Windows 10
• Text Editor: Visual Studio 2023
• Framework: Bootstrap
• Front-End Language: HTML, CSS
• Back-End: PHP
• Back-End Connectivity: MySQL

8
 CHAPTER 4- MODULES AND THEIR DESCRIPTION

4.1 MAJOR MODULES

4.1.1 Customer Module

This module provides functionalities for customers. Customers can register to get service and
get information about scheduling of queue.

The customer module is a crucial component of an Online Ride Sharing System, as it allows
users to interact with the system and access the services it provides. The customer module
typically includes the following features:

• User registration
• Search and booking
• Payment processing
• Notifications and alerts
• User feedback and reviews
• Customer support

By implementing a robust customer module, the Online Ride Sharing System can provide
users with a seamless and user-friendly experience, leading to increased customer
satisfaction and loyalty.

4.1.2 Driver Module

The driver module is an essential part of any Online Ride Sharing System, as it allows drivers to
create and manage trips. Here are some potential features of a driver module:
• Trip Creation
• Trip Management
• Booking Management
• Payment Management
• Review Management

4.1.3 Administration Module

The administrative module is an important component of an Online Ride Sharing System, as it
allows administrators to manage the system and its operations. The administrative module
typically includes the following features:
• Dashboard
• User management
• Vehicle management
• Booking management
• Payment management
9
 • System configuration
• Reporting and analytics
By implementing a robust administrative module, the Online Ride Sharing System can be efficiently
managed and maintained, leading to increased operational efficiency and revenue generation.
This module provides administrator related functionalities. Administrator manages entire
application and maintains the profiles of customers. Administrator module having all
privileges about this entire Queue, he/she can give a token to the customers according to the
time they register in the system.

4.2 SYSTEM FLOW DIAGRAM

4.2.1: Data Flow Diagram

4.2.2: ER Diagram

10
11
 CHAPTER 5: SYSTEM TESTING

5.1 INTRODUCTION
Once source code has been generated, software must be tested to uncover (and correct) as
many errors as possible before delivery to customer. Our goal is to design a series of test
cases that have a high likelihood of finding errors. To uncover the errors software techniques
are used. These techniques provide systematic guidance for designing test that
1. Exercise the internal logic of software components, and
2. Exercise the input and output domains of the program to uncover errors in program
function, behavior and performance.

5.1.1 Steps Software is tested from two different perspectives:

1. Internal program logic is exercised using ―White box ‖ test case design Techniques.

2. Software requirements are exercised using ―block box ‖ test case Design techniques. In
both cases, the intent is to find the maximum number of errors with the minimum amount
of effort and time.

5.2 TESTING METHODOLOGIES

A strategy for software testing must accommodate low-level tests that are necessary to verify
that a small source code segment has been correctly implemented as well as high-level tests
that validate major system functions against customer requirements. A strategy must
provide guidance for the practitioner and a set of milestones for the manager. Because the
steps of the test strategy occur at a time when deadline pressure begins to rise, progress
must be measurable and problems must surface as early as possible. Following testing
techniques are well known and the same strategy is adopted during this project testing.

5.2.1 Unit testing:

This involves testing individual units or components of the system to ensure that they work as
intended. Unit testing is typically done by developers during the development process.

5.2.2 Integration testing:

This involves testing how the different components of the system work together. Integration
testing is done to ensure that the different modules and subsystems of the system can work
together seamlessly.

5.2.3 System testing:

This involves testing the entire system to ensure that it meets the specified requirements. System
testing is done to ensure that the system is complete and functions as expected.

12
5.2.4 Performance testing:
This involves testing the performance of the system under different conditions, such as high user
loads or peak usage times. Performance testing is done to ensure that the system can handle the
expected workload and provide optimal performance.

5.2.5 User acceptance testing:

This involves testing the system with actual users to ensure that it meets their needs and
expectations. User acceptance testing is done to ensure that the system is user-friendly and
provides a positive user experience.

5.2.6 Security testing:

This involves testing the security of the system to identify potential vulnerabilities or weaknesses.
Security testing is done to ensure that the system is secure and user data is protected.

13
 CHAPTER 6: SYSTEM IMPLEMENTATION

6.1 PURPOSE
System implementation is the important stage of project when the theoretical design is tuned
into practical system. The main stages in the implementation are as follows:
• Planning
• Training
• System testing and
• Changeover Planning
Planning is the first task in the system implementation. At the time of implementation of any
system people from different departments and system analysis involve. They are confirmed
to practical problem of controlling various activities of people outside their own data
processing departments.
The line managers controlled through an implementation coordinating committee. The
committee considers ideas, problems and complaints of user department, it must also
consider:
• The implication of system environment
• Self-selection and allocation for implementation tasks
• Consultation with unions and resources available
• Standby facilities and channels of communication

6.2 SYSTEM MAINTENANCE

System maintenance is a crucial aspect of any project, including an Online Ride Sharing System. To
ensure the long-term success and sustainability of the system, it is important to establish a
comprehensive maintenance plan that includes the following:
• Regular system updates: The system should be updated regularly to ensure that it remains
up-to-date and functions smoothly. Updates may include bug fixes, security patches, and
new features.
• Data backup and recovery: The system should have a robust backup and recovery plan in
place to ensure that user data is protected and can be recovered in the event of a system
failure or other disaster.
• Monitoring and performance optimization: The system should be monitored regularly to
identify any performance issues or potential problems. This may involve analyzing system
logs, user feedback, and other data to identify areas for improvement.
• Technical support and user assistance: The system should have a dedicated technical
support team in place to assist users with any issues they may encounter. This may involve
providing online or phone support, as well as creating user guides or tutorials.
• Compliance with regulations: The system should comply with all relevant regulations and
standards, such as data protection laws and industry standards.

14
By implementing a comprehensive system maintenance plan, the Online Ride Sharing System can
remain functional and efficient, provide a positive user experience, and comply with regulations
and standards.

15
 CHAPTER 7- CONCLUSION AND FUTURE ENHANCEMENT

7.1 CONCLUSION
In conclusion, the development of an Online Ride Sharing System can provide a practical and
innovative solution to address the growing demand for transportation services. This project
involved a comprehensive analysis of the requirements, feasibility, and limitations of
developing an Online Ride Sharing System.
The project highlighted the importance of conducting a feasibility study to assess the
practicality and viability of the system, identifying functional and non-functional
requirements, and addressing potential challenges and risks. By addressing these factors, the
project team was able to create a detailed and comprehensive plan for the development of
an Online Ride Sharing System.
Overall, the development of an Online Ride Sharing System can provide numerous benefits,
including reducing traffic congestion, lowering transportation costs, and improving access to
transportation for underserved communities. The success of this project will ultimately
depend on the effective implementation of the system, which must ensure the security,
privacy, and reliability of user data and transactions.
In conclusion, the development of an Online Ride Sharing System can contribute to a more
sustainable and efficient transportation system, and has the potential to revolutionize the
way people commute and travel.

7.2 SCOPE FOR FUTURE DEVELOPMENT

Based on the analysis and planning conducted in this project, there is significant potential for
future development of an Online Ride Sharing System. The project team has identified the key
requirements and limitations for developing such a system, as well as the potential benefits and
challenges.
To further develop the system, it is recommended that the project team focuses on the following
areas:
• User experience
• Technology and data analysis
• Security and privacy
• Partnerships and collaborations
Overall, the future development of an Online Ride Sharing System has the potential to
revolutionize the transportation industry and provide numerous benefits to both drivers and
passengers. By addressing the key areas identified in this project, the system can be further
optimized to meet the evolving needs and expectations of users.

16
 REFERENCES

1. [1] J. Connallen, Building Web Applications, Pearson Education

Inc.. [2]https://www.geeksforgeeks.com
2. [3]R. A. Maier M., The Art of System's Architecting, CRC Press.
3. [4]https://www.gopinoy.com
4. [5]https://www.studytonight.com

APPENDIX

Screenshots:

17