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 intend is to bring in some business rules so that content relevant to the user is displayed in a particular order so as to improve user engagement
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 in a random order | Course discovery & consumption | Ability for teachers to view courses launched by their state first, followed by other states/tenants |
User Personas:
Teachers - Users who login (State SSO/State on-boarded/Self signed up) to access the platform and consume the course content
User Story 1 - Business rules to display Courses in Open for enrolment section
As a State adminuser, I would want to have a QR code generated for every published course, So that the course consumption becomes easy for my teachers in the statewant to see courses launched by my state first, followed by other states, So that i can save my time and also see the relevant courses
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/State validated
Acceptance criteria:
Verify that
Main work flow
- The first business rule to show courses is based on the user's board
- Courses published by the logged in user's board are displayed first, followed by courses published by other state/tenants
- The other states/tenants are alphabetically ordered
- The second business rule to show courses within a State/other tenants is based on the batch start date
- Courses with batch start date in descending order is displayed. For example, if there are 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.
Alternate work flow
None
Exceptional Workflow
None
JIRA Ticket ID
Localization Requirements
| UI Element | Description | Language(s)/ Locales Required |
|---|---|---|
| None | ||
Telemetry Requirements
| Event Name | Description | Purpose |
|---|---|---|
| None | ||
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 |
|---|---|---|