Target release3.1
Epic

Document status

Document owner
Technical LeadPengfei Cui (Deactivated)


Goals/Scope

Background

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 StoryLabelImportanceNotes
1[UI] Perform ad hoc receipt

Relevant labels to distinguish source. From which system, or which country? Must have


2

[UI] Perform ad hoc issue


Must have


3[API] Update the stock event API to support one event include 'receive from/issue to' fields

Allow end user to submit receive/issue stock eventMust have


4Allow users choosing a program to make receive/issue stock event

Allow end user to choose one program for the receive/issue stock eventMust have

Steps

Step 1 : User selects Program 

Step 2 : User is brought to the "Make Receive" page, where they can create receive.

Step 3 : After user choose a product and click the 'add' button

Step 4 : After filled in required fields



If the there is lot data:

Step 5 : After click 'Submit' button,  user sees confirmation modal which displays "<username> confirms "N" receive/issue.

 

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
Allow system admin assigning source/destination to specific facility type and program combination


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
Communicate the decision reached Open, In Progress, Closed, and date of closure
2



Out of Scope