Car-pool Management System

1. System
1.1. Introduction
Carpooling (also known as car-sharing, ride-sharing and lift sharing), is the sharing
of car journeys so that more than one person travels in a car. Carpooling reduces
each person’s travels costs such as fuel costs, tolls, and the stress of driving.
Carpooling is one method that can be easily instituted and can help resolve a variety
of problems that continue to plague urban areas, ranging from energy demands and
traffic congestion to environmental pollution. Authorities often encourage
carpooling, especially during high pollution periods and high fuel prices.

1.2. Existing System Study

1.2.1. BlaBla car

 Choose who you travel with

o BlaBla car will Allow Users to see which members have verified
their Govt ID and also how many Facebook friends and LinkedIn
connections they have. He/she can also see who are the
community's leading ride sharers thanks to their experience
level.
 Check out their ratings
o See what others say about them, and benefit from the experience
of other members when choosing who to travel with.
 Find out more about them
o Check out their preferences and mini bio so you know all about
who He/she will be travelling with.
 Profiles are moderated
o All profiles, photos, ratings, ride offers and ride comments are
moderated to maintain trust and respect in the community.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 1
 Car-pool Management System

 Insurance
o As co-travelers only contribute to fuel costs, no profits are made
by car owners. This means their insurance is not affected.
 Get in touch before you travel
o Use our secure messaging system. Get to know each other before
the ride and easily arrange where to meet.

1.2.2. Quick Ride

 Multi-Vehicle Support:

o This feature enables Ride Givers to configure multiple vehicles

and allows to change vehicle while posting a ride. One can
change the vehicle from their profile and also from live ride
screen.

 Recurring/Regular Ride:

o User who are travelling to office by crowded bus, high

demand cab/taxi, and auto rickshaws can find rides offered
by Ride Givers who are travelling on the same route. Get
comfortable car rides at bus fare.

 Fare-Bidding Feature for Ride Takers:

o Ride Takers can send ride request with flexible ride fare.

 Fare-Bidding Feature for Ride Givers

o Ride Givers can send ride request to Ride Takers with

flexible ride fare at each seat level.

 Refund Feature

o In-app Refund option will help Ride Takers and Ride Givers
to initiate refund when they have not taken the ride but

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 2
 Car-pool Management System
charged due to pre-check-in or charged more etc. Refund can
be full or partial.

 Switch Rider feature for Ride Taker

o Ride Taker can switch the Rider for their convenience with
the help of Switch Rider options from the matching options.
When the request is accepted, the ride will be unjoined with
current Rider and joined to the switched Rider.
 Ride Givers can get missing ride payments from Ride Takers.

 Recharge

o In-app wallet for Cashless and Automated Payments. Wallet

can be recharged using Credit/Debit card/Net Banking, Pay
TM and PayU. 1 Point = 1 Rupee

 Redeem

o Redeem the earned ride points to Fuel Card (Shell and HP)
or to Pay TM Wallet. Now, Ride Givers can check the status
of redemption requests.

 Share & Earn

 Refer Friends and Colleagues to Quick Ride and become a revenue

sharing partner!

1.2.3. Zimride
 Private name and phone
o This site allows users to keep last names on the site hidden, and
phone numbers and email addresses are also kept private until
a booking has been accepted.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 3
 Car-pool Management System
 Feedback and testimonials
o This site strongly encourages users to leave feedback for each
other after a ride.

 Mutual friends
o With Facebook integration, you can see if you have friends in
common with other members. Look for mutual friends on ride
post pages and member profiles.

 Secure payments
o When a booking is accepted, passengers are charged but
payment is held until 24 hours after the ride is complete. If the
ride doesn’t happen or something goes wrong, simply let us
know. Drivers can rest assured knowing they’ll get paid without
the need to ask in the car.

 Easy messaging
o Use your Zimride inbox to easily keep track of a conversation
about your trip. That way, the email addresses associated with
your Zimride and PayPal accounts are kept private.

1.2.4. Comparative Study

1.2.4.1 Common Features

 Provide Inter-city & Intra-city Rides

 Manage Feedback
 Chat Room
 Normal Verification (Email-id && Facebook Login)
 Secure Payment (Online & Offline)

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 4
 Car-pool Management System
