Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

Add use cases for Crop Rotation #1292

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions doc/usecases/draft/crop_rotation.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Use Case: Crop Rotation

## Summary

- **Scope:** Crop Rotation
- **Level:** User Goal
- **Actors:** App User
- **Brief:** The user gets information for selecting plant locations based on removed plants and their compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean with "selecting plant locations", I think this is another use case?

Suggested change
- **Brief:** The user gets information for selecting plant locations based on removed plants and their compatibility.
- **Brief:** The user gets information based on earlier or later plants for each location.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move to assigned and assign yourself.

## Scenarios

- **Precondition:**
- The user has opened the app and selected the planting layer.
- **Main success scenario:**
- The user performs the scenario described in the [Linked Use Case](../draft/heatmap+relation_layer_extensions.md).
- The information that is used to display the best position of the plant is substituted by the compatability between the already removed, previously existing plants and the selected plant that should be planted now.
- This can be a positive relation (synergy) or a negative relation (antagonist) which can last a predefined number of years (also only half a year) starting after the removal of the previous plant.
- **Error scenario:**
- When not having any data for a selected pair of plants, nothing happens for the user and no additional information for selecting locations is provided.
- **Postcondition:**
- **Linked Use Cases:**
- [Heatmap and Relation Layer Extensions](../draft/heatmap+relation_layer_extensions.md)
22 changes: 22 additions & 0 deletions doc/usecases/draft/heatmap+relation_layer_extensions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Use Case: Heatmap and Relation Layer extensions

## Summary

- **Scope:** Heatmap and Relation Layer
- **Level:** User Goal
- **Actors:** App User
- **Brief:** The user sees the heatmap and the relation layer enhanced by other features linked below.

## Scenarios

- **Precondition:**
- The user has opened the app and selected the Planting Layer.
- **Main success scenario:**
- The user performs the scenario from the use case [Heatmap](../current/heatmap_layer.md) or [Relation Layer](../current/relation_layer.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't double redirect.

- Within the process of selecting a location to plant/move a plant the visual indications are improved as follows:
- Additional to the information these two already have by themselves, the following features extend them by adding to its knowledge base:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let us make it better understandable: they don't have information "by themselves", but we list all use cases of these layers and all information is described in separate use cases.

- [Crop-Rotation](../draft/crop_rotation.md)
- **Error scenario:**
- When not having any data that can be added to the Heatmap or the Relation Layer the user is faced with only the information these two can provide.
- **Postcondition:**
- The relations in the Relation Layer or the Heatmap helped the user find a good position for the plant(s).