Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Instructions to use this template:

  1. Use this template to write the Product Requirements Document (PRD) for a single User JTBD or Initiative. 
  2. Each workflow within the PRD will correspond to an Epic in JIRA. Each User Story will correspond to a Story in JIRA that will be part of the Epic.
  3. Each section in the template has instructions, with examples explaining the type of content to be written in that section. 
  4. You may start typing into the section by eliminating the instructional text, or delete the instructional text after you have entered all content for the section.
  5. Repeat from section <Use Case 1> Overview for every use case in the User JTBD or Initiative

Table of Contents
outlinetrue

Introduction

JTBD

Table of Contents
outlinetrue


Introduction

Based on usage of MCQ questions by several states, there are several inputs that have come up to improve on the experience of users consuming these questions. These constitute of enhancements to support new layouts as well as improvements to existing layouts.

This PRD documents the specifications of these changes.

JTBD

Jobs To Be Done: 

  • User Personas: The logged in users who have content creator role, Will be able to use these templates. Teachers or Students who consume questions on mobile or portal
  • System or Environment: Works on for desktops with Chrome browser only.

Requirement Specifications 

For

1. Improvements to the existing MCQ

templates, which are Live in the production and also for new template described below, we need to do the changes mentioned below.
  • Image Zoom in
  • Audio Button
  • Text auto adjustment
    image Zoom in  

    Templates

    Image Zoom-in 

    1. Where ever there is an image in the question or in the option, while previewing the question in the mobile

    2. APP
    3. App or in the portal, the Zoom in button should be shown on the image.

    4. When a user clicks on the Zoom in button, the image should pop up in the full screen both in mobile

    5. APP
    6. App and in the Portal preview.

    7. Whenever the user is on the pop

    8. 's up to the image
    9. -up,  on the right side of the image there should be a cross (X) button, Whenever user clicks on that button the image should go back to its original position.

    Audio Button

  • Whenever the user adds the audio to the question, then that audio button should show before the question for all the templates.
  • Whenever a user adds the audio to the options, if there is the only text in the options then the audio button should show up before the question, If in case there is an image in the options then the audio button should show up in the image. If there is both image and text in the option, even then the audio button should show up on the image only.
  • Whenever the user clicks on the audio button, then only the audio should start play and if the audio is playing and the user taps on the same audio button it should stop the audio.
  • Text auto adjustment

    There is a change in the location and size of the audio button. The modified UI is given in the UI Screenshots. There is no change in the functionality. Only placement and size of the icon as given in the wire-frames need to be considered and not change in the icons between play and stop.

    Text Wrap

    Text wrap should be enabled for both question and options in all existing templates wherever text is present.

  • Based on that, the text in the preview should be set according to the screen.
  • New MCQ Template 

    JIRA Ticket ID

    Jira Legacy
    serverSystem JIRA
    serverId2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd
    keySB-12280

    Wire-frames

    https://projects.invisionapp.com/share/73SRFRRSBPC#/screens/371494039

    2. New MCQ Layouts 

    In MCQ, we need to add 1 two new template layouts which supports support horizontal image as a question.

    1. If a question contains Text or horizontal image or both, the audio option should be enabled, but it is user opinion to use it.

    2. If a user is adding the audio in the question, then the audio button should be shown while previewing the content both in APP and portal and if it is clicked, audio should play and in second click the audio should stop.

    3.. In the options, square image or text or both, with and without audio should be accepted. Zoom button should be shown on the image. The long text should be supported and it should be wrapped. If there are more options, automatically the scroll option should be shown. On using it, the user should be able to see al the options and select the option. 

    <Use Case 1 Overall Process Workflow>

    <Use Case 1 - User Story 1> Overview

    <Main Scenario>

    Srl. No.User ActionExpected Result

    <Alternate Scenario 1>

    Srl. No.User ActionExpected Result

    Exception Scenarios

    Srl. No.Error / ExceptionExpected Handling

    Wireframes

    For Future Release

    JIRA Ticket ID

    <Use Case 1 - User Story 2> Overview

    Localization Requirements

    UI ElementDescriptionLanguage(s)/ Locales Required

    Telemetry Requirements

    Event NameDescriptionPurpose

    Non-Functional Requirements

    Performance / Responsiveness RequirementsLoad/Volume RequirementsSecurity / Privacy Requirements

    layout for an image in the Question where the image of the question is shown on the top and options are shown at bottom.

    1. A layout that supports: Horizontal Image+Text in Question. Image+Text in options
    2. A layout that supports: Horizontal Image+Text in Question. Only Text in options

    Wireframes for the same are below.

    Functionality of the new layouts should be exactly same as that of the two layouts that support Image in Question on the left side (portrait mode).

    JIRA Ticket ID

    Jira Legacy
    serverSystem JIRA
    serverId2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd
    keySB-13367

    Wire-frames

    https://projects.invisionapp.com/share/PWSWZ1I8MFX#/screens

    Localization Requirements

    N/A

    Telemetry Requirements

    All the Telemetry events of the existing templates have to be implemented for the new MCQ layouts as well.

    Non-Functional Requirements

    N/A

    Impact on other Products/Solutions

    Product

    N/

    Solution Impacted

    A

    Impact

    DescriptionImpact

    on Existing Users/Data 

    User/Data ImpactedImpact Description

    Improvements to the existing templates will not reflect automatically in the existing live content. The content has to be republished to reflect this. Separate Jira ticket will be created for this as required. 

    Key Metrics

    Srl. No.MetricPurpose of Metric
    1.Number of content using new MCQ layoutsTo understand the business value of the new layouts