1.2.4.2 Distinct features

 Fare Management In BlaBla car

 Gov. Email Id Verification in Quick-ride
 SOS Feature In Quick-Ride
 Connect Mutual-Friends Through Facebook In Zimride

1.2.4.3 Limitation

 No privacy
 The owner driver is responsible for his passengers
 You won’t have much freedom or flexibility with your schedule and
activities
 Not helpful for blind people

1.2.4.4 Features adopted for proposed system

 Registration
 Login-in/log-out
 Inter-city & Intra-city Travel
 Feedback System
 Aadhar Verification
 Social Media Verification
 Gender Selection
 Emergency

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 5
 Car-pool Management System

2. Proposed System
2.1. Definition
Carpooling (also known as car-sharing, ride-sharing, lift- sharing), is the shared
use of a car, especially for commuting to work, often by people who each have a car
but travel together to save cost and to promote other social-environmental
benefits. People who don't have a car can also contact people with car and
commute together.

2.2. Objective
The basic objective of car-pooling is the sharing of car journeys so that more than
one person can travel in a car. When people are more and they are using the same
vehicle then it can reduce each person's travel costs like fuel costs and the stress
of driving.

This Project will serve the following objectives: -

 Registration
 Login/logout
 Provides pool details to the user with picture of the Owner and
Passenger Vice versa
 Track the location till the pool is made
 SMS alert For Security Purpose
 Aadhar card Verification and Pan Card Verification
 Emergency Service
 Gender Selection Female Can Select Female and Vice-versa

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 6
 Car-pool Management System

2.3. Scope

• “Convenience Fees” shall mean such fees that shall be charged by

This System for the Services provided by it, to be paid partly by
passenger and partly by owner, at the end of each Trip and which
would be some portion of Cost Contribution for that Trip.

• “Cost Contribution” means the amount calculated at the end of each

Trip on the basis of pre-disclosed parameters which shall be payable
by a Passenger as part of his contribution towards the cost of the
Trip

• To use the Service each Member must create a User Account and
shall agree to provide any personal information requested by this
system. Use of the Site is limited to those over the age of 18 years at
the time of registration.

• Owner can drop the Passenger to the bus stop near by their
Destination

• The Project is going to be web portal.

• Passenger can communicate with the driver via the messaging

system or he/she can call to owner.
2.4. Requirements
2.4.1. Expected
 Fare Management In BlaBla car
 Gov. Email Id Verification in Quick-ride
 SOS Feature in Quick-Ride
 Connect Mutual-Friends Through Facebook In Zimride

2.4.2. Exciting
 Inter-city & Intra-city Travel
 Feedback System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 7
 Car-pool Management System
 Chat Room
 Normal Verification (Email-id && Facebook Login)
 Secure Payment (Online & Offline)

2.5. Acronyms and abbreviation

 SOS
o SOS is a texting and chatting acronym that means someone
over shoulder.it is used during emergency situation

2.6. Proposed Technologies

 MySQL is an open source relational database management system
that runs as a server providing multi-user access to a number of
databases.
 PHP: Hypertext Pre-processor (or simply PHP) is a general-
purpose programming language originally designed for web
development. It was originally created by Rasmus Leadoff in 1994.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 8
 Car-pool Management System

3. System Design
3.1 Use Cases

3.1.1 Actors and Roles

 Admin
 Owner
 Passengers

The Role of the admin is:

o The admin will have all the Rights which the owner and Passenger has no access to
like the process of bill generation, introducing new packages, Managing schedules.
The role of the admin is discussed in detail below.
o User Details: Admin can View the Details of Both Owner and Passenger.
o Update Profile: Admin Can Update His/her Profile.
o Manage User Details: Admin Will Manage the User Details like he/she can Modify or
Delete the user Details of owner and passenger.
o Manage Ride Details: Admin will manage The Ride Details like Admin can View the
Rides and Track the Location of Ride and Admin will Manage the Payment.
o Manage User: Admin will Manage the User by Verifying the User and Admin Can
Remove the Both User Owner and Passenger.
o Manage Feedback: Admin Can View the Feedback and Most of the
promotion/Decision is Depend upon The Feedback Because If an owner is Having
Good Number of feedback Then He/she will get Some Benefits Like More Number Of
passenger will join his/her pool because of positive feedback and because of Feedback
Owner will Become Trustworthy.
o Logout: Admin will Logout from The System After All operation is Performed well.

