Use Case: Map Collaboration

Summary

• Scope: Map Collaboration
• Level: User Goal
• Actors: Map Owner, Collaborator
• Brief: Enable collaborators to modify a map.
• Assignee: Peter

Scenarios

• Precondition:
  • A map owner creates a map or has created a map.
  • At least one collaborator is registered in Keycloak.
• Main success scenario:
  • The map owner chooses if the map is open to be viewed by every registered user or member (public/protected/private).
  • The map owner searches for collaborators by their name.
  • The map owner adds a collaborator found before (repeated as needed).
• Alternative scenario:
  • The map owner removes a previously added collaborator.
• Error scenario: The app can't send an invitation to a requested collaborator through network issues. In this case, the map owner should be informed by an error message and is prompted to try again.
• Postcondition:
  • Collaborators can modify the map like it is one of their own.
  • Collaborators cannot modify map properties.
• Non-functional Constraints:
  • 30 collaborators can be added on one map.