Introduction
This report provides details of Diksha usage in terms of QR code Scans, Unique devices from each district of state. It helps the state to improve the position and consumption in ETB.The particular state can view only their state report.
JTBD
- Jobs To Be Done: As a state admin, I want to have a look at the performance of each district in ETB of the state such as consumption, failures , etcin ETB.
- User Personas: The logged in users who have State , PMUAdmin role, report viewer role can access this report.
- System or Environment: works on for desktops with Chrome browser only.
District-wise Report
This report shows 2 fields i.e; graph and Table.
Graph:
a. District-Wise devices:In the first graph, we will be displaying 2 bar charts with district's rank and the number of unique devices from each district in that state for the last month and before last month.
b. District wise Scans: In the second graph, we will be displaying 2 bar charts with district's rank and the number of scans from each district in that state for the last month and before last month.
Description:
This will provide only 2 months data, To identify which district is doing better this month than last month hence this report will of data. It will help the state admin to identify the performance of each district in that state. It gives a better understanding of users using Diksha from that state. This report should get updated on a monthly basis.
Details:
In this report, we will be displaying 2 months of data i.e; Last month and before last month. We will be showing how many scans are done Based on device Geo data, Ranking and number of unique device count are captured and are displaced in Diksha from each district of that state and according to that unique devices count, the ranking should be allocated in the same order in graph 1.of first bar chart.
Graph 1:
In the second bar chart of graph
21, based on the before last month data, the ranking should be allocated with the number of unique devices to the district of that state in the same order of first bar chart of the graph 1.
Graph 2: In this, we should create 2 bar charts based on the device geo data scans. Ranking and number of scans should be displayed for the district in that state for last month and the before last month.
Table:
Second Last Month | Last Month | |||||
Unique Devices | Rank | Total Scans | Unique Devices | Rank | Total Scans | |
|---|---|---|---|---|---|---|
District 1 | ||||||
District 2 | ||||||
District 3 | ||||||
District 4 | ||||||
District 5 | ||||||
Details:
District wise unique devices count and total scans counts of each district in the state are recorded for the last month and second last month.
Fields:
- Unique Device: Unique devices for the district in that month for a state
- Total Scans: Count of scans from each district in that state
Reason: To compare which district is doing better in every month.
NOTE: This report should be
updatedgenerated with both the graphs on every
monthmonth 1st with the latest last month data and before to last month data.
Latest last month data should be aligned in the ascending order of district ranks of that state.
District
Wise-wise Unique Devices over time
Description:
This will provide only 2 months data, To identify which district is doing better this month than last month hence this report will get updated on a monthly basis.How many unique devices data got synced in The month before last month vs How many unique devices data got synced last month in that district
Details:
InThis graph shows unique devices count for every week( i.e; from Monday to Sunday ) in DIKSHA overtime and should be generated on every Monday on a weekly basis for that state.
Details: In this report, we will be displaying
2 months of data i.e; Last month and before last month. We will be showing how many unique devices used Diksha from each district and ranking should be allocated in the same order in graph 1.In graph 2, based on the last month data, the ranking should be allocated to the district in the same order of graph 1.
Reason: To compare which district is doing better in every month.
NOTE: This report should be updated on every month 1st with the latest last month data and before to last month data.
Latest last month data should be aligned in the ascending order of district ranks.
JIRA Ticket ID
<Usethe user devices data on a weekly basis for that state. This data is calculated by the district wise.
- Whenever the user goes on to the graph, they will be able to see overall data of the state. District wise filter should be enabled and the user should be able to get the data by filtering the district name whenever needed.
- If no district is selected in the filter, Overall data should be displayed.
Graph :
Table :
| District Name\Week | Week 1 | week 2 | Week 3 | Week 4 |
|---|---|---|---|---|
| District 1 | ||||
| District 2 | ||||
| District 3 | ||||
| District 4 |
Details :
Each district unique devices count is captured on a weekly basis for that state. This is for overtime and all the districts of that state are shown.
JIRA Ticket ID
Use Case 1 - User Story 2> Overview
Localization Requirements
| UI Element | Description | Language(s)/ Locales Required |
|---|---|---|
Telemetry Requirements
| Event Name | Description | Purpose |
|---|---|---|
Non-Functional Requirements
| Performance / Responsiveness Requirements | Load/Volume Requirements | Security / Privacy Requirements |
|---|---|---|
Impact on other Products/Solutions
| Product/Solution Impacted | Impact Description |
|---|---|
Impact on Existing Users/Data
| User/Data Impacted | Impact Description |
|---|---|