Functional requirements - SuperTurban/ekm_mobiilposm2ng GitHub Wiki

Webapp

  1. Administrator should be able to log in. UC-1 UC-2
  2. Administrator should be able to create games. UC-1
  3. Administrator should be able to create destinations and add destinations to a game. UC-2
  4. Administrator should be able to select coordinates from a map. UC-2
  5. Challenges are questions or some other tasks like uploading a photo(?). Questions have answers, that administrator should be able to enter. UC-2
  6. Administrator should be able to edit destinations. UC-2
  7. Administrator should be able to activate/deactivate games. UC-1
  8. Administrator should be able to see leaderboards. UC-5.1
  9. Administrator should be able to log out. UC-1 UC-2
  10. Administrator should be able to get the contacts of a user. UC-5.1

Mobile application

  1. User shall choose a username and an email when opening the app the first time. UC-3
    1. The user can't continue if username and email haven't been inserted.
  2. User should see a map which contains points of destination and should be able to navigate to them. UC-3
    1. If the user has joined more than 1 game, then points of destination of all games are displayed at once on the map.
    2. If the user has completed a task in a point of destination, then the point of interest will not be displayed on the map. UC-4
  3. When the user clicks on a point of destination, a popup appears which contains a title, photo and a short description of the place.
  4. User should be able to join at least one game. UC-3
  5. User should be able to see a real-time leaderboard for each game. UC5.2
    1. User doesn't have to join any games in order to see the leaderboards.
    2. A leaderboard contains top 10 users who have gathered the most points in a game.
    3. The leaderboard contains information: user's username and their points.
  6. When the user has reached a destination point, the user should be able to read a text paragraph about the destination point. UC-4
  7. When the user has reached a destination point, the user should be able to listen to an audio clip about the destination point. UC-4
  8. User should be able to re-play and scroll the audio clip.
  9. When the user has reached a destination point, the user should be able to see (a) picture(s) about the destination point. UC-4
  10. User should be able to get a task after the information is skipped by the user (All possible task types are defined in functional requirements of the web application). UC-4
  11. If the user has chosen game(s), the destination points of the game(s) appear on the map. Points from different games have different colors/symbols. UC-3