| Target release | Release name or number |
|---|
| Epic | Link to related JIRA epic or feature |
|---|
| Document status |  |
|---|
| Document owner | Unknown User (aldrin) |
|---|
| Designer | Lead designer |
|---|
| Developers | Lead developer |
|---|
| QA | Lead tester |
|---|
|
Goals
- Provide a feature rich environment for aiding in the design, deployment and management of flows in MiNiFi instances
Background and strategic fit
Why are you doing this? How does this relate to your overall product strategy?
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.