Skip to content

Home

Jump to bottom
mss8087 edited this page Oct 7, 2019 · 7 revisions

Project Abstract

In the morning, if you look around SNU station and Nokdu street, it is not difficult to see a long line of students waiting for the SNU shuttle bus. On a bad day, it may take around 20~30 minutes to get to class. But taking a taxi just to get to class could be a financial burden. The clock is ticking, and the professor will check the attendance as soon as class starts. This is when Ya-Ta can be a life-saver. Ya-Ta helps students who need to urgently get to class. Within ten minutes, Ya-Ta groups students with these similar, urgent, needs, and grabs a taxi for them.

How does Ya-Ta makes it possible? From the taxi driver's point of view, Ya-Ta provides financial incentives in addition to the default charge, making Ya-Ta calls an attractive option. From the student's point of view, Ya-Ta satisfies the needs to make it to class in time through luring taxi drivers and the need to save money through a carpool system.

Document Revision History

--

Rev. 1.0 2019-10-01 - initial version

Customer

  • Students located around SNU who need to urgently grab a taxi to SNU
    • Students who need to get to class on time
    • Students too urgent to wait in line for the shuttle bus
  • Students located around SNU who need to inexpensively grab a taxi to SNU
    • Students who need to get to the dormitories after bus hours
  • Students located on SNU who need to leave campus
    • Students who missed the last shuttle bus leaving campus (11:10pm)

Competitive Landscape

Competitive Service

Competitive analysis

Other services which provide a similar carpool system have two passengers at most. Also the probability of finding someone around your current location who has a similar destination will be very low. For this reason, finding a carpool group will require some waiting time, and no matching groups will be found in the worst case, leaving the user with a wasted ten minutes.

Ya-Ta, on the other hand, has a definite pool of demand. The shuttle bus lines every morning are strong proof. A fixed departure point and destination may limit the flexibility of the system, but it may act as a hub where users and potential users can gather to use our service. With this strong demand pool, it will not take long to find a group of four people, greatly reducing taxi fares per passenger. Loss of time waiting for a group will be minimum. Also taxi drivers will benefit from an extra incentive, making Ya-Ta calls a high priority. In return, customer users will benefit from quick matching.

User Stories

Request Taxi Call

Actors

Student who wants to quickly go to campus

Precondition

The student has to be a registered user and be logged in

Trigger

Customer user goes to "Request" page.

Scenario

Request: Success

  1. Customer user is on "Request" page.
  2. Customer user checks desired departure point by clicking corresponding "From" checkbox.
  3. Customer user checks desired destination by clicking corresponding "To" checkbox.
  4. Customer user checks desired minimum number of passengers by clicking corresponding "Passenger Option" checkbox.
  5. The estimated fare is shown on the "Estimated Fare" field.
  6. Customer user clicks the "Submit" button.
  7. On clicking "Submit", customer user moves to "Waiting" page.

Exceptions:

  1. Customer user does not fill out "From" field.
  2. Customer user does not fill out "To" field.
  3. Customer user does not fill out "Passenger Option" field.

Acceptance Tests:

  1. Given the customer user has clicked the desired "From" checkbox, the selected location should be enlarged on the map.
  2. Given the customer user has clicked the desired "To" checkbox, the "From-To" route should be shown on the map.
  3. Given the customer user has clicked the desired "Passenger Option" checkbox, the expected fee should be printed on the screen.
  4. Given the customer user has filled out all required fields, the user should move to "Waiting" page.
  5. On clicking "Submit", customer user moves to "Waiting" page.

Request: Failure

  1. Customer user is on the "Request" page.
  2. Customer user checks desired departure point by clicking corresponding "From" checkbox.
  3. Customer user checks desired destination by clicking corresponding "To" checkbox.
  4. Customer user checks desired minimum number of passengers by clicking corresponding "Passenger Option" checkbox.
  5. Customer user clicks the "Submit" button.
  6. An alert message informs the customer user of insufficient YaTa-Pay money.

Exceptions:

  1. Same as Scenario 1

Acceptance Tests:

  1. Same as Scenario 1
  2. On closing the pop-up, the customer user should return to "Request" page.

Get On Taxi

Actors

Student who wants to quickly go to campus

Precondition

A group of passengers and driver have been formed. The customer and driver user move to "Group" page.

Trigger

Customer user clicks "On Taxi" button.

Scenario

