|
<Insert background and context so people can understand why we developed the feature the way we did>
Shiyu Jin (Deactivated), please update the following table with the tickets and user story column.
Title | User Story | Label | Importance | Notes | Video | |
---|---|---|---|---|---|---|
1 | [API] View current Stock on Hand by Facility/Program | Must have | API story | |||
2 | [UI] View SOH summary (currently) | Must have | UI story |
Step 1 : User click the 'View SOH Summary' from the navigation bar, then it will direct user to the default SOH summary page:
Step 2 : User select Program/Facility to view SOH summary:
Product code | Product | Lot number | Expiry date | Last update | SOH | Action |
---|---|---|---|---|---|---|
C100 | Paracetomal | lot2 | 12/2017 |
| 200 | View |
Step 3 : User can search with keywords:
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 |
---|---|
Make the noticed date as the sever processing time instead of front end created event time | |
Permission Management for stock management |
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 | Communicate the decision reached | Open, In Progress, Closed, and date of closure | |
2 |