Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

As a teacher/student, I would like to see content linked to a DIAL code in my book in a structured format. If there is a lot of content (For e.g. a textbook level DIAL code), it would be good to select a chapter to jump to the content most relevant to me.

JTBD

  • Jobs To Be Done: User scans a DIAL code, and wants to consume content contextual to what they're studying at the moment. If the user scans a book-level code or a code which has a lot of branches and content under it, then it's hard to find the right content that I want right now. As a user, I'd like to quickly find the most relevant content from the current scan for me to consume right away.
  • User Personas:  Teacher, Student
  • System or Environment: Mostly home, some likelihood of being in school.

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  

Overview

As a user, I might scan a QR code and find a lot of content linked to it. It would be good to see it categorized neatly, so I can quickly jump to the section most relevant to me.

Overall Process Workflow

  1. User scans a DIAL code with a lot of content attached to it.
  2. User sees the list of content associated with the DIAL code.
  3. User taps on the Select Chapter row.
  4. User sees the relevant sections associated with this DIAL code only.
  5. User taps on the section of interest and the user is taken to the start of that section in the flattened DIAL result.


Overview

User scans a high-level DIAL Code and wants to jump to a specific sub-section within that.

Main Scenario


Srl. No.User ActionExpected Result

User scans DIAL code (preferably at a level as close to root as possible)User sees a flattened set of DIAL results.

User taps on 'Select Chapter'

User sees the section of the TOC directly under this DIAL code only.

The closest node/sub-section of the first fully visible content card is highlighted, and visible atleast a couple of rows from the top of the screen. (This rule can be ignored if there aren't enough rows to fill the screen)

Each top-level chapter has separators, and the corresponding header styles should apply based on section.

The 'SELECT CHAPTER' UI inside the textbook should also be exactly the same as this.


User selects one of the section headersThe user is taken to the first content within the section header immediately.

Exception Scenarios

Srl. No.Error / ExceptionExpected Handling

User taps on a section that's 'Coming Soon'User should be taken back to the flattened results DIAL screen at the exact same offset as before, and a popup with the tenant specific 'Coming soon' message for the book should be displayed.

Wireframes

https://projects.invisionapp.com/share/48TSWGCJNSM#/screens/383355930
https://projects.invisionapp.com/share/48TSWGCJNSM#/screens/383356056

For Future Release

A results screen that looks exactly in the same format, whether you opened the textbook or scanned the DIAL code.

JIRA Ticket ID

SB-14404 - Getting issue details... STATUS

Localization Requirements

UI ElementDescriptionLanguage(s)/ Locales Required
LabelsLabels for 'Select Chapter'All supported languages

Telemetry Requirements

Event NameDescriptionPurpose
Landed on DIAL results page (addn attribs: DIAL code, count of nodes, content)Landed on Flattened DIAL results pageTo know how many users landed on a flattened DIAL results page, and the average count of results that users see
Tapped on Select Chapter (addn attribs: DIAL code, count of nodes, index of highlighted node)Initiated the display of the ToC for the DIAL codeTo know how many people attempt to open the ToC
Tapped on a node from the ToC (addn attribs: DIAL code, index of tapped node, index of highlighted node)Selected a chapter/sub-section from the ToCTo know for a DIAL code if there's a pattern of which node tends to get selected more often
Tapped on back button (addn attribs: DIAL code, UI/device)Attempted to go backTo know how often users choose not to change the chapter

Non-Functional Requirements

Performance / Responsiveness RequirementsLoad/Volume RequirementsSecurity / Privacy Requirements
Tapping on 'Select Chapter' should open the page immediately (<0.5s)

250 content in the book, with nodes with the following structure:

10 chapters

  • 5 sections in each
    • 5 sub-sections in each
      • 1 content in each



Impact on other Products/Solutions

Product/Solution ImpactedImpact Description
N/AN/A

Impact on Existing Users/Data 

User/Data ImpactedImpact Description
Existing usersUsers will now see a Select Chapter when they scan a DIAL code

Key Metrics

Srl. No.MetricPurpose of Metric

DIAL scan funnelUnique devices that (visited the app | scanned a DIAL code | saw DIAL results page | Clicked on Chapter Select | Changed chapter | Played content )



  • No labels