Target releaseRelease name or number
Epic

Document status
Document owner
Technical LeadTechnical Lead who reviews or supports document


Goals/Scope

Background

Overview of Supply Lines located here: Configuration Guide for Implementer/Administrator#SetupSupervisoryNodes,RequisitionGroups,SupplyLines


Assumptions

User Stories

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.

#TitleUser StoryLabelImportanceJIRA Tickets
1View Supply lines

As an admin I want to view all existing supply lines so that I can troubleshoot requisition problems as needed.

Acceptance Criteria:

  • User with admin rights can view supply lines page
  • User has ability to search for Supply Lines by "Supplying Facility"
  • When user goes to Supply Lines page, a paginated table with the existing Supply Lines is displayed (top 10)
  • Supply Lines table has default sort order by Supplying Facility Name
  • Supply Lines table displays Supplying Facility Name, Supervisory Node, Program, and Action
  • User can click View action to view more details about the Supplying Facility


Relevant labels to distinguish source. From which system, or which country? Must Have, Nice to Have
2Edit supply lines

As an admin I want to edit supply lines so that I can fix associated requisition problems as needed.

Acceptance Criteria:




3Facility 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:

  • Admin can select facility from search page to add Facility FTP settings
  • Admin can edit Facility FTP settings by facility


Diagrams

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.


Dependencies

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.

DescriptionLink
Name of story or release Link to JIRA


Open Questions

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:

#QuestionOutcomeStatus
1(e.g. How we make users more aware of this feature?)Communicate the decision reached Open, In Progress, Closed, and date of closure

Out of Scope