COLLABORATIVE

PROJECT WITH
R SYSTEMS
CAR POOLING
MOBILE APPLICATION

SUBMITTED TO: SUBMITTEDBY:

MS. INDU KASHYAP SAHIL KUKREJA
DEEPIKA SAGAR
NIKITA RANA
KASHISH HANDA
SHUBHAM SHARMA

1|Pa ge
 CAR POOLING APPLICATION

 Login Screen: Login Screen has fields named as Email and Password.
 This screen requires the basic information of the user to be filled. Users will use their
social media accounts in order to log in.
User can act as:
 Driver: owns a car and is looking for passengers/clients who have the same route and
want to share a ride. Driver publishes the information regarding the trip on the
application in order to find the clients.
 Client/passenger: one that doesn’t own a car but wants to join the trip that has been
published by the driver and agrees to all the specified terms and conditions that will
include the price and behavior.
 Third-party authentication like Facebook or Google account can be used to verify the
identity of the users.

 Application requires both the driver and passenger to be logged-in, they can use the
login forms of either Google or Facebook. For this matter, the user is requested to
connect the app to his account and then proceed for sign in/up. After the user authorizes
the application to access his social media account, the server retrieves his info. If he has
never logged to the application before, a new account is created for him.

 Home Screen Drawer: Home Screen shows options with sidebar Get Ride, Offer Ride,
Ride History, Notification and Logout.

 Drawer Header: On click of photo, user can view and edit his profile. There would be
options to upload photo by browse and also have ability to crop image, enter Phone
Number and Car details like name of Car, type of Car.

 Get Ride Screen

 There are auto-complete location search fields of “Pick Up” and “Destination”. Pick-Up
field will be prefilled with current location.
 Search should be based on following criteria’s:
2|Pa ge
  Exact source and destination of the all available rides.
 Search for routes of all the available rides and check if passenger’s source and
destination points are lying within available routes.
TRIP TYPE:
 REGULAR TRIP: A onetime long distance planned travel between two points (usually
cities) with a defined departure time and price.
 FREQUENT TRIP: A short or medium distance frequently includes (daily/weekly) a
neighborhood, workplace, school or other point of interest.
 If there are no rides available for the given search, a message “No riders available” will
be displayed.
 The application will use Google geo-localization and mapping system to map users.
 Passengers need to specify the departure date with the expected arrival and departure
time. After specifying the preferences of the trip, the user can send a request to the rider to
confirm his request.

 Offer Ride Screen

Rider would only be able to offer rides on his phone number. Rider will offer ride on this
screen, there are autocomplete location search fields for “From” and “To”. “From” field
will be prefilled with current location. Once user selects source and destination, Map with
optimized path would be shown. Now rider can “Publish Ride” from here. As rider
publish ride, ride details will be stored in DB on server. DB will search for available
passengers interested for these rides then push notification would be send to all the
passengers. Rider has to accept requests.

 The driver can create a new trip and can publish it as well. Thereafter, information will be
displayed on the search screen if the right passenger searching for that trip is found. The
displayed information consists of origin, destination, meeting point, both departure and
estimated arrival time and the travelling preferences that will include price, number of
bags,
Number of passengers, pets etc. along with the maintenance of one’s behavior that
includes prohibited smoking, drinking and other issues as per acceptance of the user.

3|Pa ge
Mandatory information provided by driver:-
Upload
 Whena driver uploads one’s id they would need to provide their Adhar
number. This number won’t be made public and would be kept with the
organization for security purposes.
 Driver has to upload his/her driving license along with either RC or
insurance papers of the car.

 Ride History Screen

4|Pa ge
 It contains list of rides taken or offered. There will be option of “Cancel Request” against
requested ride, as passenger cancel request, a push notification goes to the rider “User
(name of user) has cancelled to take your share ride. This screen also shows rides taken
by the user. On click to particular ride again “Ride Details Screen” will open.

 Notification Center Screen: All the notification comes to user will be stored here, as in
if user misses any notification, user can see here.

 Application manages its notifications through the use of web service like Google Cloud
Messaging. Cloud messaging being multi-platform will help the application to maintain
the compatibility with almost all technologies present.
 Pushwoosh service can also be used that will help in centralizing the notification system
for various platforms like android, iOS, web etc.

 Check-in trip:
After finalizing the meeting point both the users should arrive the spot on time and will
check-in to show other user their punctuality. The application will use the GPS
technology for time to time checking of the meeting point.

PRODUCT FUNCTIONS
All used cases are explained below:
Sign Up: Users need to sign up to use the web site. The users should have a username and
password. After filling their name, surname, e-mail, age, job, phone and gender information, they
get registered.

5|Pa ge
Sign In: If a user is signed up, she/he can sign in the system by filling username and password
fields.

