| Target release | Release name or number |
|---|---|
| Epic | Cold Chain Management & Reporting |
| Document status | |
| Document owner | @JSI |
| Technical Lead | Ashraf Islam |
|
All users are expected to know how to use basic Internet tools.
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 | |
|---|---|---|---|---|---|
| 1 | Update functional status | As DIVO or RIVO, I should be able to update the status CCE located at the facility I supervise | VIMS, VLMIS | Must Have | |
| 2 | Specify Spare part that is needed | As a VIMS user I would like to specify the name of spare part that is needed in the refrigerator so that I can run the report of spare parts needed in my stores. Acceptance Criteria: 1. On the Not-functional status. If the reason is Need spare then the user should specify by typing the name of the spare part needed | VIMS | Nice to have | Ashraf Islam (Unlicensed) Muhammad Ahmed (Unlicensed) I'm labeling this as Nice To Have. Would be helpful to specify VIMS persona. |
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.
Availability of internet, well maintained warehouse / stores
| Description | Link |
|---|---|
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 |
