Target release3.1
Epic

Document status

Document owner
Technical LeadPengfei Cui (Deactivated)


Goals/Scope

Background

<Insert background and context so people can understand why we developed the feature the way we did> Shiyu Jin (Deactivated) please fill this section out.

Assumptions

User Stories

Shiyu Jin (Deactivated), please update the following table with the tickets and user story column. I inserted some but it was a guess. 

#TitleUser StoryLabelImportanceNotes
1Create a new physical inventory

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




2Add new products from the approved product list during physical inventory


Must Have



3Save a physical inventory draft


Must have



4Submit a new physical inventory


Must Have






5Remove a physical inventory draft


Must Have


Diagrams/Steps

Step 1 : User selects Program 

Step 2 : User is brought to the "Physical inventory" page, where they can create/view physical inventory. 

Step 3 : Input quantity for active products 

Step 4 : user selects the "Add" button

Step 5 : After added products

Product CodeProductLot NumberExpiry DateStock on handCurrent Stock
C100Venlafaxine capsule 75mgLot A05/05/2018

34

(cannot edit)

100

(editable)







Step 6 : Save physical inventory

Step7:  Remove a physical inventory

Step 8 : Submit physical inventory

Users are required to choose the occurred date for the physical inventory. Moreover, users are able to fill in the optional signature fields. 

After users click the confirm button then this physical inventory is submitted. 

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 storeroom managers to create stock cards during physical inventory

Validation for physical inventory stock event

Only the program ID, Facility ID and orderable ID combination can create a stock card, get rid of the logic that stock card can be created based on the stock card ID. This is the feedback coming from technical discussion meeting.


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