|
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 | Notes |
---|---|---|---|---|---|
2 | Stock status | As a Vaccine managing officer, I can get different indispensable information on the stock status report. I can see the available stock that I have, how many of them have expired or are about to expire, how many of them are reserved for facilities, whether I am overstocked, near EOP or below EOP and much more. | HCMIS | Must Have | |
Item detail report | As a Vaccine managing officer, in this report, I can see all the transactions for a certain item I selected and the detailed information about each transaction. Most like bin card in OpenLMIS v3 (VS note) so review this as part of that | HCMIS | Must Have | ||
Near expiry | As a Vaccine managing officer, I can see the number of months left for an item to get expired and the quantity that will be expired. How to determine which is "near expiry"? Are the numbers showing up in weeks to expiry in the SS? Who needs this, how often, what decisions, and how interactive should these be? | HCMIS | Must Have |
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 | How is item detail report different from the bin card functionality that is being built for OpenLMIS 3.1? What else would we need to add to make this reporting piece work out of that? | Communicate the decision reached | Open, In Progress, Closed, and date of closure |
2 | How is near expiry determined? |