| Target release | Release name or number |
|---|---|
| Epic | Reporting - New |
| Document status | |
| Priority | |
| eLMIS Status | Not implemented |
| OpenLMIS Status | Not implemented |
| PATH | Jenny Thompson (Unlicensed) |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI | Ashraf |
|
Status in eLMIS: Not in eLMIS
Status in OpenLMIS: Not implemented
Priority: Medium
This section outlines features which are not in the current eLMIS, but have been highlighted by users as needed.
Trends over time: Currently eLMIS requires the user to select one individual period to produce most reports and analysis, and does not show multiple periods in the same data sets. While there is one small graph feature showing some data over four quarters of one year, there is need for more comprehensive trend analysis features.
Multiple programs: Analysis features which contain data from multiple programs in the same data set do not currently exist. At the moment users can only see the data for one program at a time.
Treatment of the emergency order data during analysis: If an emergency order covers a period 1st April to 25th May, and later a routine R&R is submitted for 1st April to 30th June, this currently sometimes leads to double counting in some of the eLMIS analysis. The 1st April to 30th June data currently does not override the 1st April to 25th May submission earlier on the emergency R&R.
Parameter section user friendliness: The parameter selection for analysis is currently not user friendly, including that it's unclear when the analysis output had refreshed and when a required but blank parameter meant that the analysis has not refreshed yet.
What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).
User Stories
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 | Trends over time | As a report user, I want to be able to see trends over time so that I can compare and analyze these and this can inform decision-making. | Tanzania Reports | Must have |
|
| Multiple Programs | As a report user, I need analysis features which contain data from multiple programs in the same data, including analysis of reporting timeliness across programs, so that I can see the data for more than one program at a time to identify issues and take action. | Tanzania reports | Must have | ||
| Treatment of the emergency order data during analysis | As an R&R submitter I want emergency order submissions to be overwritten by routine R&Rs covering the same period so that there is not double counting. | Tanzania reports | Must have | Emergency R&Rs covering transitions from one schedule (eg “schedule A” Jan-Mar) to another schedule (eg “schedule B” Feb-Apr) do need to be included in data analysis. | |
| Parameter section user friendliness | As a user of analysis features, I want the parameter selection for analysis to be more user friendly so that its clear when the analysis output has refreshed and when a required but blank parameter meant that the analysis has not refreshed yet. | Tanzania reporting | Nice to have | ||
Diagrams
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 | For Tanzania user stories: review the users, "so thats" added, review the label, and review the priority level. | Communicate the decision reached | Open, In Progress, Closed, and date of closure |