RIDE CONNECT

Synopsis of project

BACHELOR OF TECHNOLOGY

COMPUTER SCIENCE AND ENGINEERING

SUBMITTED BY SUBMITTED TO

SHASHANK AWASTHI PROF. ATUL MATHUR

(Rollno.- 1842910023)

TANMAY TIWARI
(Rollno.- 1842910027)

PRAGATI GAUTAM

(Rollno.- 1842910018)

Naraina Vidya Peeth Engineering & Management Institute

Session – 2021-22
 ACKNOWLEDGEMENT
First I would like to thanks for giving this opportunity for this project .
I would like to thanks Mr. Atul Mathur (Head Of Department) ,and also coordinator of our
project who support us in our project with his suggestion and experiences.
I also like to thanks Ms. Shruti ma’am for his suggestions in your projects.
I would like to thanks Dr. Akash Awasthi (Director) who push our ideas for implementation
and give her support to us.
It is indeed with a great sense of pleasure and immense sense of gratitude that I acknowledge the
help of these individuals.
My thanks and appreciations also go to my classmates for helping us to developing the project
and to the people who have willingly helped me out with their abilities.
 Index

 Introduction………………………………………………….01.
 What is ride connect.
 Blockchain.
 Analysis……………………………………………………...03.
 Requirement of Project.
 Literature Review……………………………………………04.

 System requirement………………………………………….05.
 Software requirements.
 Hardware requirements.
 Design of Project…………………………………………….06.
 Working of Project…………………………………………..10.
 Feasibility Study……………………………………………..12.
 Abstract……………………………………………………....13.
 Conclusion…………………………………………………....14.
 INTRODUCTION

Ride connect is an Android App in which is an arrangement in which drivers usually have
privately owned vehicles who wish to offer rides and passengers who wish to obtain rides. In
this use a network (such as one accessed through an app) to coordinate the sharing of individual
automobile trips for which the passengers pay a fare.
RideConnect is a ridesharing platform for communities, groups, families, events andcompanies.
RideConnect solves the problem of trust and affordability by giving you control to create your
own community of drivers and riders so that you can ask people for a ride, or offer them one.
This app lets user and driver ,if driver have the closest current locationand destination by taking
ride. A user who vehicle and is about to start a journey firstmarks its status as “I can share a
ride” and then enters its destination in the app before starting the journey. A person who wants
to travel but is not having conveyance requests the app for a lift by providing his/her destination.
The app calculates three things:

1. Requesting user’s current distance from the current distances of all the users who have
marked their status as “I can share a ride”.
2. The distance of destination of the requesting user from the destinations of all the users
who have marked their status as “I can share a ride”.
3. Finally, the app adds up the current location distance and destination distance for each
user whose status is “I can share a ride” from the requesting user.

functional Requirements

1. A user must be able to register in the app.

2. A user can mark its status as “I can share a ride” and set its destination on the map before
starting its journey.
3. A user can request a ride and provide its destination on the map.
4. Once a user requests a ride, the app calculates the following things:
5. Requesting user’s current distance from the current distances of all the users who have
marked their status as “I can share a ride”.
6. The distance of destination of the requesting user from the destinations of all the users
who have marked their status as “I can share a ride”.
7. Finally, the app adds up the current location distance and destination distance for each
user whose status is “I can share a ride” from the requesting user. 1
 8. The user with the smallest sum is the selected user.
9. The app sends the message to the selected user “You have a ride request” and displays
the current location of the requesting user on the map.
10. A user who has marked its status as “I can share a ride” can mark its status as “I cannot
share a ride” after the journey ends.

BLOCKCHAIN

Blockchain can connect drivers directly with riders via instant P2P protocol

Since we are using Blockchain enables riders via the decentralized network to
communicate directly with drivers. It minimizes the extra costs accrued due to the
presence of multiple intermediaries.
Blockchain can sign digital contracts and directly make transfers between parties

Ride is a Community-based Taxi Booking app built on Ethereum Blockchain which

allows drivers to bid on various nearby ride requests with an optimal amount within the
Ride recommended price range. Users can make payments with popular crypto tokens
which in turn gets swapped into stable tokens like DAI, TSUD (Driver ends).

Ethereum smart contract

A "smart contract" is simply a program that runs on the Ethereum blockchain. It's a
collection of code (its functions) and data (its state) that resides at a specific address on
the Ethereum blockchain.Smart contracts are a type of Ethereum account This means
they have a balance and they can send transactions over the network. they're not
controlled by a user, instead they are deployed to the network and run as programmed.
User accounts can then interact with a smart contract by submitting transactions that
execute a function defined on the smart contract. 