Sign Out: A user may need to sign out from the system. She/he can do it by clicking the sign out
button which is placed in every page.
Offer Ride: Users may add transportations by specifying a route, t h e time period and the
number of empty seats. The user can select the route by two different ways. The first way is by
entering the starting and ending locations. Thus, the route is drawn on the map. The other way is
by selecting start and end locations on the map. Also, he/she can select at most 3 waypoints.

6|Pa ge
Delete Transportation Route (ride): A user may delete his/her transportation route. After
deleting route, other passengers in that transportation will be informed by the system.
Search ride: A user can search for transportations such that one can see suitable routes to his/her
destination by specifying time and route.

Get Ride: A user may use a transportation by sending transportation request to the driver of the
transportation.

Ride History: It contains list of rides taken or offered. There will be an option of “Cancel Request”
against requested ride, as passenger cancel request push notification goes to rider “User (name of
7|Pa ge
user) has cancelled to take your share ride. This screen also shows rides taken by user. On click
to particular ride again “Ride Details Screen” will open.

Send Message: The users can have communicate each other via messages.

Reply to A Message: After receiving a message, the user can read the message.

Block User: When a user receive disturbing message, she/he can block the user who send that
message.
Confirm message: A confirmation message will be sent to the user after the driver has accepted
the request for car pool.

8|Pa ge
Rate User : After having a transportation, the users in the same transportation can rate each
other in the application Thus, other users can see the user rates and they can decide which
transportation is better.

Main page:

9|Pa ge
 Notification: After confirming the ride, the user would be getting the updates regarding the time
left to reach at the pickup point.
Also notifications would include the received unread messages by the user.
The driver would be receiving a notification that the user has accepted the request to pool the car
along with the time left for reaching the pickup point.

Customer care: user can share his/her experience regarding the application.

10 | P a g e
Application layout:-

CONSTRAINTS
 Carpool system requires mutual trust i.e. the users’ security of life must be protected by
the government’s law system but there is no legal infrastructure about this driver-client
relationship in our country.
 The system requires remote server which enables the system functionality and data
storage. Because of this situation, when the server crashes the system will not be able to
operate until the server becomes available to respond to system requests.
 The users’ information is stored in a database which if hacked can lead to the users’
Information being no longer private.
 To sum up, Carpool system has constraints in terms of regulatory, reliability, safety and
security but these constraints can be manageable.

ASSUMPTIONS AND DEPENDENCIES

11 | P a g e
User interface and some functionalities can be changed and added during the development
process of the project which in turn can change the dependent system requirements.

TECHNOLOGIES INVOLVED
1. Google maps: for map and direction
Google map API for android is used to show GPS coordinates in the map. Google uses a
textual identifier that uniquely identifies a place so it is useful to unify the name of places
which can avoid user confusion.

2. Facebook and Google plus:

It will help the user to login quickly into application.

12 | P a g e
INTERNAL STRUCTURE

14 | P a g e
8. ER DIAGRAM

9. LIST OF AVAILABLE RIDES

On click of get a ride List items consists of image view, name and route of rider along with
Time offered by rider. Passenger can select a ride to confirm, ride details screen will open.

15 | P a g e
10.RIDE DETAILS SCREEN
 This screen shows ride and riders details like time and route of ride. Rider image view
with car name, email of rider and seats available in car.
 On click confirm button, push and email notification goes to rider, if rider agree,
again a notification come to passenger that your ride is confirmed and his/her phone
number would also be shared.
 If rider rejects the request, passenger would be notified that “Rider (name of rider)
has rejected your request. Please select any other ride.”

11.RIDER PROFILE SCREEN

On click of image view of rider shows rider profile page like photo, contact number, no. of
rides taken or no. of given, rating of this particular rider.

12.FEEDBACK AND RATING ON RIDE

Whenever user ride has been completed there will be a screen open on app to give feedback
and rating on ride.

 RATE DRIVER/PASSENGER
 Both the driver and passenger can rate each other which can be used as a benevolence of
trust by the other users by seeing up the reviews.
 The importance of the rating is to encourage users to be helpful and nice during the trip
so that they gain popularity in the application.
 It is also a way to ensure users about who can be trusted or not.
 The ratings represent a relative guarantee for the users to trust each other.

 RATING FIELDS
 PUNCTUALITY
 COMPANIONSHIP
 HONESTY
 OVERALL RATING

16 | P a g e
  DRIVER RATING FIELDS
 SAFE DRIVING
 COMFORT

CONCLUSION
 In this document, the functional and other requirements of the system are described.
Furthermore, the needs of the user are stated through the document. However, all
requirements are not defined and some of the requirements needs to be clarified in
this document.
18 | P a g e