Introduction
JTBD
- Jobs To Be Done: As a state admin, I want to have a look at the performance of each district in ETB such as consumption, failures, etc.
- User Personas: State, PMU
- System or Environment:
Requirement Specifications
District Level Report
Weekly
Description: This report provides details of district wise Diksha usage in terms of QR code Scans, Content Downloads, and Content Play. All the graphs show the usage status per week. This report is updated on every week.
Total no of scans by District: Total no of scans from the District
Logic: Total no of devices which are linked to the specific district and did the scan on that specific day.
Total no of content Downloads in the district: Total no of contents downloaded on a specific day in the district
Logic: Total no of devices which are linked to the specific district and downloaded the content which is linked to the ETB.
Total no of Content play in District: Total no of content played in the district.
Logic: Total no of devices which are linked to the specific district and played the content which is linked to the ETB.
Total no of of Content play on PortalAPP: Total no of content played on the portal APP in the district.
Logic: Total no of devices which are linked to the specific district and played the content on portal APP and those contents are linked to the ETB.
Total Devices that played content on App: Overall in how many devices did the content has been played.
Logic: Total no of content played either through QR code scans or Directly from the ETB.
Content play on APPPlay Time on App (in hours):
Logic: Total no of time spent on the content either through QR code scans or directly from ETB
Total no of Content play on Portal: Total no of content played on APP the portal in the district.
Logic: Total number of content played that day which is linked to the ETB and QR code scans.
Total Devices that played content on Portal: Overall in how many devices did the content has been played.
Logic: Total no of devices which are linked to the specific district and played the content on APP portal and those contents are linked to the ETB.
Content Play Time on Portal (in hours): Total no of Total time spent on content play on the portal.
Logic: Total time spent on the content either through QR code scans or directly from ETB.
Logic:
Total number of Content Plays: Total no of content played both on App and the Portal
Logic: Total Content Plays on App + Total Content Plays on Portal.
Total number of hours of Content Play Time including both app and portal (in hours):
Logic: Content Play Time on App (in hours) + Content Play Time on Portal (in hours)
District Wise Unique Devices
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:
Logic:
<Use Case 1> Overview
<Use Case 1 Overall Process Workflow>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.
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.
<Use Case 1 - User Story 1> Overview
<Main Scenario>
| Srl. No. | User Action | Expected Result |
|---|---|---|
<Alternate Scenario 1>
| Srl. No. | User Action | Expected Result |
|---|---|---|
Exception Scenarios
| Srl. No. | Error / Exception | Expected Handling |
|---|---|---|
Wireframes
For Future Release
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 |
|---|---|