The Role of the owner is:

The Owner will Register into The System to Use the System and Will Give Proper Details
During Registration

o Once The owner is Registered, he/she can log in to system to use

o Owner Can update his/her details like can modify his/her data and can delete the
data
o Owner will create the pool
o Owner will manage Schedule like he/she can add, edit, view and Delete the
Schedule
o Owner will manage the fare he/she can increase the amount at certain level.
o Owner will manage the location like source and destination.
o Owner will accept the request of the passenger.
o Owner can delete the pool.
o Owner will manage the feedback he/she can reply to given feedback. And can
delete to harsh feedback.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 9
 Car-pool Management System

The Role of the passenger is:

The passenger will Register into The System to Use the System and Will Give Proper
Details During Registration

o Passenger will register into the system.

o Passenger will login after the registration.
o Passenger can view the schedules.
o Passenger will search for the pool.
o Passenger will select the pool.
o Passenger will send the request.
o Passenger will be notified while the pool is confirmed or canceled.
o Passenger can update the profile.
o Passenger can view the owner details.
o Passenger can make payment online or offline.
o Passenger can give feedback to owner and can respond to feedback.
o Passenger can track the location.
o Passenger can cancel the booking.
o After all operations and uses Passenger can logout.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 10
 Car-pool Management System
3.1.3 Use-Cases diagrams
3.1.3.1. Admin

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 11
 Car-pool Management System

3.1.3.2. Passenger

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 12
 Car-pool Management System

3.1.3.3. Owner

3.2 E-R Diagram

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 13
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 14
 Car-pool Management System

3.3 Data Flow Diagrams

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 15
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 16
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 17
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 18
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 19
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 20
 Car-pool Management System

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 21
 Car-pool Management System

3.4. Data Dictionary with Constraints

1.1 Data Dictionary With Constraints

3.4.1

Data

Passenger
Field Name Data Constraints Description
Types(Size)
Passenger_id CHAR(5) PRIMARY KEY Unique id of the passenger.

Passenger_Name VARCHAR(30) NOT NULL The Name of passenger.

Passenger_Email VARCHAR(30) NOT NULL The Email of a passenger.

Address VARCHAR(255) NOT NULL The address of passenger.

Passenger VARCHAR(30) NOT NULL User name of passenger.

User Name
Passenger VARCHAR(15) NOT NULL The user name password of
Password passenger.

Owner
Field Name Data Constraints Description
Types(Size)
Owner_id CHAR(5) PRIMARY KEY Unique id of a owner.

Owner_Name VARCHAR(30) NOT NULL The name of owner.

Contact_No Integer - The contact number of owner.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 22
 Car-pool Management System
Driving License VARCHAR(15) NOT NULL The driving license of owner.

Owner VARCHAR(30) NOT NULL The user name of a owner.

User Name
Owner VARCHAR(15) NOT NULL The user name password of
PassWord owner.

Routes
Field Name Data Constraints Description
Types(Size)
Route_id CHAR (5) PRIMARY KEY Unique id of a route.

Route_type VARCHAR(30) NOT NULL The types of route.

Route_Description VARCHAR(255) NOT NULL The details of routes.

Route_Name VARCHAR(30) NOT NULL The name of a route.

Cars
Field Name Data Constraints Description
Types(Size)
Car_id CHAR(5) PRIMARY KEY The Unique of a car.

Car_Name VARCHAR(30) NOT NULL The Name of a car.

Car_Type VARCHAR(25) NOT NULL The Types of a Car.

Vehicle _no VARCHAR(10) NOT NULL The plate number of Car.

Passenger_id CHAR(5) FOREIGN KEY The id of passenger

Admin

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 23
 Car-pool Management System
Field Data Constraints Description
Name Types(Size)
Admin_id CHAR(5) PRIMARY KEY The Unique id of a admin.
Password VARCHAR(15) NOT NULL The username password of
admin.

