Algorithm based share taxi TANNAE

This service provides taxi service which passengers can ride taxi together with other passengers.

Server will match with passengers that moves on similar path.

The main purpose is to pay low price than general taxi service.

Development Plan

• Topic

TANNAE project is a updated taxi service which provides sharing service.  

Passengers can share same taxi which moves on similar path.   

When single service ends passengers who shared same taxi pays the total fee in proportion to distance.  

By this service passengers will pay 40~50% lower price than using normal taxi service.  

• Requirements

Main service : Allows passenger to use the service and drivers can use navigation.  

Sub service : Provides account|lost & found|QnA(FAQ)|history|charge services.   

• Schedule

  

• Tools

  • Client[Android]

  IDE : Android Studio    
  
  Language : Java   
  
  UI design : XML     
  

  • Server[AWS EC2 Ubuntu]

  IDE : Visual Studio Code    
  
  Framework : Express.js(Node.js)   
  
  Language : Javascript
  
  Database : InnoDB engine based MySQL
  

  • Network Communication(HTTP)

  Retrofit2 : Client(request) to Server(response) communication library    
  
  Socket.io : Bi-directional communication library    
  

  • Code Manage

  GitHub 
  

• Team

Choi Jae Won[Leader - Back-end Developer]

Server & Algorithm Develop  
  
Build Database 
  
Client-Server Network Develop

Kim Dong Hyun[Front-end UI Developer]

UI/UX Design Develop
  
Map Develop

Lee Seung Chan[Front-end Java Developer]

Client View & Event handler Develop  
  
SharedPreferences Develop

Analysis

• Requirements Statement

  • Functional Requirement

  Function for Account    : Sign In | Sign Out | Register | Withdrawal | Find Account | Edit Account
  
  Function for Driver     : Check service request | Change operation status
  
  Function for Passenger  : Request Service | Rate driver
  
  Function for User       : Lost & Found | QnA(FAQ) | Check History | Charge point
  

  • Non-Functional Requirement

  Client/Server application   : Project is developed based on Client/Server.
  
  User Familiarity            : Develop Ui/UX intuitively for easy using.
  
  System Scalability          : Easy maintenance
  
  System Connectivity         : Server must track users position and update database in real time
  
  System Response Speed       : Response time must be faster than 1s for single request
  
  Security                    : Users private info must be secured
  

• Use Case

  • Use Case Diagram

  

  • Use Case Description

  

• Diagram

  • Sequence Diagram

  

  • Screen FLow Diagram

  

  • Class Diagram

  

Design

• Diagram

  • Class Diagram

  

  • Sequence Diagram[Example(Payment & Assessment)]

  

• User Interface

• Database Table

Implementation

• Link

  Android Code Link
  https://github.com/codesver/Capstone/tree/master/TANNAE

  Server Code Link
  https://github.com/codesver/Capstone/tree/master/Server

• Structure

• Implementation Size

• Demo
  https://user-images.githubusercontent.com/87649850/174003448-78cb473b-f622-4312-b6eb-e537aea6a30f.mp4

• Efficiency

  • Test Method

    Number of test case is 100 and the method of testing is as follows. There are three passengers who rides same taxi for service.
  Single test case ends when all three passengers get on and get off. The order in which service is requested remains the same,
  but all cases of boarding and getting off positions for each passenger are tested. In addition, since the final fee is settled in
  proportion to the distance, the test is conducted in consideration of the distance, and the service use area is limited to Gwangju.
  

  • Test Result

    As a result of creating and testing of 100 test cases, the rate discount rate for the first service requester is 43%.
  The rate discount rate for the second service requester is 52%. The rate discount rate for the third service requester is 46%,
  and the average discount rate is 46%. This figure corresponds to 40-50% or more of the initially set rate discount rate,
  and it is judged that the algorithm has been implemented successfully.
  
    The reason why the discount rate for the second passenger is greater than that of the other two passengers is
  that the first passenger and the third passenger have an average number of solo rides at the beginning and end,
  while the second passenger does not have a relatively large number of solo rides in more tests. For this reason,
  Version 2.0 is expected to reduce the rate ratio of first and last passengers and to reduce the rate burden of first and last
  passengers by applying a method of calculating the rate that other users share.