FS Participant requirements
Target release | Â |
---|---|
Epic | Â |
Document status | DRAFT |
Document owner | @Vineet Singh |
Designer | Yash |
Project lead | @Avinash Verma (Unlicensed) |
Technology team | @ravindra.tripathi (Unlicensed) @Ksuresh | Thrymr (Unlicensed) @Monika Khare (Unlicensed) |
QA | @chandrashekhar (Unlicensed) @Razak K M |
User interaction and design
Initial release for web based interaction only
figma design for art board with placeholder text
figma design for user story based flow
Â
Requirements
Requirement | User Story | Importance | Notes | |
---|---|---|---|---|
1 | Short and guided sign up | H is a senior official in a global social impact company in Ethiopia and wants to sign up in quick efficient way | HIGH | figma design for signup plus activation process |
2 | Single sign on with Google | M is a subordinate of H and wants to signin using google | HIGH |
|
3 | Retrieve credentials | H forgot his password and wants to recover in simple way | HIGH |
|
4 | First login activation - root admin | Guided step by step way to help H add team members and show around using tooltips | high | figma design of root admin activation including adding member + quick guided tour of the tabs |
5 | First login activation - team admin/ member | Guided step by step way to help user customise the settings and show around using tooltips | meidum | figma design with shorter guided tour |
6 | Nth login tip | Important tip (skippable) | LOW |
|
7 | Dashboard for managing projects/ connectors Main features:
| M wants to have quick view of what connectors are used where in which project and add/ remove/ update projects within which he can create or pause and update connections:
| HIGH |
|
8 | Dashboard for root admin giving overview of team | H wants to have quick view of who is owning what connectors apart from the connectors dashboard | HIGH | Â |
9 | Datasets tab to add description about data | M wants to add description about data which includes:
| high | Â |
10 | Explore datasets published within the network | M wants to explore who has what data, available through which connector and with which usage policy | high | Â |
11 | Package tab to manage containerised applications | Dashboard to give quick overview of what packages have been published for review following which the package is registered for configuring usage policy | high | Â |
12 | Settings | User wants to change attributes related to own profile and add team members or guest viewers | HIGH | Â |
Questions
Questions | Answers |
---|---|
Does every user get to see the connectors created within the organisation? | Â |
Is every user required to add details about the same dataset? Can it be that root admin can add details and make it available for all? | Â |
If a root admin is changed, does the new root admin has auto filled dashboard? Will he/she have the same projects and connectors if made? | Â |
If a new user takes place of an existing user, does he have the auto filled dashboard and connectors? Same projects or different projects? | Â |
Out of Scope
Notifications related to connectors and user settings
User requests and tracking system
Auto upgrades