2
 ANALYSIS

REQUIREMENT OF PROJECT

The main idea of ridesharing apps is to organize a group of people going to the same place. And
the most convenient way is to connect drivers and riders via a mobile app.
Industry Challenges
Costly Payments due to Intermediaries
In the current scenario, when a passenger books a ride, an email first goes to the company, and
then it assigns a driver for a journey.

In this process, the service providers levy a 10-20 percent charge on the total fare. Consequently,
it proves costly for a customer while the driver also gets the payment after a commission
deduction. Indeed, extra costs arise from the presence of intermediaries between a driver and a
passenger.

Insufficient Transparency
Often, drivers fail how these firms work because of the lack of accountability in the existing,
centralized systems. You may also have come across a concern of peak pricing if you have ever
used a ride-sharing service. As a ride-sharing company involves numerous unknown roles, riders
and drivers alike do not get any explanation behind abrupt price spikes.

No Data Security and Privacy Mechanisms

One major challenge that companies face is ensuring the security and privacy of information
related to drivers and riders. Although organizations spend millions of dollars on user
authentication, cases of false identities are still growing daily.

3
 LITERATURE REVIEW

Blockchain technology has attracted a lot of research interest in the last few years. Originally,
their consensus algorithm was Hashcash, which is an instance of the so-called Proof-of-Work.
Nowadays, there are several competing consensus algorithms, not necessarily PoW. In this
paper, we propose an alternative proof of work algorithm which is based on the solution of
consecutive discrete logarithm problems over the point group of elliptic curves. At the same
time, we sketch a blockchain scheme, whose consensus is reached via our algorithm. In the
considered architecture, the curves are pseudorandomly determined by block creators, chosen to
be cryptographically secure and changed every epoch. Given the current state of the chain and a
prescribed set of transactions, the curve selection is fully rigid, therefore trust is needed neither
in miners nor in the scheme proposers.
The use of on-demand ride-sharing apps like Uber and Lyft is gaining considerable popularity
among daily commuters globally. The industry is ripe for opportunities. Instead of flag-down
taxis, customers are willing to pay on-demand ride-sharing providers for convenience and a
lower fee. Nonetheless, the industry is full of challenges too. For ride-sharing service providers,
identifying and addressing factors that attract passengers and make them lose interest are crucial.
With blockchain-based automotive solutions, stakeholders can develop a customer-centered
ride-sharing app that enables them to optimize customer-attracting features while addressing the
ones that force them to change a service provider.

4
 SYSTEM REQUIREMENT

Software Configurations

The software requirement specification can produce at the culmination of the analysis task. The
function and performance allocated to software as part of system engineering are refined by
established a complete information description, a detailed functional description, a
representation of system behavior, and indication of performance and design constrain,
appropriate validate criteria, and other information pertinent to requirements.

Software requirements:

Operating System: Windows.

Tools: Android studio.
Programming Language: Java.
API : Google map Api.
Database : firebase.
Blockchain: Ethereum smart contract (solidity).

Hardware Requirements:

Processor : Intel core i3.

Memory : 8GB RAM.
Hard Disk : 1TB.
 DESIGN OF PROJECT

ER-DIAGRAM

ER diagram used in Taxi App Backend Architectu


 User:
o User plays one out of two roles: Rider and Driver
o User is a Rider.
o User is a Driver.
 Rider:
o One Rider can add many new trip requests.
o One Rider can take many trips.
 Driver:
o One Driver can recieve many trip requests.
o One Driver has many trips to process.
 Trip:
o One Trip is taken by one Rider.
o One Trip has one Driver.

7
 LEVEL ZERO DFD (DATA FLOW DIAGRAM)

Booking
Management

Ride Payment
Management Management

Ride-
sharing system

System User
Customer Management
Management

Login Management

8
 DESIGN OF PROJECT

LEVEL ONE DFD

Login Check
To Roles of
Admin System Access

Manage Ride Details

Check Manage Booking Details

Forgot Manage
Credentials
Password modules

Manage Payment Details

Manage Insurance Details

Send
Email
To user Manage Membership Details

Manage Customer Profiles

Manage Report
Manage System Manage Roles of Manage User
Admins User Permission

Second Level DFD – Ride Sharing System

9
 WORKING OF PROJECT

In the working of project there are two section :

Customer section.
Driver section.

Customer section

Customer can have following feature-

1)Source and Destination box-in this section customer can give his/her source and destination
And this source and destination request send to driver.