All passengers including customer user have arrived at the departure point before the set departure time.

  1. The departure point and the driver user's current location is shown on the map.
  2. The driver user info and license plate number is shown below the map.
  3. The time remaining before departure is shown below the driver user info.
  4. The "On Taxi" button becomes activated once it becomes departure time.
  5. Customer users get on the taxi and click "On Taxi" button.
  6. As taxi departs, customer users move to "Detail" page.

Exceptions: None

Acceptance Tests:

  1. Given that the departure time has passed, the "On Taxi" button becomes activated.
  2. When the customer user clicks the "On Taxi" button.
  3. The customer user moves to "Detail" page.

Taxi has departed before customer user could arrive at the departure point.

Exceptions:

  1. The departure point and the driver user's current location is shown on the map.
  2. The driver user info and license plate number is shown below the map.
  3. The time remaining before departure is shown below the driver user info.
  4. The "On Taxi" button becomes activated once it becomes departure time.
  5. As taxi departs, customer users move to "Detail" page.

Acceptance Tests:

  1. Given that the departure time has passed, the "On Taxi" button becomes activated.
  2. When the customer user clicks the "On Taxi" button.
  3. The customer user moves to "Detail" page.

Taxi Departure

Actors

Driver user

Precondition

Driver user should be matched to customer user passenger group through clicking "Accept" button or confirming through voice recognition.

Trigger

Driver user clicks "Go" button at the bottom of "Group" page.

Scenario

Driver user tries to provide taxi service

  1. Driver user sees his/her current location and departure point on the map.
  2. Driver user sees customer passenger info, and the number of currently on-board passengers to total expected passengers.
  3. Driver user sees departure time.
  4. As current time passes departure time, or all customer user passengers click "On Taxi" button, the "Go" button becomes activated.

Acceptance Test:

  1. Given current time has passed departure time, the "Go" button should be activated.
  2. Given the number of currently on-board passengers equals the number of total expected passengers, the "Go" button should be activated.
  3. When the "Go" button is clicked, the driver user should go to "Detail" page.

Taxi Driver Selects Request

Actors

Driver user

Precondition

Driver user must be logged in.

Trigger

Driver user goes to "Call" page.

Scenario

"Accept" Button

  1. A taxi request is shown on the screen.
  2. The screen shows the departure point and destination of the request, estimated fare, and a map shows the location of the departure point.
  3. The screen shows a new request every 5 seconds.
  4. An "Accept" button is on the lower part of the screen.
  5. Driver user clicks "Accept" button.
  6. On clicking "Accept" button, driver user should move to "Group" page.

Exception

Driver user does not click "Accept" button.

Acceptance Test

  1. Given driver user clicks "Accept" button
  2. Driver user moves to "Group" page.

Voice Recognition System

  1. A taxi request is shown on the screen.
  2. The screen shows the departure point and destination of the request, estimated fare, and a map shows the location of the departure point.
  3. The screen shows a new request every 5 seconds.
  4. An "Accept" button is on the lower part of the screen.
  5. Driver user speaks the activation keyword.
  6. On the voice recognition system recognizing the keyword, driver user should move to "Group" page.

Exception

Driver user does not say the keyword.

Acceptance test

  1. When driver user says something different than the keyword
  2. Driver user should not move to "Group" page
  3. When driver user says the keyword
  4. Driver should move to "Group" page.

The story of future iterations

  1. Charge page - YaTa-pay storyline
  2. Register page
  3. User profile page

User Interface Requirements

  1. Intro page

    • introduction (text)
    • tutorial (text)
    • start (button)

  2. login page

    • ID (input)
    • password (input)
    • login(button)

  3. Request page

    • From (checkbox)
    • To (checkbox)
    • Option (checkbox)

  4. Waiting page

    • waiting info (text)
    • waiting time (text)
    • cancel (button)

  5. Call page

    • MAP API - From location
    • From (text)
    • To (text)
    • Estimated Fare (text)
    • Accept (button)

  6. Group page

    Customer User's view

    • Map API - driver location, start point
    • Driver User info (text)
    • Department time (text)
    • On Taxi (button)

    Driver User's view

    • Map API - driver location, start point
    • Customer User info (text)
    • Department time (text)
    • Go (button)

  7. Detail page

    Customer User's view

    • Estimated Time of Arrival (text)
    • Estimated Fare (text)

    Driver User's view

    • Fare (input)
    • Confirm (button)

  8. Final page

    Customer User's view

    • Taxi Fare (text)
    • Your cost (text)
    • You saved (text)
    • Current YaTa-pay (text)
    • Go back to home (button)

    Driver User's view

    • Taxi Fare (text)
    • Additional incentive (text)
    • Go back to home (button)

image

Clone this wiki locally