| Status | ||||
|---|---|---|---|---|
|
...
As of today, Review will publish to the textbook directly.
...
| Note |
|---|
Ignore below section for now! - Rough notes |
Program Portal V1
Use case story
...
| Expand | ||
|---|---|---|
| ||
|
For each content type
Program user journeys
...
Experiment vs Program
Experiment - driven by us, Program - driven by state
Experiment - to test a feature variation, may be flaky
Programs are mainly used for scoping and tracking of the activities
Core feature vs Program
Available to all users vs custom experience for a content type / program
..
Conceptual Model
Program - Types??, Definition: Scope, Activity ~ (Tool, Actions, Config)
Users, Teams, Roles - on boarding, setup
Default Programs - e.g. workspace, consumption for a content type
High Level Design
Program Entity structure
Structure of Tools - Angular components, dynamic loading
Program Configuration
Deployment Model
Delivery Channels
Portal
Mobile App
Roadmap
Telemetry Requirements
Basic telemetry parameters should be captured for each page: start, end, impression, interact, error
For any page following should be captured : No. of users visited, time spent, feature accessed. Feature threw errors, success workflow completed
For page load following should be captured: Response time for any page to load - limit may be 30 sec max, No. of page load requests, page load capture, page load error with time , page load success with time
Non-Functional Requirements
All API should give the relevant response code.
NFR should be followed as per standard sunbird platform
Program portal should support scale up and scale down feature (similar to Diksha). For reference : https://project-sunbird.atlassian.net/browse/SB-15591
Impact on the products/solutions
Anticipated Diksha integration under Workspace
Impact is being taken care through dependencies
Impact on the existing users/data
NA
Localization requirements
NA