-
Notifications
You must be signed in to change notification settings - Fork 0
S1_QS
luccasrojas edited this page Sep 7, 2023
·
14 revisions
Scenario name | 1. Lack on internet when loging |
---|---|
Quality attributes | No conectivity where the user is |
App status and context | App is waiting for conectivity to send the login and validate if the user exist in the DB |
Changes in the context | User goes to a zone without any wifi network and looses connection |
System reaction | The app notifies the user that wifi is needed, and each second it check if there is a connection |
Scenario name | 2. Internet goes off after loging |
---|---|
Quality attributes | The connection suddenly drops to zero |
App status and context | App register in a log the last time it has connection to the server |
Changes in the context | User accidentaly turn off wifi while looking for events |
System reaction | The app notifies the user that wifi is off, and the app show a message that says the last time the app was updated with information provided by the server |
Scenario name | 3. Authentication |
---|---|
Quality attributes | Security, authentication of users |
App status and context | The application is actively running |
Changes in the context | Another person tries to impersonate and identity by assisting an event or creating an event in someone else's name |
System reaction | The app will detect that the user is not who he says he is and block the fake user entrance to the platform |
Scenario name | 4. App creation performance |
---|---|
Quality attributes | Performance when creating a group or event |
App status and context | The application is actively running and a user is logged in |
Changes in the context | The user wants to create a new event or group |
System reaction | The app should create the event and make it public in less than 1 second |