I. ABSTRACT
Traffic congestion, high gas price and inadequate public transportation are major challenges for any country, business or individual. The traditional approach to solving these problems has been to improve public transportation and use greener energy. These approaches require huge investment, research and time, and can only be carried out by governments or businesses. An alternative solution seeks to reduce the number of vehicles on the road based on ridesharing.
Vehicle Sharing Systems, which aim to bring together travelers with similar itineraries and time schedules, may provide significant societal and environmental benefits by reducing the number of cars used for personal travel and improving the utilization of available seat capacity. Effective and efficient optimization technology that matches drivers and riders in real-time is one of the necessary components for a successful ride-share system.
We formally define dynamic Vehicle Sharing and outline the optimization challenges that arise when developing technology to support Vehicle Sharing. We hope that this project will encourage more research by the transportation science and logistics community in this exciting, emerging area of public transportation.
i
Contents ................................................................... ............................................. ............................................. ........................................... ....................i I. ABSTRACT ............................................ ................................................................. ............................................. ............................................. ........................................ ................. iii II. List of Figures.......................................... .................................................................. ............................................. ............................................. ......................................... ..................iv III. List of Tables ........................................... ...................................................... ............v IV. ABBREVATION, NOTATION AND NOMENCLATURE .......................................... Chapter 1 - Introduction ....................... ............................................. ............................................. ............................................. ............................................. ............................... ........ 1 Chapter 2 - Literature Survey ............................................ .................................................................. ............................................ ............................................. ......................... 3 Chapter 3 - Report on Present Investigation ......................... ................................................ .............................................. .......................................... ................... 6 3.1 Software Requirement Document (SRS) .......................................... ................................................................. ....................................... ................ 6 3.1.1 Introduction.......................................................... ................................................................................ ............................................. ....................................... ................6 3.1.1.1 Purpose....................................................... ............................................................................ ............................................. ............................................. ........................ 6 3.1.2. Overall Description. ................................................ ...................................................................... ............................................ ................................... ............. 7 3.1.3. Operating Environment. ............................... ..................................................... ............................................. ............................................. ........................ 8 3.1.4. External Interfaces Requirements. ......................................... ............................................................... .......................................... .................... 8 3.1.5. System Features. .......................................... ................................................................ ............................................ ............................................. ......................... 9 3.1.6. Other Non-Functional Requirements. ................................ ...................................................... ............................................ ...................... 12 3.2 Project Design ........................................... ................................................................. ............................................ ............................................. ................................. .......... 13 13 3.2.1 Project Model ............................................ .................................................................. ............................................ ............................................. .......................... ... 13 3.2.2 Use Case Diagram.......................... Diagram................................................ ............................................ ............................................ ..................................... ............... 14 3.2.3 Activity Diagram .......................................... ................................................................ ............................................ ............................................ ...................... 15 3.2.4 Class Diagram .................................................. ......................................................................... ............................................. ........................................ .................. 17 3.2.5 Data Base Schema.......................... Schema................................................ ............................................ ............................................ ..................................... ............... 18 3.2.6 Sequence Diagram ............................................ .................................................................. ............................................ ........................................ .................. 20 3.2.7 Interface Design ........................................................... ................................................................................. ............................................. ............................. ...... 21 3.3 Implementation Details ............................................ .................................................................. ............................................ ........................................ .................. 24 3.3.1 User Registration and login Module ............................... ..................................................... ............................................. .......................... ... 24 3.3.2 User Interface Module ......................................... ............................................................... ............................................. ..................................... .............. 25 3.3.3 Create Pool Module .......................................... ................................................................ ............................................ ........................................ .................. 25 3.3.4 Search Pool Module ...................................... ............................................................ ............................................ ............................................ ...................... 26 3.4 Testing ............................................ .................................................................. ............................................ ............................................. ............................................ .....................27 Chapter 4 - Results and Discussion ............................................................. ................................................................................... ........................................ .................. 31 Chapter 5 - Conclusion and a nd Future Scope ........................................... .................................................................. ............................................. ......................... ... 33 Appendix ........................................... ................................................................. ............................................ ............................................ ............................................. ................................. .......... 34 References ............................................ ................................................................... ............................................. ............................................ ............................................. ............................. ...... 36 Acknowledgement .......................................... ................................................................. ............................................. ............................................. ........................................ ................. 37
ii
Contents ................................................................... ............................................. ............................................. ........................................... ....................i I. ABSTRACT ............................................ ................................................................. ............................................. ............................................. ........................................ ................. iii II. List of Figures.......................................... .................................................................. ............................................. ............................................. ......................................... ..................iv III. List of Tables ........................................... ...................................................... ............v IV. ABBREVATION, NOTATION AND NOMENCLATURE .......................................... Chapter 1 - Introduction ....................... ............................................. ............................................. ............................................. ............................................. ............................... ........ 1 Chapter 2 - Literature Survey ............................................ .................................................................. ............................................ ............................................. ......................... 3 Chapter 3 - Report on Present Investigation ......................... ................................................ .............................................. .......................................... ................... 6 3.1 Software Requirement Document (SRS) .......................................... ................................................................. ....................................... ................ 6 3.1.1 Introduction.......................................................... ................................................................................ ............................................. ....................................... ................6 3.1.1.1 Purpose....................................................... ............................................................................ ............................................. ............................................. ........................ 6 3.1.2. Overall Description. ................................................ ...................................................................... ............................................ ................................... ............. 7 3.1.3. Operating Environment. ............................... ..................................................... ............................................. ............................................. ........................ 8 3.1.4. External Interfaces Requirements. ......................................... ............................................................... .......................................... .................... 8 3.1.5. System Features. .......................................... ................................................................ ............................................ ............................................. ......................... 9 3.1.6. Other Non-Functional Requirements. ................................ ...................................................... ............................................ ...................... 12 3.2 Project Design ........................................... ................................................................. ............................................ ............................................. ................................. .......... 13 13 3.2.1 Project Model ............................................ .................................................................. ............................................ ............................................. .......................... ... 13 3.2.2 Use Case Diagram.......................... Diagram................................................ ............................................ ............................................ ..................................... ............... 14 3.2.3 Activity Diagram .......................................... ................................................................ ............................................ ............................................ ...................... 15 3.2.4 Class Diagram .................................................. ......................................................................... ............................................. ........................................ .................. 17 3.2.5 Data Base Schema.......................... Schema................................................ ............................................ ............................................ ..................................... ............... 18 3.2.6 Sequence Diagram ............................................ .................................................................. ............................................ ........................................ .................. 20 3.2.7 Interface Design ........................................................... ................................................................................. ............................................. ............................. ...... 21 3.3 Implementation Details ............................................ .................................................................. ............................................ ........................................ .................. 24 3.3.1 User Registration and login Module ............................... ..................................................... ............................................. .......................... ... 24 3.3.2 User Interface Module ......................................... ............................................................... ............................................. ..................................... .............. 25 3.3.3 Create Pool Module .......................................... ................................................................ ............................................ ........................................ .................. 25 3.3.4 Search Pool Module ...................................... ............................................................ ............................................ ............................................ ...................... 26 3.4 Testing ............................................ .................................................................. ............................................ ............................................. ............................................ .....................27 Chapter 4 - Results and Discussion ............................................................. ................................................................................... ........................................ .................. 31 Chapter 5 - Conclusion and a nd Future Scope ........................................... .................................................................. ............................................. ......................... ... 33 Appendix ........................................... ................................................................. ............................................ ............................................ ............................................. ................................. .......... 34 References ............................................ ................................................................... ............................................. ............................................ ............................................. ............................. ...... 36 Acknowledgement .......................................... ................................................................. ............................................. ............................................. ........................................ ................. 37
ii
II.List of Figures
................................................................................................................................... ........................................................................ .. 13 Figure 1: Project Model ............................................................. .............................................................................................................................. ............................................................ 14 Figure 2: Use Case Diagram .................................................................. .............................................................................................................................. ........................................................................ .. 16 Figure 3: Activity Diagram ........................................................ ................................................................................................................................. ........................................................................ .. 17 Figure 4 : Class Diagram ........................................................... ............................................................................................................................. 20 Figure 5: Sequence Diagram .............................................................................................................................. ......................................................................................................................................... 21 Figure 6: Login Page. ......................................................................................................................................... ................................................................................................................................... ........................................................................ .. 21 Figure 7: Main Activity ............................................................. ...................................................................................................................................... ....................................................................... .. 22 Figure 8 : Create Pool ................................................................. ........................................................................................................................................ 22 Figure 9: Search Pool ......................................................................................................................................... Figure 10: Join Pool .................................................................... ......................................................................................................................................... ....................................................................... .. 23 23 ............................................................................................................................................2 3 Figure 11: Register . ............................................................................................................................................
iii
III. List of Tables
........................................................................................... ............................. 6 Table 1: SRS Abbreviation, Notation and Acronym .............................................................. ............................................................................................................... 18 Table 2: Commuter database Schema ................................................................................................................ ....................................................................................................................... ............................................................. 18 Table 3: Offer Database Schema .......................................................... ....................................................................................................................... ............................................................. 19 Table 4: Rider Database Schema .......................................................... .......................................................................................................................................... ....................................................................... .. 30 Table 5: Test Cases .....................................................................
iv
IV. ABBREVATION, NOTATION AND NOMENCLATURE
GUI
Graphical User Interfaces
API
Application Program Interface
SRS
Software Requirement Specification
PHP
Hypertext Preprocessor
DBMS
Data Base Management System
SDK
Software Development Kit
v
Chapter1 -Introduction
Vehicle Sharing System is an Android based application which is based on the concept of Carpooling. Carpool allows sharing of vehicle between people travelling on same route, while going to and/or returning from a particular place. The Parking and Sustainable Transportation Division is continuously working on introducing new incentives to improve alternative methods of transportation. This concept is popular in countries like U.S.A and Canada to a considerable extent. In China, during the 2008 Beijing Olympics, there were instances of the citizens resorting to it when there were a lot of restrictions imposed on the vehicles plying on the roads every day.
A simple Google search revealed an array of websites that offer wide variety of services to facilitate carpooling. Judgment could not be made on the success rate of these endeavors with respect to the number of car users in India. Since reliable information could not be found out regarding the number of people carpooling in the country on any given day, the claims made by the sites were accepted [1]. But the numbers are very less as compared to the other countries.
Vehicle Sharing System is an easy alternative to driving alone, but for others it requires more effort.The Parking and Sustainable Transportation division recognizes the contributions made by carpoolers and has created two incentive programs to encourage carpooling as a sustainable method of transportation. If we were to list out the sustainable ways of transportation, carpooling can be definitely considered to be a viable and comfortable option for those who are not accustomed to the rigors of a public transport system. But, in reality, it is indeed a fuel and expenditure saving option and that the activity requires minimum efforts or infrastructure should be an added bonus [2]. Although it could take some time for any laws related to carpooling to come into effect, it is up to the citizens to take it seriously whenever and wherever possible so that it culminates into reduction in pollution and fuel consumption and ultimately saves the environment from destruction.
1
Vehicle Sharing System is a possible solution to lack of transportation convenience faced by commuter. It is often observed that some people travel with vacant passenger seats. The public transport are some very uncomfortable, congested and unlikely to be in time. So, the vacant seats in the automobiles can be used to help these traveler’s reach their destination. The major obstacles are difficulty of offering and finding rides especially within a short-notice. But this android based application helps solving the problem of finding the automobile owner who are willing to share their vehicle and help the others to reach their destination.
2
Chapter 2 -Literature Survey
Vehicle sharing also known as carpool is two or more commuters sharing a ride in one of their own vehicles. The best carpooling arrangements are very flexible. Usually people arrange carpools in order to save money, protect the environment by burning less fuel/gas or to enjoy each other's company. By having more people using one vehicle, carpooling reduces each person's travel costs such as fuel costs, tolls, and the stress of driving. The other motive behind the development of such an application is to reduce the hardships that are faced by the commuters to reach their destination. Cities with worse traffic, longer commutes and longer rush hour times often have more people who want to carpool. In areas where you find "extreme commuters" (like Mumbai) traveling an hour or more to work every day, there is even more demand for car pooling. In such a system commuters are benefited because they can share gas and toll. Of course, if you accept a carpool, you may need to compromise on your specific work hours in order to make a carpool happen. Conventional
Vehicle-Sharing
has
multiple
issues
associated
with
it.
Carpooling/Vehicle-Sharing is like taking care of health[1].People know that its good, but many end up not doing it after an initial attempt. Some problems are li sted below:
Co-ordination Issues:
Matching the travel time on a daily basis, managing multiple calls can be too taxing in the morning.
Bound by daily car pool commitment:
Carpool becomes a daily or a monthly affair and it becomes difficult for the vehicle owner to say no even when they have some other commitment.
Informal Contract:
A party can drop out of the pact any time as per their convenience.
Safety concerns:
Unavailability of proper verification details of ride sharing partners.
3
Awkward cash exchange:
Discussing money and exchanging cash is extremely awkward, and people having reputed jobs do not prefer this.
Limited circle:
Do not know enough people or are not comfortable with many to initiate a carpool.
So there seems to be a need for a platform which could handle most of these tasks at its end so as to ease the process of carpooling and making it all the more feasible and effective. The platform should be a dynamic, safe and simple Carpooling solution that enables easy cost sharing for car owners when they share empty car seats with fellow commuters Doing analysis of the current market for such platforms for sharing of vehicles we came across a bunch of platforms providing these facilities and features most of them had usually failed. Delving deeper into the analysis of as to why this was the case, reveals that these platforms were built a few years back. Now, few years back the most preferred and feasible way to reach the masses in a country like India would be via the web. Needless to mention mobile devices and the platforms that run them were barely as developed as they are today. And even if there were smartphones/PDAs available in the market, but they catered only to people falling in highincome bracket or to geeks who spent all their money on such devices. This made it very difficult to communicate to the user’s information about carpooli ng and make them use it daily.Only famous platform for mobile devices one could easily recall was Symbian or to the max windows for India. Websites were the only way to go back then owing to these factors. Region-wise analysis threw some light on the fact that other countries such as USA and European countries have accepted carpooling in great numbers as compared to India. This could be a result of consumer behavior in India which needs to be analyzed. [2]
4
Popular current implementations:
Carpooling.com is one such platform which connects people in over 40 countries so they can travel together. Today the site is available in 7 languages: English, French, German, Greek, Italian, Polish and Spanish. But this platform is specifically for European countries and hence India is not on the list. [3] Zimride is another carpooling platform which is gaining some ground in the USA and its platform is still restricted to web.[4] Mebuddie.com is a good operational carpooling system in India covering areas such as Mumbai, but their technology has been implemented only on web platform and has not reached the hand-held platforms.[5] Carpoolworld.com is again a web platform which is one of the leading carpooling implementations but is again specific to just the unites states of America. [6] Ridingo is one such carpooling application which has been made available for android platform and is based in India. But they currently cater to only Bangalore. [7]
5
Chapter 3 - Report on Present Investigation 3.1 Software Requirement Document (SRS) 3.1.1 Introduction 3.1.1.1 Purpose. Aim of this software specification requirements document is to provide a complete description of all of the features that are planned to implement to system and define the expectations from the vehicle sharing project. It also describes how the system operates and how users interact with the application. Project members will utilize this software specification requirements document to define test scenarios according to the mentioned requirements. Besides project manager, quality manager and acquirer use this SRS document for reviewing purposes. 3.1.1.2 Scope of the Project. The Vehicle sharing Project is an android based application which includes user interaction. The project will provide communication environment for users (drivers and customers). Every user has their own profiles and they can have access with given password to the system. The drivers can draw their routes from map in our application. And customers can communicate with the driver via the messaging system and pick their path. After mutual agreement with each other, they record the transportation information to the system. At the end, users can assess each other via feedback system. 3.1.1.3 Intended Audience. Project team members & Users. 3.1.1.4 Definition, Abbreviation and Acronym. The definitions of the terms, which are used in this SRS document, are shown below GUI
Graphical User Interfaces
API
Application Program Interface
SRS
Software Requirement Specification
PHP
Hypertext Preprocessor
DBMS
Data Base Management System
SDK
Software Development Kit Table 1:SRS Abbreviation,Notation and Acronym
6
3.1.1.5. References. [1] IEEE STD 1233-1998, IEEE Guide for Developing System Requirements Specifications. [2] IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements Specifications.
3.1.2. Overall Description. This section gives background information about specific requirements of the android based Vehicle sharing environment to be developed in brief. Although we will not describe every requirement in detail, this section will describe the factors that affect the final product. 3.1.2.1. Product Perspective. Vehicle sharing system will be an independent and self-contained. The constraints which describe how the software operates are listed below: 3.1.2.2. Product Functions. All the use cases are explained below: Sign up: Users need to first register to this application by filling up the required
information like first name, last name, email id, contactno, gender, age, date of birth, username and password. Sign in / Sign out: After signing up for the application the user can sign in / sign out
of the application. Search / Join offer: User when signs in, he/she can search for the offer they are
searching for and can send the joining request. Post offer: Rider will post the offer when he/she will be travelling with the required
details needed for the offer.
View profile: The rider/commuter can check out each other’s profile.
Participate: The commuter can participate in the ride if there is a ride available.
Confirm / Cancel offer: The confirmation/cancellation of the offer solely depends on the rider to accept the request or to cancel it.
Notification: Once the rider confirms/cancels the request the commuter who send the request for joining it will be notified via sms or email. 3.1.2.3. User Classes and Characteristics. All the people who are using Android based smart phones could use this vehicle
sharing
system. We intend to provide accurate results for the users which will be
helpful for
travelling.
7
3.1.3. Operating Environment. 3.1.3.1 Design and Implementation Constraints. Vehicle sharing system is required mutual trust for example user’s security of life must be protected by the government’s law system but there is no legal infrastructure about this driver and customer relation in our country. So, this is an important constraint for Vehicle sharing system. Another constraint is that 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 its operations until the server become available to respond system requests. In addition to these, since the user information is stored in a database and this database can be hacked and user information will be no longer private to the user. To sum up, Vehicle sharing system has constraints in terms of regulatory, reliability, safety and security but these constraints can be manageable. 3.1.3.2 Assumptions and Dependencies. User interface and some functionalities can change during the development process of project. And also new functionalities can be added which is able to change the dependent system requirements.
3.1.4. External Interfaces Requirements. 3.1.4.1 User Interfaces. This software product is developed for drivers and customers.
Product will be
deployed
as android application and all users of the system will access the system
through the
web interface which includes multiple pages according to the system
functionality for
example for login functionality there will be login page. To access the
system, every
user has unique user name and password. In addition, there will be a
database who stores and manipulate all the data about the users. Application will only be the interface for all the user data which stored by database and the execution of provided functionalities. sign up
After the sign up, user information will be transferred to database. In the
process, there will be e-mail verification to verify user information. After that
point, users can register through the web interface. After log in, user will be able to log out whenever he or she wants. 3.1.4.2 Hardware Interfaces. Vehicle sharing system is android based, it would be compatible with all the smartphones having android version 4.2 and can be run on android operating system.
8
3.1.4.3 Software Interfaces. Database management system is required software product for Vehicle sharing system
because all data about system for example user and route information must be
stored in
database for later use and system functionality.
MySQL database management system is used for that purpose and it has nice open source user interface which displays table and rows in well formatted form for developers to create and manage the whole database. Another server that will be used is Google Map Server to provide geographical service
and to visualize transportations. These client and server sides attraction will be handled with Http Requests by
JavaScript and PHP Languages. 3.1.4.4 Communication Interfaces. The system shall send automatic verification e-mail to the user who wants to register to the system. Moreover, in communication between driver and customer, users shall send and receive an e-mail through the e-mail interface. For communication between users, system shall support SMS functionality and users can be able to send and receive
SMS through the remote mobile devices.
3.1.5. System Features. 3.1.5.1 Sign up 3.1.5.1.1 Description Users need to first register to this application by filling up the required information like
first name, last name, email-id ,contactno, gender, age, date of birth, username and password. 3.1.5.1.2 Validity Checks
Input fields like username, password, name, gender, contact no, mail-id aremandatory.
If any one of the fields are missing, he/she can’t register and a warning message will appear. 3.1.5.1.3 Stimulus or response sequence
The commuter opens the application.
User presses the sign up button.
User enters her or his user name, surname, password, contact no and e-mail information.
User checks his or her e-mail account to verify his or her use information. 9
3.1.5.1.4 Error handling/ Response to abnormal situation 3.1.5.2 Sign in/Sign out 3.1.5.2.1 Description After signing up for the application the user can sign in / sign out of the application. 3.1.5.2.2 Validity Checks One has to enter his username and password to sign in to the application. 3.1.5.2.3 Stimulus or response sequence
The user opens the application.
User presses the sign in button.
User enters her or his username and password.
If the user forget his or her account information, he or she get account information via the “forgot your password?” panel under the log in page.
The user can sign out of the application any time. 3.1.5.2.4 Error handling/ Response to abnormal situation
3.1.5.3 Search / Join offer 3.1.5.3.1 Description User when signs in, he/she can search for the of fer they are searching for and can send the joining request. 3.1.5.3.2 Validity Checks
User forgets to fill “from” or “to” input field.
The related warning message is shown to the user to fill the input fields properly.
If user fills the input fields properly.
The available routes will be listed. 3.1.5.3.3 Stimulus or response sequence
User fills “from” input field.
User fills “to” input field.
User presses the search button.
User presses the join button when the ride is available. 3.1.5.3.4 Error handling/ Response to abnormal situation
10
3.1.5.4 Post offer 3.1.5.4.1 Description Rider will post the offer when he/she will be travelling with the required details needed for the offer. 3.1.5.4.2 Validity Checks One has to enter full details of the offer. 3.1.5.4.3 Stimulus or response sequence
Rider shall enter her or his profile page.
Rider shall press add new transportation button.
Add transportation page will be loaded.
Rider enters departure time, available seats and iteration of transportation like “one time” or “periodic”.
User draws a route on the map panel. 3.1.5.4.4 Error handling/ Response to abnormal situation
3.1.5.5 View profile 3.1.5.5.1 Description The rider/commuter can check out each other’s profile. 3.1.5.5.2 Validity Checks 3.1.5.5.3 Stimulus or response sequence
The commuter sends join request and check the profile of the ri der.
The rider can check the profile of the commuter. 3.1.5.5.4 Error handling/ Response to abnormal situation
3.1.5.6 Confirm/cancel offer 3.1.5.6.1 Description The confirmation/cancellation of the offer solely depends on the rider to accept the request or to cancel it. 3.1.5.6.2 Validity Checks
The journey can be confirmed only by the rider.
The offer can be cancelled by the rider with prior information. 3.1.5.6.3 Stimulus or response sequence
Checks the number of request.
Rider confirms the commuter to share a ride if there is a seat available.
Rider can cancel the request if there is no seat available.
11
3.1.5.6.4 Error handling/ Response to abnormal situation 3.1.5.7 Notifications 3.1.5.7.1 Description Once the rider confirms/cancels the request the commuter who sends the request for joining it will be notified via sms or email. 3.1.5.7.2 Validity Checks The notifications will be sent to the commuters and the riders only after they accept or cancel the request. 3.1.5.7.3 Stimulus or response sequence The rider gets the notifications when there is a join in request.Commuter gets notifications for his join in offer whether his sharing offer is confirmed or cancelled. 3.1.5.7.4 Error handling/ Response to abnormal situation
3.1.6. Other Non-Functional Requirements. 3.1.6.1 Performance Requirements. Good response time. 3.1.6.2 Safety Requirements. A commercial database is used for maintaining the database and the application server takes care of the application. In case of failure, re-initialization of the program will be done. Also the software design is being done with modularity in mind so that maintainability can be done efficiently. 3.1.6.3 Security Requirements. Sensitive data will be encrypted before being sent over insecure connections like the internet. 3.1.6.4 Software Quality Attributes. Availability:The system should be available at all times. In case of a hardware failure or database corruption, back up of the database should be retrieved from the server and
saved by the administrator.
12
3.2 Project Design 3.2.1 Project Model The following design outline displays the work flow of the application. It describes how the user is guided while using the application. First user is register to application and then he/she can post/search the offer as per their requirements.
Register to App
Login
Search Carpool
Post Offer
Carpool Details
Participate
Provide Fare
Notify finder
Confirm/ Cancel
View Route (Map)
Figure 1: Project Model
13
Confirm/ Cancel
3.2.2 Use Case Diagram A use case diagram at its simplest is a representation of a user's interaction (commuter and rider) with the system and depicting the specifications of a use case.
In the system, actors are rider creator, commuter and admin.
Register and Login to application.
User can post and search offer to and from server.
User can edit posted offer and Profile once created.
Figure 2: Use Case Diagram
14
3.2.3 Activity Diagram Activity Diagrams are used to illustrates dynamic view of the application. It shows the flow from one activity to another activity within application. An activity shows the set of activities, the sequential or branching flow from one activity and object that act and are acted upon. This activity diagram shows the activity that are performed by the ride creator and participant while using Easy Ride Share application.
15
Figure 3:Activity Diagram
16
3.2.4 Class Diagram The class diagram illustrates all the enitites within the system and shows the interactions between them. The interactons are represented using relationships between objects.These relationships can be one to many or many to many. The attributes and methods associated with each entity is represented along with its object.
Figure 4 : Class Diagram
17
3.2.5 Data Base Schema 3.2.5.1 Commuter
Sr No
Attribute
Data Type
Constraints
1
VSS ID
Integer
Primary key
2
C_uname
Varchar2
Not null
3
Password
Varchar2
Not null
4
Gender
Varchar2
Not null
5
Phone_no
Integer
Not null
6
Location
Varchar2
Not null
Table 2: Commuter database Schema
3.2.5.2 Offer
Sr No
Attribute
Data Type
Constraints
1
Offer_id
Integer
Primary key
2
Date
Date
Not null
3
Carpool_Type
Varchar2
Not null
4
Location
Varchar2
Not null
5
Destination
Varchar2
Not null
6
No_of_Participa
Integer
Not null
nts
Table 3: Offer Database Schema
18
3.2.5.3 Rider Sr No
Attribute
Data Type
Constraints
1
VSS ID
Integer
Primary key
2
R_uname
Varchar2
Not null
3
Password
Varchar2
Not null
4
Gender
Varchar2
Not null
5
Phone_no
Integer
Not null
6
Location
Varchar2
Not null
7
Vehicle_No
Varchar2
Not null
Table 4: Rider Database Schema
19
3.2.6 Sequence Diagram A sequence diagram is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart.This sequence diagram displays how the activity will be performed in step-step by manner and how the messages are exchanged between participant, Ride creator and the system/application.
Figure 5: Sequence Diagram
20
3.2.7 Interface Design Interface Design (UID) or user interface engineering is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user's experience and interaction. This design displays the UI interface of the system i.e. Login Page,Register Page, Search Pool ,Post Pool, Main Activity Page.
3.2.7.1 Login Page
Figure 6: Login Page
3.2.7.2 Main Activity Page
Figure 7: Main Activity
21
3.2.7.3 Create Pool
Figure 8 : Create Pool
3.2.7.4 Search Pool
Figure 9:Search Pool
22
3.2.7.5 Join Pool
Figure 10: Join Pool
3.2.7.6 Register
Figure 11: Register
23
3.3 Implementation Details 3.3.1 User Registration and login Module
This is the start page of the application. The start page contains the textbox in which the user inputs the login and password. If the user is not registered then he can register himself by giving the following required details. All the fields during the registration process are compulsory without them the registration would be incomplete and could cause a security breach in the application. Thelogin page is an gateway for the user to access the functional features of the application.
24
3.3.2 User Interface Module
This is the home page of the application in which it contains options such as create pool, search pool and also my detail.Using the following option the user can create his own pool,Search for a pool and also edit his details.Thus this forms an important page in the application without which it would be impossible to use the application. 3.3.3 Create Pool Module
User can go to the create pool option and then select his source and destination for the journey. After the selection of the location he can view his journey over the google maps using the google map API.This is core of the application where in a rider posts for the ride and without which the carpool would not be created. 25
3.3.4 Search Pool Module
User can also select the appropriate location for his journey and can request for the search and joining of it and as he clicks on proceed he is redirected to another page where he can find the carpools available for him to pick and request for the travel.This forming the core of the Application where the interested rider searches for the relevent pool for the journey and would mainly take care of the comfort,cost and his location accessability with the timing issues in his mind.
26
3.4 Testing
Development of test cases (functional): Performance Analysis OnVarious Testing There are two general categories of testing. Pre implementation and post implementation. The software testing for the process planning system has been done during the pre-implementation stage using various software testing strategies.
Unit Testing The individual modules are tested for proper functioning and are found to be satisfactory as regard to the expected output from the module. The whole work is divided into modules and every module is tested independent of other modules and their functionalities. If the testing of the module requires sub divisions for accurate output they are permissible. The testing is carried out during programming stage itself. There are some validation checks for verifying the data input given by the user for the authentication purpose. The errors could be identified and debugged. Interface Testing After the modules are individually tested we confine the testing process to each and every interface which has been developed in the application since every interface is a master screen. During the interface testing, the GUI interfaces are tested accordingly as per their functionality prescribed. This testing would ensure the proper functioning of the interfaces as per the requirements demanded. Interface testing would improve the performance of the system. Black Box Testing This testing focuses on the functional requirements of the software and also it enables the Software engineer to drive the sets of input conditions that will fully exercise functional requirements for a program. It attempts to find error such as incorrect missing functions, interface errors, errors in data structures or external database, access, performance errors, initialization and termination errors. The software has been tested to drive a set of cases that satisfy the user requirements. Integrated Testing The need for the integrated testing is to find the overall system performance, while testing the whole application there are chances of reoccurrence of errors because, previously all the testing techniques were used to test some individual modules. Now we would integrate all of them and would test for their compatibility as a whole for all the interfaces and the charting process because they are all interdependent on each other. The application has been tested for various kinds of inputs and has successfully passed.
27
ID
TC1
Validation Testing At the culmination of Black Box testing, software is completely assembled as a package and tested as a whole unit. Validation testing is where the requirements established as part of the software requirements analysis are validated against the software that has been constructed. It ensures that the software meets all the functional, behavioral and performance requirements. The application was tested on various inputs which authenticates the user as specified by the organization.
Objective
Steps/Description
Input
Expected
Actual
output
output
Result
Validate
To verify that
String
An error
An error
Succes
Register
fields like e-mail
values
message
message
sful
and phone no is
from the
must be
is
fill properly.
user
displayed
displayed
showing
.
Remark
enter 10 no’s for phone no. TC2
Validate
To verify that no
Login
data fields are left empty.
Alert
String
Alert
values
comes to
from the
fill all
user
the
all the
fields.
fields is
message]
Succes sful
} to fill
displayed .
TC3
Validate post offer
An error
An error
message
message
must be
to fill all
displayed
the fields
workin
vacancy are filled
to fill all
correctly
g
correctly.
thecorrec
is
succesf
t fields
displayed
ully
To verify that
Source
fields like source,
and
destination, date,
destinatio
time and no of
n location
28
Succes
AutoCo
sful
mplete Adapter
. TC4
Validate search offer
TC5
To verify that user has enter the fields like source, destination, pick up and drop point, date and time correctly.
An error
Source
An error
and
message
Destinati-
must be
on
displayed
the fields
workin
location
to fill all
correctly
g
the
is
correct
displayed
fields
.
message
Succes
Google
sful
geocodi
to fill all
ng API
Google
To get the route
Source
To get
Less
Failed
Incomp
maps for
description for
and
the exact
efficient
lete
direction
the commuter
destinatio
location
in
google
n address
view
location
map
viewing
informa tion about some areas in mumba i
TC6
Search
Gives details of
Input
Result
Result
Succes
Result page
all the pools
from the
should
displays
sful
coming in
search
correctly
the
commuters
page
display
required
the same
pool
searched route
route pools TC7
Join Pool
Gives the
Selection
The
The
Succes
confirmation that
of the
required
joining of
sful
the user has
pool from pool
the
joined the pool
user
should
required
only be
pool done
selected
successfu lly
29
TC8
View Pool
Displays the
Selection
The
Correct
Succes
uploaded pool or
of the
selected
detail
sful
the pool joined by
option
pool
about the
option
pool is
and
displayed
the user.
detail should be displayed
Table 5:Test Cases
Test Case TC5: Since the given test case failed during the testing phase the given functionalit y for the Google maps for the direction was then combined with the LatLang API and PolyLine API to get the correct details and location for the required source and destination which is accurate enough to get and display the details on the map correctl y.
30
Chapter 4-Results and Discussion
The commuters will register using the developed application. Vehicle owner will give source and destination (including the actual path), number of seats, vehicle no. and starting time as input to application. The user who is going to travel by his/her vehicle will mention source, destination along with the route selected. He will also mention the capacity of vehicle. All the updates would happen instantly without fail. Now the other side of application, the commuter who want ride will subscribe to the application. During subscription a fellow will enter source and destination. This request will be sent to the application. The commuter will respond with vehicle available on that route. Vehicle number, owners name, seats available etc. will be visible to the commuter. The user (passenger) who finds the path convenient will apply for the trip. The vehicle owner on the other side will approve the request.
Vehicle Sharing Application would also overcome the old Systems shortcoming which used to restrict the users from carpooling. Commuters would not need to access the website for finding available carpool offers again and in this mobile world and hence making the carpool a lot easier. Contacting each other by call or e-mail would be risky while the driver is driving and hence a single button push application can remove this risk. Commuter need not has to call back in-case they won’t participate as facility would be provided in the application to cancel the booking. Drivers carry the additional burden of potential legal action from passengers in case of an accident. When carpooling, it becomes difficult to run errands on the way to and from the common locations. Tends to be complicated to reliably organize and is difficult to maintain, due to changing travel patterns and needs. Sign mark locations outside of their metro stops and large bus stations where drivers can share rides with other passengers in an orderly fashion. While there were rules and protocols that participants follow, generally, the unstructured approach to carpooling is what appeals to many of the participants. On any given day, a participant can opt to casual carpool or not without regard to commitments and
31
obligations; in fact, it is this flexibility with regard to personal schedules that is highly valued by many participants.
Safety is a primary concern among new casual carpoolers. This was especially the case among women, who experienced initial apprehension and nervousness, particularly over the prospect of being the only woman in a car with men. Participants minimized this concern by first:
Riding with a known registered user for the first fe w weeks or months.
Participating as a driver until familiar with the process and their commute.
Carpooling is viewed as a more realistic alternative for lower socio-economic classes or for those who, due to their age, do not have their own private vehicle or do not have the resources to use it during the week.Increasing flexibility through carpooling with nonfamiliar persons requires a system that provides astrong trust basis amongst carpoolers, and this has lead to the proposal of a carpooling club structure. It is grounded in psychology and social behavior research which points to these interaction platforms as being capable of fostering friendship and trust relations that are key aspects for allowing more resilient groups to be formed.
32
Chapter 5-Conclusion and Future Scope Vehicle Sharing System is very effective means to reduce pollution and the congestion of vehicles in cities. It also provides an eco-friendly way to travel. As today most people prefer private vehicle to travel due to delay caused in public transport system and luxuries provided by private vehicles. Vehicle Sharing System provides rider to create and post the ride as per his/her requirements andCommuters to search the available rides by providing pick-up and drop point as mandatory fields. Thus, we can successfully reduce the long conversations needed for normal car pool events. Vehicle Sharing System aims at identifying suitable matches between commuters requesting rideshare services with appropriate drivers available to share vehicle. Preregistration ensures that only identified people get into the vehicle so that trust can be established. The ridesharing preferences and characteristic considered in this project are: age, gender as well as the maximum number of people sharing a ride Development for other mobile Operating Systems so that users across any mobile operating system can access the carpool features of our application and get integrated access to users registered using mobile Corporate Ride Sharing Today a large number of people working in multi-national companies generally have their own vehicle for travelling from their home to their place of work, so instead we can have a feature for corporate ride sharing where people within an organization can directly find and carpool with their co-workers, since they belong to the same organization the fear of strangers will reduce to a greater extent. Currently the application is limited for carpooling with other people for Mumbai only, later on Vehicle Sharing application can be created to support different cities considering the legal factors of that state. This simulated approach to a human-based system such ascarpooling clubs is pertinent and advantageous. Thedevelopment of these experiences will help determine theviability of the systems in terms of the identification ofthe most suitable geographic areas in which to invest inthe promotion of this mode, and the development of incentives.
33
Appendix
A Android Development Tools: ADT is a plug-in for the Eclipse IDE that is designed to give
you a powerful, integrated environment in which to build Android applications.ADT extends the capabilities of Eclipse to set up new Android projects, create an application UI, add packages, debug your applications using the Android SDK tools, and even export signed (or unsigned) .apk files in order to distribute your application. Application Programming Interface : API is a protocol intended to be used as an interface
by software components to communicate with each other. An API is a library that may include specification for routines, data structures, object classes, and variables. Android Application Package: APK is the file format used to distribute and install
application software and middleware onto Google's Android operating system. To make an APK file, a program for Android is first compiled, and then all of its parts are packaged into one file. C Carpooling System: A carpooling system is a vehicle sharing system in which a user can
share a ride with other commuters on a similar routes and helps in reducing the fuel cost and traffic. Commuter: The commuters are the people who travel to a particular destination using
carpooling system. J Join Offer: The commuters will confirm that they will join the ride by using join offer
option. M MySQL: MySQL is an open source Relational Database Management System (RDBMS)
that runs as a server providing multi-user access to a number of databases. MySQL databases, build database structures, back up data, inspect status, and work with data records.
34
P PHP: PHP is a server-side scripting language designed for web development but also used as
a general-purpose programming language. PHP code is interpreted by a web server with a PHP processor module which generates the resulting web page. Post Offer: The rider will post the route from source to destination using post offer option. R Rider: A rider is a person who drives the car and also is one of the commuters. S Search offer: The commuter will search whether there are any riders travelling by using
search offer option. Software Development Kit : SDK is typically a set of software development tools that
allows for the creation of applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, or similar development platform.
35
References
Roubina Pyanee, "NuCarpool - Real-Time Dynamic Carpooling App for Mauritius 1] using Push Service," p. 5, J an 2013. Wikipedia Inc. (2014, Sep) wikipedia. [Online]. http://www.wikipedia.com 2] Carpooling Inc. (2014, Aug) carpooling.com | Europe's largest carpooling network. 3] [Online]. http://www.carpooling.com/ ZIMRIDE. (2014, Aug) Ridesharing, carpooling and buses - Zimride. [Online]. 4] http://www.zimride.com/ ME
buddie.
(2014,
Aug)
Mebuddie
-
Lets
go
buddie.
[Online].
Rideshare.
[Online].
5] http://www.mebuddie.com/home/carpool Carpool
Word
Inc.
(2014,
Aug)
Carpool
6] https://www.carpoolworld.com/ RIDINGO. (2014, Aug) Ridingo - Ride Sharing, Carpooling - in Bangalore and 7] soon in other major Indian metros. [Online]. https://www.ridingo.com/
36
