“Share A Ride Application"

IDP
A PROJECT REPORT
Submitted by

RANA NIRALI N (130410107043)

PARMAR KIRTI M (130410107054)
In fulfilment for the award of the degree

Of

BECHLOR OF ENGINEERING
Computer Engineering

SARDAR VALLABHBHAI PATEL INSTITUTE OF

TECHNOLOGY ,VASAD-388306

Gujarat Technological University, Ahmedabad

October, 2016

i
 SARDAR VALLABHBHAI PATEL INSTITUTE OF
TECHNOLOGY, VASAD–388306,GUJARAT–INDIA

Certificate

This is to certify that the dissertation entitled “Share A Ride Application ” has been carried out by
NIRALI RANA(130410107043) under my guidance in fulfilment of the degree of Bachelor of
Engineering in Computer Engineering 7th Semester of Gujarat Technological University, Ahmedabad
during the academic year 2016-2017.

Prof. Keyur Upadhyay Prof. Bijal Talati

Internal Guide Head of Depepartment

ii
 SARDAR VALLABHBHAI PATEL INSTITUTE OF
TECHNOLOGY, VASAD–388306,GUJARAT–INDIA

Certificate

This is to certify that the dissertation entitled “Share A Ride Application ” has been carried out by
Kirti Parmar(130410107054) under my guidance in fulfilment of the degree of Bachelor of
Engineering in Computer Engineering 7th Semester of Gujarat Technological University, Ahmedabad
during the academic year 2016-2017.

Prof Keyur Upadhyay Prof. Bijal Talati

Internal Guide Head of Depepartment

iii
 ACKNOWLEDGEMENT

Every project is an outcome of culmination of efforts of many people. There are teachers, friends
and well-wisher who have contributed to our work directly or indirectly. It might not be possible
to name and thank them all individually. However, we must make a sincere effort to name people
who have taken personal interest and contributed to the successful completion of the project. We
would like to thank our internal guide, Mr. KEYUR UPADHYAY and External guide Mr.
GULABCHAND TEJWANI for whom we have our deepest admiration, for their continuous
guidance throughout the duration of this project. We are also thankful to our Head of Computer
Department Ms. Bijal Talati for being supportive Their faith and belief in our abilities helped
us accomplish our project work.

By:-

Nirali Rana

Kirti parmar

iv
 ABSTRACT

Travelling is a daily part, not only for cities people but village people also. But in 21 st
Century it’s not possible for all to buy their own vehicle and ride them. So we serve our best
facility for all travelers as well as riders to share and ride their vehicle using RIDE
SHARING APPLICATION. In today’s era there is also problem of Noise Pollution as well
as Air pollution in all over the world. Our application is also overcome this problem. We
provide riders to offer their ride and travelers to lift a ride as per their source and destination
point. Mainly we make our project live for delhi people for Odd – Even formula scheme.

v
 List of figures
Figure no. Figure description Page no.
Figure-1 Project schedule chart
Figure-2 Use-case diagram for Rider
Figure-3 Use-case diagram for Traveller
Figure-4 Use-case diagram for Admin
Figure-5 Class diagram
Figure-6 E-R diagram
Figure-7 Activity diagram
Figure-8 State diagram for create ride
Figure-9 State diagram for join a ride
Figure-10 Sequence diagram for Login/Registration
Figure-11 Sequence diagram for create ride
Figure-12 Sequence diagram for join a ride
Figure-13 Incremental Model

vi
 INDEX
1. INTRODUCTION

1.1Organization Profile

1.2 Problem Statement And Definition

1.3Aim And Objective Of The Project

1.4Purpose And Scope Of The Project

1.5Technology And Tool Required

2. REQUIREMENT ANALYSIS

2.1 System Requirement

2.2 Functional Requirement

2.3 Non-Functional Requirement

2.4Time line chart

2.5 Feasibility Study

3. SYSTEM DIAGRAMS

3.1 Use Case Diagram

3.2 Class Diagram

3.3 ER Diagram

3.4 UML Diagram

3.4.1 Activity Diagram

3.4.2 State Diagram

3.4.3 Sequence Diagram

4. SYSTEM DESIGN

4.1System Model

4.2 Data Dictionary

5. REFERENCES

6. APPENDIX

vii
 CHAPTER-1:-INTRODUCTION

1.1 Organization Profile

 Company Details:
Technet is supported by bright mind from world class MNCs. Our skilled team of expert is
well versed with every sector of technology, thus provide best services. Company till date
provided training to more than 10,000 students on various cutting edge technologies and
worked with many domestic and international clients on different domains.

 Company Objective:-
Technet Consultancy provide wide range of software development and consultancy services.
Our main goal is provide quality services in education and development sector.

 Brief History:-
