Use Case: Crop Rotation

Summary

  • Scope: Crop Rotation
  • Level: User Goal
  • Actors: App User, Plant A, Plant B
  • Brief: The user gets information based on earlier or later plants for each location.
  • Assignee: Lukas

Scenarios

  • Precondition:
    • The user has opened the app and sees either Heatmap or Relation Layer.
    • A plant A has been on the same spot in the past as plant B is now.
    • This plant A has a removal date before the adding date of plant B (remove_date of A < add_date of B).
    • There is a positive or negative crop rotation effect between plant A and B, which can last from half a year to a predefined number of years.
  • Main success scenario:
    • A positive effect is shown green in the heatmap on this spot before plant B is planted.
    • A weak negative effect (within max in the relation table) is shown at least orange in the heatmap on this spot before plant B is planted.
    • A strong negative effect (within min in the relation table) is shown at least orange in the heatmap on this spot before plant B is planted.
    • The relation layer shows an icon with text describing the specific crop rotation effect between plant A and B, e.g.:
      • "Strong negative crop rotation effect: Cabbage shouldn't be placed within the same year on the same spot."
      • "Nachteilige Fruchtfolge: Kohl braucht ein Jahr Anbaupause bevor wieder Kohl gepflanzt werden soll."
  • Alternative scenario:
    • Without data or relation for A or B, nothing happens for the user and no additional information is provided.
  • Error scenario:
  • Postcondition:
  • Linked Use Cases:
  • Notes: