Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
Submitters want to have the ability to identify the specific application/business areas they have access to (i.e., AIMS, BedSurvey, etc.). This is a way of grouping/organizing forms.
Business Rationale:
Priority (MoSCoW): Could Have
Some authenticated users submit multiple forms directed at the same business area on a regular basis. Users may not want to have to keep track of multiple links.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
Technical Details:
Custom feature.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|