Technet Consultancy was established in 2011 as a software development and training.
Technet Consultancy draws its inspiration from Gulab Chand Tejwani who has been serving
this industry and having more than 15 year of experience. Technet Consultancy is Microsoft
small action partner.

1.2 Problem Statement and Definition

 Problem Statement:-
Based on The Delhi Government's road rationing scheme there was a concept of odd-even
number cars riding , one day only even numbers car can drive and next day the odd
numbers car turn. Driver of a Odd numbered car being penalized in the capital on Even day.
So ride sharing Application is useful for them. We overcome this problem using our
application.

 Definition:-
The Ride share app, gives you the amazing UI to assist you for your ride sharing. It helps you
to find near by rides going on the same destination, one way – round trip and many other
amazing features. You can also choose ride based on different filters like based on fuel prize,
based on car model no., based on prize, based on car type.

1.3 Aim and Objectives of the Project

 Aim of the Project:-
Our system’s goal is give interactions of the riders and travelers as per their need and
according to their source and destination points. We are also aware of noise pollution and
air pollution so using this system we also try to reduce to this.

 Objectives of the Project:-

Our system has the following objectives:

1
 1) Traveler can select ride based on fuel, based on ride model number, based on ride
type ,based on prize.
2) Rider can lift registered user as per their source and destination place.
3) Traveler get push notification once they registered in a system for starting and
ending point.

1.4 Purpose And Scope Of The Project

 Purpose:-
The purpose of designing the Ride Sharing Application is to give the People a platform
for finding a right and a satisfactory Ride according to their needs. It connects the
Riders and Travelers so useful for both of them. Easy and faster service to the people for
getting the Ride.
 Scope:-
Our application will help the Rider and Traveler to get good Traveler for rider and good
rider for traveler according to their requirements faster and in a convenient manner.
Where Traveler can select best Rides from available Rides as per their requirements.Our
application also provides Travelers Push notifications as per their stations ,once they
login in the System.

1.6 Tool/Technology Required

The following are the technologies which are used in our project:
 Front End: HTML5, CSS3, ANDROID,BOOTSTRAP,JQUERY
 Programming Language: PHP , JAVA
 Database: SQLite, MYSQL
 Tools Used: Microsoft Android Studio , XAMPP , Notepad ++

1. HTML5

 HTML5 is the fifth revision and newest version of the HTML standard. It
offers new features that provide not only rich media support, but also enhance
support for creating web applications that can interact with the user, his/her
local data, and servers, more easily and effectively than was possible
previously.
 Some HTML5 features remain unsupported by some browsers. However,
Gecko, and by extension, Firefox, has very good support for HTML5, and
work continues toward supporting more of its features. Gecko began
supporting some HTML5 features in version 1.8.1. You can find a list of all
of the HTML5 features that Gecko currently supports on the main HTML5
page.

2
2. CSS3

 Part of creating web pages is cascading style sheets (CSS).

 CSS is a style language that describes how HTML markup is presented or
styled.
 CSS3 is the latest version of the CSS specification.
 It also adds new features to help developers solve a number of problems
without the need for non-semantic markup, complex scripting, or extra
images.
 New features in CSS3 include support for additional selectors, drop shadows,
rounded corners, multiple backgrounds, animation, transparency, and much
more.

3. ANDROID
 Android is a open source software development platform for creating mobile
applications.
 Android is a mobile OS developed by google based on Linux Kernel.
 Android applications are usually developed in the Java language using the
Android Software Development Kit.

4.BOOTSTRAP

 Bootstrap is the most popular front end framework in the recent time
 Bootstrap is sleek, intuitive, and powerful mobile first front-end framework
for faster and easier web development.
 Bootstrap uses HTML, CSS and Javascript.

5.jQuery

 jQuery is a fast and concise JavaScript library created by John Resig in 2006.
 jQuery simplifies HTML document traversing, event handling, animating, and
Ajax interactions for Rapid Web Development.

6.PHP

 The PHP Hypertext Preprocessor (PHP) is a programming language that

allows web developers to create dynamic content that interacts with
databases.
 PHP is basically used for developing web based software applications. This
tutorial helps you to build your base with PHP.

7.JAVA

 Java is a high-level programming language originally developed by Sun

Microsystems and released in 1995.

3
  Java runs on a variety of platforms, such as Windows, Mac OS, and the
various versions of UNIX. This tutorial gives a complete understanding of
Java.

8.SqLIte

 SQLite is a software library that implements a self-contained, serverless, zero-

configuration, transactional SQL database engine.
 SQLite is the most widely deployed SQL database engine in the world. The
source code for SQLite is in the public domain.

9.Mysql

 MySQL is the most popular Open Source Relational SQL database

