|
Why are you doing this? How does this relate to your overall product strategy?
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | Short identifier for the story | Describe the user and what they are trying to achieve | Must Have |
|
Any preconditions before a client can use the new functionality
Any rules to be applied for a client or user when using this functionality
List of attributes to be captured for the new functionality
Attribute | Description | Notes |
---|---|---|
List of security areas to be considered and permissions to be added/considered for a user/role to have access to this functionality
List of new screens required
List of existing screens that need any kind of changes
Functional changes to Batch jobs that may be needed - along with suggested frequency at which it should be run for various scenarios
With sample accounting entries with dates
Include any mockups, diagrams or visual designs relating to these requirements.
List of error scenarios and the action - if message is to be displayed, then text of the message.
List of changes/enhancements/new reports to support this functionality
From a functional perspective, list of new APIs needed.
From a functional perspective, list of existing APIs that need changes.
Points to be handled during upgrades
Any reference data that needs to be prepopulated or defaulted for clients/users
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 |