-
Notifications
You must be signed in to change notification settings - Fork 0
Functional Requirements and Use Cases
Mihály Dobos-Kovács edited this page Oct 12, 2020
·
11 revisions
ID | Requrirement |
---|---|
FU1 | Users must be able to register to the service |
FU1.1 | Users must be able to register to the service with a valid email, globally unique username, and a password. |
FU2 | Users must be able to login to the service |
FU2.1 | Users must be able to login to the service with a valid email or username and the matching password |
FU2.1 | Users must be able to reset their password with their email address |
FU3 | Users must be able to modify their profile |
FU3.1 | Users must be able to modify their username |
FU3.2 | Users must be able to modify their email |
FU3.3 | Users must be able to modify their password |
FU4 | Administrators must be able to list all users of the service |
FU4.1 | Administrators must be able to view the profile of any user |
FU4.2 | Administrators must be able to modify the profile of any user |
FU4.2.1 | Administrators must be able to modify the username of any user |
FU4.2.2 | Administrators must be able to reset the password of any user with their email address |
FU4.3 | Administrators must be able to delete any user |
ID | Requrirement |
---|---|
FCa1 | Users must be able to view the list of CAFFs |
FCa1.1 | Users must be able to search the list of CAFFs |
FCa1.1.1 | Users must be able to search for CAFFs by their tags |
FCa1.1.2 | Users must be able to search for CAFFs by their name |
FCa2 | Users must be able to view individual CAFFs |
FCa2.1 | Users must be able to see a preview of the CAFFs |
FCa3 | Users must be able to upload CAFFs |
FCa3.1 | The owner of the CAFF must be able to modify the CAFFs metadata |
FCa3.1.1 | The owner of the CAFF must be able to modify the CAFFs name |
FCa3.1.2 | The owner of the CAFF must be able to modify the CAFFs tags |
FCa3.1.3 | Users that are not the owner of the CAFF must not be able to modify the CAFFs metadata |
FCa3.2 | The owner of the CAFF must be able to download the CAFF |
FCa3.3 | The owner of the CAFF must be able to delete the CAFF |
FCa4 | Users must be able to purchase a CAFF |
FCa4.1 | Users must be able to list their purchased CAFFs |
FCa4.2 | Users must be able to download their purchased CAFFs |
FCa4.3 | Users that did not purchase the CAFF must not be able to download it |
FCa4.4 | The owner of the CAFF must not be able to purchase the CAFF |
ID | Requrirement |
---|---|
FCo1 | Users must be able to comment on CAFFs |
FCo1.1 | Users must be able to edit their comments |
FCo1.2 | Users must be able to delete their comments |
FCo1.3 | Users must not be able to edit other users' comments |
FCo1.4 | Users must not be able to delete other users' comments |
FCo1.5 | Administrators must be able to edit any comment |
FCo1.6 | Administrators must be able to delete any comments |
© Grotesque Gecko, 2020
- Functional Requirements and Use Cases
- Security Requirements and Objectives
- Threat Assessment
- Quality Gates
- Chosen Technologies
- Required Security Functionalities
- Structural Model of the System
- Behavioral Model of the System