-
Notifications
You must be signed in to change notification settings - Fork 13
Add use cases for Crop Rotation #1292
base: master
Are you sure you want to change the base?
Conversation
Is there something missing here still and what do you think about this draft? @markus2330 |
@markus2330 Could you please give me some feedback on this or should I just convert it to a real pool request instead of having it as a draft because its roughly ok as it already and ready for normal reviews? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as discussed in meeting
- **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. |
There was a problem hiding this comment.
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?
- **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. |
- **Main success scenario:** | ||
- The user performs the scenario from the use case [Heatmap](../current/heatmap_layer.md) or [Relation Layer](../current/relation_layer.md). | ||
- 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: |
There was a problem hiding this comment.
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.
- **Level:** User Goal | ||
- **Actors:** App User | ||
- **Brief:** The user gets information for selecting plant locations based on removed plants and their compatibility. | ||
|
There was a problem hiding this comment.
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.
- **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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't double redirect.
Basics
close #X
, are in the commit messages and changelogChecklist
First Time Checklist
Review