4.4 Main Use-Case Diagram For Vowcabs Passenger Application

4.4 Main Use-case Diagram The main Use-case diagram for “VowCabs Passenger app” shows how the user can access different modules of the application. The user has to first login. Later user can use the different operation of the application. Fig 4.3 Main Use-case diagram for “VowCabs Passenger Application” Passengers are the users of this application. Passengers can register, login, create booking; cancel booking, select the car, track his trip, can use panic button, view his Invoice bill. Chapter 5
DETAILED DESIGN
5.1 Detailed Use Case Diagram The following sub sections shows the detailed use case diagrams for each of the major use cases represented in the main use case diagram.
5.1.1 Use-case for Passengers Fig 5.1.1 Passenger
Password varchar Login Password NOT NULL
Gender char Gender NOT NULL del_flg char Delete flag NOT NULL r_cre_time datetime Profile creation time NOT NULL
Validate char Validated or not NOT NULL
GeoPlaceId varchar location NOT NULL
AlterPhoneNo varchar Alternate phone number NOT NULL
FB_id varchar Facebook Id NOT NULL
GPlus_id varchar GooglePlus Id NOT NULL
BonusAmt numeric Credits/Money NOT NULL

Table 5.3 Customer Database CustomerAccount Table
Field Name Data Types Description Remark id numeric Customer Account ID Primary Key
CustId numeric Customer ID NOT NULL
Amount numeric Balance in the Account NOT NULL
AmtType varchar Credits/balance NOT NULL
Balance numeric Remaining Balance in the Account NOT NULL
Description varchar Description of the user NOT NULL r_cre_date datetime Account created date NOT NULL

Table 5.3 CustomerAccount Database
VehicleCategory Table
Field Name Data Types Description Remark
VehicleCategoryId numeric Emai- id of user Primary Key
CategoryName Varchar List of resume NOT NULL r_cre_date datetime Account created date NOT NULL

Table 5.4 Vehicle Category Database
TrackTrip Table
Field Name Data Types Description Remark
TripId numeric Trip id NOT NULL
TrackId numeric Track id NOT
This API automatically handles access to Google Maps servers, data downloading, map display, and response to map gestures. For this we have to install Google play services SDK. Once this has been installed then we have to add the Google play services version to the app’s manifest file.

Fig 6.2 Google play services version code
Later we should get an android certificate and the Google Maps API key from the web site https://code.google.com/apis/console/. Add the Google Map API key to manifest file.

Fig 6.3 Google Map API code
6.2.2 Android Support Libraries Inside the ADT tool there is an option called window. Inside window select Android SDK Manager and download the Android 4.2 API.
6.2.3 Application Permissions o Android.permission.CAMERA o Android.permission.WRITE_EXTERNAL_STORAGE o Android.permission.INTERNET o Android.permission.ACCESS_NETWORK_STATE

6.2.3 Effectively and Efficiently

The App uses SJF (Shortest-Job-First) Algorithm to find the nearest taxi available to the passengers.

All the data are stored and retrieved to and from server through API calls; the app uses MVC (Model-view-Controller) architecture which is a three tier architecture. The App uses REST api calls.
6.3 Screen Shots Fig 6.1 Loading page of VowCabs Application

Fig 6.2 Signup to VowCabs