Use Case: Soil Layer

Summary

  • Scope: pH Values Layer
  • Level: User Goal
  • Actors: App User
  • Brief: The user can add, move, remove, delete and edit areas of pH values and soil weight class in their map using the soil layer
  • Assignee: Lukas

Scenarios

  • Precondition: The user has opened the app and has selected the soil texture layer.
  • Main success scenario: The user successfully adds, edits, moves, removes and deletes soil texture areas in the soil texture layer. For example: sandy hills, loamy spot etc. This includes positioning the areas in the appropriate location.
    • Default is to not consider it for heatmap.
    • Sandy, loamy, clay and sealed areas can be added by a small or big brush to draw on the soil texture layer.
      • Sand (Sand): cannot be rolled to a ribbon even if moist (kann nicht zu einer Wurst gerollt werden, selbst wenn feucht)
      • Loam (Lehm): there is sound when rubbing near your ears or sand can also be felt on the tongue
      • Clay (Ton): you can form the moist ribbon to a ring (Handtellergroß), without breaking it
      • Sealed (Versiegelt): no earth on the surface (keine Erde auf der Oberfläche)
  • Heatmap:
    • per default: no information
    • red: plant does not match with soil texture information
    • green: plant matches with soil texture information
  • Alternative scenario:
    • The user accidentally edits, moves or removes an element and uses undo to correct the mistake.
    • The user accidentally adds an element and deletes it with the "delete" or "undo" functionality.
  • Error scenario: The user attempts to edit a soil weight class or pH value in a area that is not within the acceptable range and the app displays an error message. The previous values stay unmodified.
  • Postcondition: The user's map includes the added, moved or edited pH value areas as desired.
  • Non-functional Constraints:
    • is a brushing layer
    • Performance: Map sizes with more than 1ha in 100 raster elements (in 1a=100m²) per year with 4 values per raster element should be usable without noticeable delays and acceptable memory overhead

Out of scope

  • To be done in the future:
    • ph-values and yield grade
      1. First the user globally tells a pH topsoil value, soil weight and yield grade.
      2. Then the user successfully adds, moves, removes, deletes and edits:
        • pH value areas for topsoil
        • pH value areas for subsoil
        • soil weight class
        • yield grade in their map using the soil layer, where it differs from the global value. This includes positioning the pH value areas in the appropriate locations and adjusting their values as needed. A big brush is used to draw on the soil layer.
      3. The user can check the values at individual spots by clicking on it.
  • Notes:
    • pH values have one significant digit, not more (e.g. 4.5, 6.7, 8.4)
  • Non-functional Constraints:
    • The app must clearly communicate to the user the constraints for editing pH values in the soil layer.