2)List Driver Nearby -in this section customer get list of drivers which are nearby, and he/she
can accept any one requesthe/she can complete her journey.

3)Driver Review and Feedback-in this section customer give some reviews and feedback which
help us for different features like safe driver for women.by seeing customer reviews we can
select best driver for women.

4) Safe Drivers for Women –

5)Chat,Call Features to Driver-if anyone have any problem then he/she can call,chat to solve her
problem
Driver Section

If the user is Driver than he/she have his/her profile rating also the chat box for directly chat
with customer ( only if customer required) .
The driver also have their priority whether they want to give the services or not as there will be
button for that also if driver is already booked than driver can check the “booked” button .
driver is logged in, the app assigns them pickup requests from people nearby. The system metes
out feedback by tracking the proportion of pickups a driver accepts and averaging the rating that
passengers give their driver after a ride.
Drivers are highly motivated to keep their score up to avoid being cut off.
 10

Functional Requirements

1. A user must be able to register in the app.

2. A user can mark its status as “I can share a ride” and set its destination on the map before
starting its journey.
3. A user can request a ride and provide its destination on the map.
4. Once a user requests a ride, the app calculates the following things:
5. Requesting user’s current distance from the current distances of all the users who have
marked their status as “I can share a ride”.
6. The distance of destination of the requesting user from the destinations of all the users
who have marked their status as “I can share a ride”.
7. Finally, the app adds up the current location distance and destination distance for each
user whose status is “I can share a ride” from the requesting user.
8. The user with the smallest sum is the selected user.
9. The app sends the message to the selected user “You have a ride request” and displays
the current location of the requesting user on the map.
10. A user who has marked its status as “I can share a ride” can mark its status as “I cannot
share a ride” after the journey ends.
 11

FEASIBILITY STUDY

The first step of my project consisted of assessing the different available ride sharing
applications in order to come up with requirements along with improvements. Given that Play
Store is the official source of applications of Android, I used their search engine to find ride
sharing application by typing the keyword “ride sharing”. A set of similar applications that hold
the same icon showed up in the results. All those applications are from the same publisher but
the difference between them is that each one is for a different country (carpooling.fr,
carpooling.co.uk, …). After installing one of this set of applications and exploring the different
features, I found out that it was offering trips between two cities along with frequent trips. The
only disadvantage is that the application works only in France and in order to have access to
other countries you have to download a separate application. The other apps were similar to the
one previously stated. Another app called Carma offered to make the payments between the
passengers and drier goes through the application. Another set of applications offer different
kind of trip: the one that make parents or tutors that do a trip frequently to take kids to school,
clubs or sports meet so that they take turn. These applications are only available through web
and not as a mobile application. An example of this kind of applications is HopWays.
After exploring the different applications, I came up with essential features that are feasible
and also some improvements that should be considered. Single trips and frequent should be
implemented in order to have an application that answers the need of the market.
 12

ABSRTACT

Carpooling has become a practical, cheap and stress-free way to move around. This project
presents the requirement, design and implementation of an enterprise-class application for
carpooling following a Model-View-Control model. The added features, compared to available
applications, are different kinds of trips, a check-in system and social media integration. The
two kinds of trips are single trips, which are trip between two cities, and frequent trips which
are the ones that commuters do every day. The check-in system enables users to check in
meetings points and notify all users about that. Users can also share their activities on the
application thanks to social media integration. The application is designed to be scalable,
extensible, highly available and with a good performance. The server is implemented using the
powerful JavaScript server LoopBack. The server exposes a REST API, for the clients to
consume, and makes the application compatible with multiple platforms. For the scope of this
project, one client application is developed using Android. An iOS and Web client may be an
improvement to this project given that the server is compatible with these technologies as
previously stated.

13
 CONCLUSION

This carpooling application is an application that complies to the enterprise

class application principles. It is designed to be performing, scalable, extensible, and
highly available. It also ensures the privacy of the users’ data and secures its access.
Given that it may be improved in many ways, the application is also easily
maintainable.

The result achieved in this project is a working Android application and

server that perform the requirements stated in this document. It is still not ready to be
deployed on the Play Store for the public. The main reason is that the server should
be deployed on stronger hardware with a good Internet connection.

The constraint that should have been considered is that developing a server
and an Android application demand a lot of work. This should be considered in the
time allowed for each one of these activities. Due to this lack of time, many things
can be improved in the present application. This includes a better user interface with
more attractive styles. Also, adding more support for authentication systems can be
an improvement.
14