Use Case: Area of Plantings

Summary

  • Scope: Plants Layer
  • Level: User Goal
  • Actors: App User
  • Brief: The user can add, edit, move and delete area of plantings in their map in the plants layer.
  • Assignee: Paul

Scenarios

  • Precondition: The user has opened the app and has selected the plants layer.
  • Main success scenario:
    • While adding a plant, while holding the mouse, the user can draw a rectangle.
    • The size of the arena and the number of plantings is shown next to the mouse.
  • Alternative scenario: The user accidentally drew a wrong size of the area:
    • and uses the app's undo function to correct the mistake, and
    • is able to change the size as wanted.
  • Error scenario:
    • The user attempts to add, move or edit an area of plantings but the app is experiencing technical difficulties and is unable to complete the request, displaying an error message.
    • There is an error in the app's plant relationship indication and the lines connecting the plants are not displayed correctly. In this case, the app displays an error message.
  • Postcondition:
    • The user's map includes the added, edited, moved or deleted area of plantings as desired.
    • If constraints are violated for the place where an area of plantings was added or moved, relations get added (or removed) to (from) the relation layer.
  • Non-functional Constraints:
    • Partial offline availability: editing attributes, especially for planting and harvesting
    • Supports alternatives
    • Performance: more than 10000 elements per year and per alternative should be usable without noticeable delays and acceptable memory overhead (area of plantings should count as one element)