|
Overview of Supply Lines located here: Configuration Guide for Implementer/Administrator#SetupSupervisoryNodes,RequisitionGroups,SupplyLines
Assumptions
Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
# | Title | User Story | Label | Importance | JIRA Tickets |
---|---|---|---|---|---|
1 | View Supply lines | As an admin I want to view all existing supply lines so that I can troubleshoot requisition problems as needed. Acceptance Criteria:
| Relevant labels to distinguish source. From which system, or which country? | Must Have, Nice to Have | |
2 | Edit supply lines | As an admin I want to edit supply lines so that I can fix associated requisition problems as needed. Acceptance Criteria: | |||
3 | Facility FTP Settings | As an administrator I need to add and edit Facility FTP settings by facility so that I can complete the setup for the requisition workflow process. Acceptance Criteria:
|
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
Description | Link |
---|---|
Name of story or release | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
---|---|---|---|
1 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |