-
Notifications
You must be signed in to change notification settings - Fork 0
3.1. Functional Requirements
Silfer edited this page Apr 18, 2017
·
5 revisions
Due to the shared functionality between the pages, the requirements have been further distilled into tasks presented in the following table. Users are both students and tutors that require the same functionality.
Index. | Description | Priority |
---|---|---|
1. | Users should be able to access the system with an IVLE account. | High |
2. | Users should be able to get information about their tutorials and modules from IVLE. | High |
3. | Users should be able to retrieve experience, levels and avatar preferences gained from previous tutorial sessions. | High |
4. | Users should be able to receive a notification message upon failure to log in. | High |
5. | Tutors should be able to get information identifying students in assigned tutorials. | High |
6. | Users should be able to navigate between modules, tutorials and tutorial subgroups. | High |
7. | Tutors should be able to create tutorial subgroups for their tutorial classes. | High |
8. | Tutors should be able to name and manually assign students to tutorial subgroups. | High |
9. | Tutors should be able to remove students from tutorial subgroups. | High |
10. | Tutors should be able to open a lobby for the tutorial. | High |
11. | Tutors should be able to see which tutorial subgroups students are assigned to. | High |
12. | Tutors should be able to delete tutorial subgroups. | High |
13. | Students should be able to join open lobbies. | High |
14. | Tutors should be able to unlock the lobby for students to join. | High |
15. | Users should be able to leave the lobby and return to the dashboard. | High |
16. | Tutors should be able to initiate a battle with the tutorial group. | High |
17. | Users should be able to view a list of students by name currently active in the lobby. | High |
18. | Users should be able to communicate through text messages. | High |
19. | Students should be able to join a battle after the tutor initiates one. | High |
20. | Tutors should be able to select groups to direct the composed question to | High |
21. | Tutors should be able to give a score for the answers that are provided | High |
22. | Users should be able to create a new text box instance when composing each subsequent action. | High |
23. | Users should be able to refer to the text boxes containing previously answered questions and the respective answers provided by each subgroup. | High |
24. | Users should be able to personalise their avatars. | Medium |
25. | Users should be able to view other avatars with their chosen customisations. | Medium |
Index. | Description | Priority |
---|---|---|
1. | Tutors should be able to access the system with an IVLE account. | High |
2. | Tutors should be able to receive a notification message upon failure to log in. | High |
Index. | Description | Priority |
---|---|---|
1. | Students should be able to access the system with an IVLE account. | High |
2. | Students should be able to receive a notification message upon failure to log in. | High |
Index. | Description | Priority |
---|---|---|
1. | Tutors should be able to navigate between modules, tutorials and tutorial subgroups. | High |
2. | Tutors should be able to open a lobby for the tutorial. | High |
3. | Tutors should be able to delete tutorial subgroups. | High |
4. | Tutors should be able to personalise their avatars. | Medium |
5. | Tutors should be able to get information about their assigned tutorials and modules from IVLE. | High |
6. | Tutors should be able to retrieve avatar preferences gained from previous tutorial sessions. | Medium |
Index. | Description | Priority |
---|---|---|
1. | Students should be able to navigate between modules, tutorials and tutorial subgroups. | High |
2. | Students should be able to join open lobbies. | High |
3. | Students should be able to personalise their avatars. | Medium |
4. | Students should be able to retrieve experience, levels and avatar preferences gained from previous tutorial sessions. | High |
5. | Students should be able to get information about their assigned tutorials and modules from IVLE. | High |
Index. | Description | Priority |
---|---|---|
1. | Tutors should be able to unlock the lobby for students to join. | High |
2. | Tutors should be able to leave the lobby and return to the dashboard. | High |
3. | Tutors should be able to initiate a battle with the tutorial group. | High |
4. | Tutors should be able to view a list of students by name currently active in the lobby. | High |
5. | Tutors should be able to communicate with the students through text messages. | High |
6. | Tutors should be able to view a list of students by name currently active in the battle room. | High |
7. | Tutors should be able to end a battle session. | High |
8. | Tutors should be able to view their avatars with their chosen customisations. | Medium |
9. | Tutors should be able to view each student’s avatar with their chosen customisations. | Medium |
10. | Tutors should be able to create tutorial subgroups for their tutorial classes. | High |
11. | Tutors should be able to name and manually assign students to tutorial subgroups. | High |
12. | Tutors should be able to remove students from tutorial subgroups. | High |
13. | Tutors should be able to see which tutorial subgroups students are assigned to. | High |
Index. | Description | Priority |
---|---|---|
1. | Students should be able to return to the dashboard. | High |
2. | Students should be able to communicate with the other students in the lobby and the tutor via textual chat. | High |
3. | Students should be able to join a battle after the tutor initiates one. | High |
4. | Students should be able to view a list of students by name currently active in the battle room. | High |
5. | Students should be able to view the tutor's avatar with their chosen customisations. | Medium |
6. | Students should be able to view each student’s avatar with their chosen customisations within their subgroup. | Medium |
From the littlest team with big dreams, SOLOQ:
Joey Yeo
Weizheng Lee
Goh Yuan Tat
- Introduction
- Getting Started
- Software Requirements
- 3.1. Functional Requirements
- 3.2. Non-Functional Requirements
- 3.3. Abuser Stories
- Software Design
- 4.1. User Interface
- 4.2. Software Architecture
- 4.3. Database Design
- Usability
- Performance, Robustness and Security
- Project Log
- Archive