Pool
Field Name Data Constraints Description
Types(Size)
Pool_id CHAR(5) PRIMARY KEY The unique id of a pool.

Pool_Amount INTEGER - The amount of pool.

Pool_Description VARCHAR(255) NOT NULL The details of pool.

Pool_Name VARCHAR(30) NOT NULL The name of a pool.

Passenger_id CHAR (5) FOREIGN KEY The id of passenger.

Bill
Field Name Data Constraints Description
Types(Size)
Bill_id CHAR(5) PRIMARY KEY The unique id of bill.

Bill_name VARCHAR(30) NOT NULL The name of a bill.

Bill_recipt VARCHAR(255) NOT NULL The receipt of a bill.

Bill_type VARCHAR(30) NOT NULL The type of a bill.

Passenger_id CHAR(5) FOREIGN KEY The id of passenger.

Feedback

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 24
 Car-pool Management System
Field Data Constraints Description
Name Types
Question VARCHAR(255) NOT NULL The Questions for feedback.
Answer VARCHAR(255) NOT NULL The Answer the questions for
feedback.

3.5 User interface Design

3.5.1 UI Specification with technical justifications

 Used External CSS registration.

 Used html 5 elements to structure webpage.
 Page size is desktop size(1368x768).

3.5.2 Validation
 Validation for Registration Form

Sr.N
Field Actual data Valid Set Invalid Set
o
1 User_id 1 ^[0-9] ABC
First
2 Raj ^[A-Za-z] 434@!%
Name
Last
3 Varma ^[A-Za-z] 873@!%
Name
^(?=.*[a-z].*[a-z])(?=.*[A-
Passwor Z].*[A-
4 Raj#012 ABC!@#123
d Z])(?=.*\d.*\d)(?=.*\W.*\W
)[a-zA-Z0-9\S]{9,}$
Mobile
5 9904660041 ^[0-9]{10} raj1237@72
No
^[a-zA-Z0-9](\.?[a-zA-Z0-
Email_I rajvarma@gmail.c
6 9]){5,}@g(oogle)?mail\.co 324raj@gmai.com
D om
m$
7 Gender M/F [A-Z] MALE
61002, surat, 61002 su&rat,
10 Address Gujarat, 04843, ^\d+\s[A-z]+\s[A-z]+ Guj@rat, 04843,
India Indi@

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 25
 Car-pool Management System

 Validation for Reset Password

Sr.N
Field Actual data Valid Set Invalid Set
o
^(?=.*[a-z].*[a-z])(?=.*[A-
Old
Z].*[A-
1 Passwor Raj#012 rah!@#123
Z])(?=.*\d.*\d)(?=.*\W.*\W)[
d
a-zA-Z0-9\S]{9,}$
^(?=.*[a-z].*[a-z])(?=.*[A-
New
Ravaramaj#01 Z].*[A-
2 Passwor rah!@#123
2 Z])(?=.*\d.*\d)(?=.*\W.*\W)[
d
a-zA-Z0-9\S]{9,}$
Confirm ^(?=.*[a-z].*[a-z])(?=.*[A-
New Ravaramaj#01 Z].*[A-
3 rah!@#123
Passwor 2 Z])(?=.*\d.*\d)(?=.*\W.*\W)[
d a-zA-Z0-9\S]{9,}$

 Validation for Login

Sr.N
Field Actual data Valid Set Invalid Set
o
1 User_id 1 ^[0-9] ABC
^[a-zA-Z0-9](\.?[a-zA-Z0-
Rajvarma@gmail.co
2 Email_ID 9]){5,}@g(oogle)?mail\.co 324raj@gmai.com
m
m$

 Validation for Reset password

Sr.N
Field Actual data Valid Set Invalid Set
o
^[a-zA-Z0-9](\.?[a-zA-Z0-
Email_I Rajvarma@gmail.co 324raj@gmai.co
1 9]){5,}@g(oogle)?mail\.com
D m m
$

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 26
 Car-pool Management System
1.1.1. Navigations
• Navigation for Admin

• Navigation for Owner

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 27
 Car-pool Management System
• Navigation for Passenger

3.5.4 Screenshots
3.5.4.1 Login page

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 28
 Car-pool Management System

3.5.4.2 Reset Password page

