Introduction

Why Certificates?

Teachers deem a certificate provided by a valid authority as an important artefact:

• serves as an evidence of completing a training

• collection of multiple certificates can potentially build teachers' learning profile

• permanence of the certificate since it is in a digitised format

Hence, the value of including this use case as an integral part of the teacher's online course journey.  

Further, awarding a certificate is a common mechanism used to recognise people with a set of skills and accomplishments:

• Helps to create a standard system of recognition across organisations. A certificate is recognisable and verifiable. It brings in Trust
• Helps teachers to showcase their skills and achievements to others to get a sense of Satisfaction and Recognition. It can also lead to material benefits such as, monetary rewards, promotions, recommendations etc.

JTBD

• Jobs To Be Done: 

• User Personas:
  • Content Creator: Role which has access to create courses
  • Content Reviewer: Role which has access to review and publish courses
  • Course Mentor: Role which has access to create batches and monitor batches via course dashboard
  • Badge Creator: Role which has access to create badges

All the above roles are envisioned as admin activities and hence typically are carried out by state admin or authorised personnel from SCERT office.

• • User: End user who consumes the course - typically a state teacher
• System or Environment: 
  • Admin related functionalities - course creation and review, batch creation and monitoring of batches - are designed to work on desktop/laptop form factor. Consumption experience is designed to work on mobile, tablet and desktop/laptop form factors.

  Portal:

  1. Min. internet speed (download): 1 Mbps
  2. Time to load any webpage (first meaningful paint): 3 seconds
  3. Max. time for any webpage to be interactive (consumption side): 5 seconds
  4. Max time to load a content slide in player (streaming/online play): 3 seconds
  5. Accessibility (basic level): All images with alt tags
  6. Cross-browser support: Chrome 50 + (desktop + mobile), UC Web (mobile only), Firefox (desktop only)
  7. Resolution:
  1. Desktop: Least resolution: 1024 * 768, Projector: 1920*1080
  2. Mobile phone (top list): Samsung SM-J200G (960x540, minimum 100 MB free space)
  8. Active devices per day: 70,000 (Predicted - 200,000 to 500,000)
  9. Concurrent users:  400 requests/sec, concurrent logins

  Mobile App:

  1. Time taken to show book details after downloading spine: <3 seconds
  2. Time taken to show ‘Play’ after downloading content: <3 seconds

Requirement Specifications

This section consists of requirement specifications for specific use cases in the User JTBD. The requirements for each use case are elaborated in detail through sub-sections for:

• Use case overview
• Overall process workflow
• Associated user stories 
• Non-functional requirements
• Localization requirements  
• Telemetry requirements
• Dependencies
• Impact on other products
• Impact on existing data  

Issue of Course Completion Certificate - Overview

This use case is related to providing a course completion certificate to a user who has completed a course, if there is a certificate associated to it. Once a certificate is associated to a course all the batches created for that course within the tenant inherit the certificate. This certificate is a digitized completion certificate equivalent of an existing paper certificate which can be accessed from the user profile page.

In-scope for this use case

There are broadly two types of certificates:

Digital certificates - certificates which are based on the principles of verifiability and portability

Digitized certificates - pdf certificates which are equivalent of a paper based certificate which the users can download

The scope for this use case is 'Digitized Certificates'. 

Overall Process Workflow

Epic JIRA Ticket ID

SB-11097 - Getting issue details... STATUS

User Story 1: Assertion of certificate to a course - Overview

Main Scenario

Assertion of a certificate to a course will be done using a API from the back end. API will be used to carry out the following functions:

1) Associate a certificate to the course
2) Update existing course certificate <if the certificate is already set>
3) Remove association between certificate and the course

These certificates will be modelled after the physical certificate currently issued by the state and will comprise of the following components:

Mapping of the components

• A state can have multiple unique issuers.
• Each issuer will have single signatory and signature.
• Each certificate will have a single issuer, signatory and signature.

The structural model for certification infra needs to be built on Open badges model and add extensions where necessary.

Pre-requisites

• Course is published

• Certificate template is available

• State has provided the details needed to assert the certificate

  • Issuing authority/Issuer name - The issuer will be an organisation or institution which is a competent authority to certify recipients. Note that the issuer is different from the signatory (i.e. the individual(s) who applies his/her signature to the credential). 

  • Signatory - will be the name of the individual/authority signing the certificate. 

  • Signature - will be the digital signature of the signatory. 

Alternate Scenario 1

N/A

Exception Scenarios

When the signatory changes?

In this scenario, the digital signature image is updated with the new signature image by the DIKSHA implementation team. The new signature image is provided by the state.

Wireframes

N/A

For Future Release

• As a badge creator, I want to assert certificates to courses created within my tenant so that users receive the certificate upon course completion.

JIRA Ticket ID

SB-11098 - Getting issue details... STATUS

User Story 2: Auto issue of certificate upon completion of course - Overview

Users who complete the course which has an active completion certificate associated will be awarded the completion certificate. This awarded certificate will be made available for download to the user in their profile page. 

Pre-requisites

• Course is published

• Certificate is asserted to the course

• User is enrolled into the course batch

• User's course progress is 100%

Alternate Scenarios

Once a certificate is associated to a course all the batches created for that course within the tenant inherit the certificate. i.e., teachers enrolled into batches created by mentors from other tenant will not be receiving the certificates.

Exception Scenarios

Scenario 1

If for some technical reason valid user(s) who should have received the certificate have not received it.

• All these user details should be captured and shared with DIKSHA implementation team on a daily basis by an overnight batch job

• DIKSHA implementation team to manually assert these certificates to these users

Scenario 2

Lets say a user has completed the course but for some reason has not received the certificate. However, before the certificate was manually provided to the user, the certificate was updated or removed. 

In this scenario, the user should still be provided with the certificate that was active when the user completed the course.

Wireframes

<Add UX links>

For Future Release(s)

• As a teacher, who'd want to enroll into courses, I want to be able to identify courses which offer completion certificates upon completion of the course so that I can decide whether to enrol into the course or not.

• As a state admin, I want to be able to ensure certificates are to be awarded ONLY to teachers from my state so that teachers from other states do not receive my state authorized certificates.

• As a state admin, I want to be able to view valid teachers who have not received certificates so that I can ensure that certificates are awarded to these teachers.

• As a teacher, I want to be notified via an email or mobile as soon as I receive the completion certificate so that I'm aware that I can now download my certificate.

JIRA Ticket ID

SB-11099 - Getting issue details... STATUS

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics