View Source

Plant records in Scenario Three need to be connected to records/attributes of that specific plant type (and family) for positive identification. Choose an existing database and schema to use for this purpose or create one if it does not already exist.

Target release	Release name or number
Epic	Link to related Jira epic or feature
Document status
Document owner	Joe Pearson
Designer	Lead designer
Developers	Lead developer
QA	Lead tester

Goals

E.g. Simplify the user experience, reduce friction etc...

Background and strategic fit

If at all possible, re-use existing work and information. For example, see USDA Plants database.

Assumptions

List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).

Requirements

#	Title	User Story	Importance	Notes
1	Short identifier for the story	Describe the user and what they are trying to achieve	Must Have	Additional considerations or noteworthy references (links, issues)
2

User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
(e.g. How we make users more aware of this feature?)	Communicate the decision reached

Not Doing

List the features discussed which are out of scope or might be revisited in a later release.