- Scope: Plants Layer
- Level: User Goal
- Actors: App User
- Brief: A short overview of the different attributes a plant has are shown to the App User when searching for plants.
- Precondition:
- The App User has a map and wants to add a plant with a beneficial attribute.
- Main success scenario:
- When searching for plants, attributes are shown for every result and on hover those show a short description of the attribute.
- Alternative scenario:
- The App User searches for a plant and notices the icons associated with each result.
- They hover over an icon to learn more and discover attributes of plants they weren’t originally searching for.
- Error scenario:
- The call to get the attributes fails and no icons are shown.
- Postcondition:
- The correct icon should persist with the correct plant attributes after a search.
- Any visual elements related to the search, like the tooltips, should be cleared if the App User switches layers.
- Non-functional constraints:
- The icons and descriptions should be user-friendly and easy to understand.
- They should not create clutter and should be designed in a way that's space efficient but also visually pleasing.
- It should not affect load times significantly.
- functions: ecological and environmental functions of the plant (e.g. nitrogen fixer)
- life cycle: life span of the plant
- drought tolerance
- hardiness zone
- edible
- warning: important information regarding the plant for humans, animals or environmental well-being (e.g. toxicity)