management system.
 MySQL is one of the best RDBMS being used for developing web-based
software applications

10.Android Studio

 Android Studio is the official IDE for android application development.

 It is available for download on Windows, Mac OS X and Linux, and replaced
Eclipse Android.

4
 CHAPTER-2:-REQUIREMENT ANALYSIS
2.1 System Requirements
Hardware Requirement (minimum):

 Processor : i3 Processor

 Memory : 4GB RAM

 Hard Disk : 2GB free space on a single drive/partition.

Software Requirement:

 ANDROID SDK
 JAVA

2.2 Functional Requirements

1.Register with OTP:-
• Description : User will have to register himself in the system.
• Input: Filling registration forms
• Output: Registration successful prompt
• processing:Create account in database

2.Login:-

• Description : User will have to register himself in the system.

• Input: Filling registration forms.
• Output: Registration successful prompt.
• processing: Create account in database.

3.Find a Ride:-

• Description: Traveller can find a ride as per his/her source and destination point
based on different filter.
• Input: Travellers Source point Destination point and filter data.
• Output: Show available data based on their finds.
• processing: Search a same source and destination point in a database.

4. Share a Ride:-

• Description:-Rider can share a ride with traveller with almost same source and
destination point.
• Input: Riders source and destination points.

• Output : Show available data based on their finds.

5
• Processing: Search a same source and destination point in a database.

5.Send Request:-

• Description : Travellers can send request to a rider which have same source and
destination.
• Input: To send request
• Output : To receive a request

6. Get Request:-

• Description : Rider get request from traveller and take decision to give lift or not.
• Input : To receive request.
• Output: approve request successfully.

7. Payment:-

• Description: It will decide what amount will be deducted from the travellers account
• Input: Users details.
• Output: Successful payment
• Processing: Pay Money.

2.3 Non Functional Requirements

1.Reliability-factor:-

The capability of the software to maintain the level of performance of the system when
used under specified conditions .Wear or ageing does not occur in software. Limitations
in reliability are due to faults in requirements, design, and implementation. Failures due
to these faults depend on the way the software product is used and the program options
selected rather than on elapsed time.

2. Maintainability–criteria:-
• Changeability: The capability of the software product to enable a specified
modification to be implemented.
• Stability: The capability of the software to minimise unexpected effects from
modifications of the software.
• Testability: The capability of the software product to enable modified software to be
validated.

3. Performance:-

For very large number of users, the server should be able to handle requests
efficiently.Data Storing and Retrieval should be quick. Computation time for evaluating
the answers should be limited and as fast as possible.

6
2.4Time Line Chart

Figure :1

2.4 Feasibility study

Technical Feasibility:
 The technologies used would be Android studio, JAVA ,PHP which are easily
available.
 Databases would be made using SQL because of it's flexibility.
 Thus the system will be technically feasible.
Time Feasibility:
 The deadlines mentioned in the time line chart are estimated on the basis of
resources available and complexity of work.
 Hence proposed system will be completed within the decided time limit.
Operational Feasibility:
 Users of the system are familiar with the Application navigation.
 Simple GUI.

7
 CHAPTER-3:- SYSTEM DIAGRAMS
3.1 Use Case Diagram

1. For Rider:-

Figure :2

8
2.For Traveller:-

Figure :3
3.For Admin:-

Figure :4

9
3.2 Class Diagram:-

Figure:5

10
3.3 E-R Diagram:-

Figure :6

11
3.4 UML Diagrams
3.4.1Activity Diagram:-

Registration/Login

Get OTP

Incorrect

Correct

User Type

Rider Traveller

Registered
Search Ride
Not Registered

Not Available
Register Ride

Available

Select Ride
Create Ride

Send Request
Fill required information

Incorrect Notification Box

Correct
Reject
cofirm
Get
Accept
Request
Get A Ride
Notification Box

Send
notification
Manage Requests Bill

Figure :7

12
3.4.2 State Diagram:-

1.For Create A Ride:-

Figure:8

2.For Join Ride:-

Figure:9

13
3.4.3 Sequence Diagram:-

1.For Login/Registration with OTP:-

User Application Server

Enter contact no. and OTP

Validation

Error message

Send details

Provide access

Home page access

Figure:10

2.For Create A Ride:-

14
 User Application Server

Enter source,destination,date&time

send details

Succesfully updated

Receive request

Accept request
Request accepted

Reject request
Request rejected

Figure:11

3.For Join A Ride:-

User Application Server

Enter source,destination,date&time Request appropriate solution for requested details

Not found

No ride available

Found an appropriate ride

Informs the user

Confirms the ride

Sends confirmation message

Data updated

Acknmowledgement

Figure:12