3.5.4.3 Forget Password page

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 29
 Car-pool Management System

3.5.4.4 Signup page

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 30
 Car-pool Management System

3.6. Reports

3.6.1. TPS

3.6.1.1. Inputs-Process-Outputs [detailed explanation for each report]

3.6.1.1 Owner

Input:

Field Name Value

MYRIDE

Process:

Passenger, Pool table need to get retrieve.

Output:

Field Name Value

Pool id Po1
Pool date 2/07/2019
Pool pickup Surat
Pool Drop bardoli
Pool Amount 60
Passenger id P1
Passenger name Raj Varma

Pool Passenger Owner Pool Pickup Drop Ride Car Car

id name name date address Address Fare Name Number

3.6.1.2 Report usage

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 31
 Car-pool Management System
Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

3.6.2.1 Passenger

Input:

Field Name Value

MYRIDE NULL

Process:

Pool, Owner table need to get retrieve

Output:

Field Name Value

Pool id Po1
Passenger id P1
Pool date 10/07/2019
Pool pickup Bardoli
Pool drop Surat
Car id C1
Owner id O1
Pool description Po1
ride fare 60

Pool passenger Owner Pool Pickup Drop Ride Car id Pool

id id id date address Address Fare description

3.6.2.2 Report usage

Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 32
 Car-pool Management System

3.6.2.3 MIS
3.6.2.1. Inputs-Process-Outputs [detailed explanation for each report]

Admin
1.
Input:
Field Name Value
Bill id

Process:

Bill table will process to retrieve the data.

Output:
Field Name Value
Owner name Raj Varma
Owner car name Swift
Owner car no GJ19AF6991
Bill id B1
Passenger name Mayur Nhavi
Pool date 2/07/2019
Pickup Address Surat
Drop Address Kamrej
Ride Fare 50

3.6.2.3. Layouts
Bill id:

Bill Passenger Owner Pool Pickup Drop Ride Car Car

Id name name date address Address Fare Name Number

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 33
 Car-pool Management System
3.6.2.4. Report usage
Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

Input:

Field Name Value

Pool date Form 2/07/2019
Pool date To 3/07/2019

Process:

Pool table a null of fee process for retrieve the data.

Output:

Field Name Value

Pool id P1
owner id O1
Pool date 2/07/2019
Pickup address Surat
Drop address Ahmedabad
Ride fare 500
Car name Swift
Car number GJ19AF6991

Layout:

Pool date from:

Pool date to:

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 34
 Car-pool Management System

Pool owner id passenger Pool Pickup Drop Ride Car Car

id id date address Address Fare Name Number

3.6.2.3. Report usage

Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

Minimum

Input:

Field Name Value

Date from 3/07/2019
Date to 4/08/2019

Process:

Pool table need to be process for retrieve data

Output:

Field Name Value

Minimum pool 10
Pool id P1
Pool amount 100
Pool date 3/07/2019
Pool pickup Surat
Pool drop Kamrej
Pool payment Online
Pool description Nothing
Passenger id P1
Passenger name Mayur Nhavi
Layout:

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 35
 Car-pool Management System
Pool date From:

Pool date To:

Pool owner id passenger Pool Pickup Drop Ride Car Car

id id date address Address Fare Name Number

Minimum Total Rides/pool are:

3.6.2.3. Report usage
Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

Maximum

Input:

Field Name Value

Date from NULL
Date to

Process:

Pool table need to be process for retrieve data

Output:

Field Name Value

maximum pool 100
Pool id P1
Pool amount 10000
Pool date 3/07/2019
Pool pickup Surat
Pool drop Kamrej
Pool payment Online
Pool description Nothing
Passenger id P1

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 36
 Car-pool Management System
Passenger name Mayur nhavi
Layout:

Pool date from:

Pool date to:

Pool owner id passenger Pool Pickup Drop Ride Car Car

id id date address Address Fare Name Number

Maximum Total Rides/pool are:

3.6.2.3. Report usage
Reports Is Used To retrieve The Data of Pool/ride They Joined or Created.

4.Refrences
4.1 Books

4.2 Web references

4.3 Additional references

[201806100610006, 201806100610011,
201806100610014, 201806100610020] Page 37