Skip to content

Passenger Functionalities

Ediz Genc edited this page May 26, 2021 · 1 revision

Summary

The passenger shall have a user interface to be able to ask the bus to stop at a station.


Functional Requirements

  1. Passengers shall be directed to the appropriate UI upon identification.
  2. Passengers shall have the ability to see which stops are upcoming.
  3. Passengers shall be able to see the exhaustive list of the station line.
  4. Passengers shall have the ability to request the bus to stop.
  5. Only passengers of the bus shall be granted the opportunity to request a stop. (barcode just as an assumption)!
  6. Passengers shall be notified if they have arrived at their stop.
  7. Passengers shall see how many minutes left to reach their stop. (vote to nix as this requires knowledge of position)
  8. Passengers shall have the ability to request longer alighting times.

Non-Functional Requirements

  1. The app interface shall be easy to use and the buttons are clear.
  2. Asking for a bus stop shall be executed fast and immediately.

Assumptions

  1. All passengers can use a mobile phone and be able to register an account.
  2. All passengers can sign in to their accounts.
  3. The buses have barcode badges so the app can scan them.
  4. All passengers requesting to stop are boarded on the bus.

Clone this wiki locally