15
 CHAPTER-4:-SYSTEM DESIGN
4.1 System Model
For our system we will be using Incremental model.

What is Incremental model?

In incremental model the whole requirement is partitioned into different sections. Here
multiple
development cycles occurs, which makes the life cycle a “multi-waterfall” cycle. Cycles are
further divided into smaller modules, which can be more easily managed. Each module
passes
through the different requirements i.e. design, implementation and testing. The first module
produces the working version of the software, so we get working software early on during the
software life cycle. Each and every following release of the module adds some function to the
preceding release. This process is continued until the final system is being achieved.

Figure 13 Incremental Model

When to use Incremental Model

This model should only be used when the requirements of the whole system is well
defined and clearly understood.
Major requirements has to be clearly defined; however, some details can be added with
time.

16
Preparing the working version of the software within less time is necessity.
New technology should be used.
Resources with needed skill set are not available.
There are some high risk features and goals.
Advantages of Incremental Model
Generates working version of software quickly during the software life cycle.
Model is more flexible and less costly when it comes to change scope and requirements.
Testing and Debugging is easy during a smaller iteration.
Customer can respond to each section.
Initial delivery cost gets less.
It is easy to manage risk because risky pieces are identified and handled during the
iteration.
Disadvantages of Incremental Model
Good planning and design is needed.
A clear and complete definition of the whole system is needed before it can be broken
down and built incrementally.
Total cost is higher than waterfall.

4.2 Data Dictionary

No. Field Name Data Type Field Length Constraints For
1 Name varchar 150 Not Null Use
2 Email varchar 50 Not Null r:-
3 Password varchar 50 Not Null
4 Phone No. int 40 Not Null
5 Id int 40 Primary key
6 Gender varchar 40 Not Null
7 Country Varchar 40 Not Null
8 DOB varchar 50 Not Null
9 City varchar 40 Not Null
10 Profile_img varchar 255 Not Null
11 Identity_img varchar 250 Not Null
12 User_type varchar 40 Not Null
13 Address varchar 250 Not NULL

For Admin:-
No. Field Name Data Type Field Length Constraints
1 Name Varchar 40 Not NULL
2 Password Varchar 40 Not NULL
3 Email varchar 40 Not NULL
4 Admin_img varchar 255 Not NULL
5 Company_name Varchar 250 Not NULL
6 Company_email Varchar 250 Not NULL
7 Company_mobile varchar 250 Not NULL
8 Access varchar 50 Not NULL

17
For Ride:-

No. Field Name Data Type Field Length Constraints

1 Name varchar 100 Not NULL
2 ride_no. varchar 60 Not NULL
3 Model varchar 60 Not NULL
4 Id int 20 Primary key
5 No of Seats int 20 Not NULL
6 AC/Non AC varchar 20 Not NULL
7 Source varchar 100 Not NULL
8 Destination varchar 100 Not NULL
9 Destinatin_via varchar 100 Not NULL
10 Date Date 30 Not NULL
11 Time Time 30 Not NULL
12 Fuel_type varchar 50 Not NULL

For Notification:-
No. Field Name Data Type Field Length Constraints
1 User_id int 20 Primary key
2 message varchar 100 Not NULL l

18
 CHAPTER-5:-REFERENCES

Book Reference

[1] “Object Oriented Modeling and Design with UML”: Michal R Blaha & James R
Rumbaugh

[2] PL SQL Ivan Bayross

[3]Database System by Korth

[4] Software Engineering by Roger S. Pressman

Web Site Reference

[1] http://www.w3schools.com/aspnet/

[2] http://www.tutorialspoint.com/asp.net/

Pattern Search Site

http://www.freepatentsonline.com/

19
 CHAPTER-6:-APPENDIX
Canvas:-
EMPATHY CANVAS:
This is the first canvas contains users, stake holders, activities and Happy-Sad story boarding
related with the domain.

20
IDEATION CANVAS:
Second canvas of domain associate with people, activities, solutions and realistic part in which we
have to take an activity its time period and surrounding where it is going to be performed.

21
PRODUCT DEVELOPMENT CANVAS:
As the name suggests the canvas is all about product like it’s component, features and experience
after that customer feedback and the modification in addition the people and purpose are also
there.

22
A E I O U SHEET:
1. ACTIVITIES:

It includes Observations, elements, features associated directly or indirectly with the all
activities attached with product.

2. ENVIROMENT:

It include the atmosphere, physical space and function of the context in which an activity
takes place.

3. INTERACTION:

It includes how product will interact with the user and how product will interact with the
surroundings.

4. OBJECTS:

What are the objects and devices people have in their environments and how do they relate
to their activities?

.
USERS:

It is related with users which are directly or indirectly connected with the product.

23
.

24
25
26