Introduction
The open for enrolment section currently displays all courses that has has an open batch (on-going/Upcoming). Also, currently
- All the courses are displayed in a random order for all types of users (State validated user, self signed up user, guest user)
- There are no business rules to drive the order in which the courses are displayed
The intent is to add business rules so that courses relevant to the user are displayed which would help user to discover the courses published by their state board.
JTBD
Who is the user and what is the user trying to do which is currently a struggle | What is the context | Functional Goal |
---|---|---|
Teachers see all the courses launched by their state + other states/tenant tenant and other tenants in a random order | Course discovery & consumption | Ability for teachers to view courses launched by their state/tenant first, followed by other states/tenants |
User Personas:
Teachers - Users (State SSO/State on-boarded/Self signed up/Anonymous) who have access to the 'Trainings' section in the platform.
User Story 1 - Business rules to
display Courses in Open for enrolment sectionshow Courses with open batch/es
As a user, in the open for enrolment section, I would first want to see courses launched by my state first/tenant, followed by other courses launched by other states, So that i can save my time and also see the relevant coursesget to see relevant courses easily and consume the same
JIRA:
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd key SB-16743
Pre-conditions:
User is logged in/Guest userUser has selected the Location(State and District) Option to select the location is prompted/not prompted
Acceptance criteria:
Verify that:
Main work flow
- The first business rule is to show courses based on the user's State availability
- If available, show Courses published by the User's state first, followed by courses published by other states. The states should be arranged in the alphabetical order (group by state)
- If not available, show Courses published by states in the alphabetical order(group by state)
- The second business rule is to show courses based on the batch start date (this rule needs to be applied after applying the first rule)
- Sequence the courses within a state in descending order of their batch start date. For example, Course 1 (batch start date - 01st Jan), Course 2 (batch start date - 10th Jan) published by UP, then courses are displayed in this order - Course 2, Course 1
- Refer the below flow diagrams for different users/scenarios
Workflow 1 - Anonymous user views Courses on Portal
Workflow 2 - Logged in user views Courses on Portal
Workflow 3
- "Open for enrolment" section is replaced with the below two sections depending on the type of user
- Recommended by my state - shown for SSO users only
- Recommended by other state - shown for SSO, Anonymous and Self signed up users
- Refer the below sheet for various scenarios and examples:https://docs.google.com/spreadsheets/d/1j6Tv7IR5T7jJawb2tYRF2a44ehOA_q_Pf3J_qeoRSww/edit#gid=0
- Note: "Batch start date", "Tenant of the user who created the batch for the course" and "Enrolment end date" should be included in the course metadata to allow for course search and show to the users in appropriate order
Workflows for various types of users
Alternate work flow
None
Exceptional WorkflowScenario
01: If there are no courses published by the board chosen by the user. In this scenario show the courses per 'Workflow (U01)'JIRA Ticket IDlogged in state user's tenant, do not show "Recommended by my state" section. Show only "Recommended by other states" section alone
Localization Requirements
UI Element | Description | Language(s)/ Locales Required |
---|---|---|
No UI changes. Hence N/A | ||
Telemetry Requirements
Event Name | Description | Purpose |
---|---|---|
Only sequence change. Hence N/A | ||
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 |
---|---|
NA | |
Key Metrics
Srl. No. | Metric | Purpose of Metric |
---|---|---|