| Target release | Release name or number |
|---|---|
| Epic | |
| Document status | |
| Document owner | |
| Technical Lead | Technical Lead who reviews or supports document |
|
The goal of this requirements page is to document the feature of Lot Management.
Lot Management for Stock Management Service
Being able to track lots provides us with two new pieces of data: lot number and expiry date. Other fields may be added, but for now we are focusing on these two. The lot number data allows decision makers to track orderables/products at the lot level and also allows warehouse managers to recall orderables if there is an issue for a specific lot. The Expiry date data will not only provide the storeroom managers with the information on when orderables have or will expire (reduce wastage) but also allows the decision makers to implement the FIFO process.
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 | Short identifier for the story | Describe the user and what they are trying to achieve As a ______ I want/need to ________ so that I _______. - High level acceptance criteria | Relevant labels to distinguish source. From which system, or which country? | Must Have, Nice to Have |
|
| 2 |
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.
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 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |