S1_QS

Quality Scenarios

Scenario name	1. Lack on internet when loging
Quality attributes	No connectivity 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

Scenario name	5. Rapid User Growth
Quality attributes	Scalability
App status and context	The app is experiencing a surge in new users and event creation.
Changes in the context	User registration and event creation activity increase significantly.
System reaction	The system should automatically scale its resources to handle increased user load, ensuring that event creation remains responsive and data integrity is maintained.

Scenario name	6. Limited Memory
Quality attributes	Performance
App status and context	The user's device is running multiple memory-intensive apps concurrently.
Changes in the context	The user starts the event creation process.
System reaction	The app should monitor memory usage and prioritize memory-efficient operations, preventing crashes or slowdowns. It should provide feedback if the device's memory is insufficient.

Scenario name	7. Feature states
Quality attributes	Scalability
App status and context	Many users are trying to sign up for a very popular event at the same time. The mobile application is sending requests to the server to change the status of event registrants.
Changes in the context	Users must be put in a queue to know which ones can register and which ones cannot.
System reaction	The application must oversee responding to the number of requests and inform the user of the status of his registration to the event/group in a period of less than 5 seconds.

Scenario name	8. Features usability
Quality attributes	Usability
App status and context	A university professor wants to create an event to give a talk. The main page of the extension shows the most popular events.
Changes in the context	The user cannot identify the functionality of creating an event since he is not very tech-savvy.
System reaction	The application should be intuitive and easy to navigate for different levels of experience with technologies. Allowing to find any important functionality in less than 2 clicks.

Scenario name	9. Accesibility
Quality attributes	Accessibility
App status and context	Users with disabilities (e.g., visual impairments) access the application.
Changes in the context	A visually impaired user attempts to create an event using screen reader software.
System reaction	The application should comply with accessibility standards (e.g., WCAG) to ensure that all users, including those with disabilities, can navigate and use the application effectively, with features like alternative text for images.

Scenario name	10. User Data Privacy
Quality attributes	Privacy and Security
App status and context	The application collects and stores user data for authentication and event management purposes.
Changes in the context	A user is concerned about the privacy of their personal information and event attendance history.
System reaction	The application should implement strong data encryption and clear privacy policies to protect user data and assure users of their data's confidentiality and security.

Scenario name	11. Event Cancellation
Quality attributes	Reliability, User Experience
App status and context	An event organizer decides to cancel an event
Changes in the context	Event participants receive notification of the event cancellation
System reaction	The app promptly notifies all participants of the event cancellation and initiates the refund process if applicable. It should also update event status accordingly.

Scenario name	12. Event Privacy
Quality attributes	Privacy
App status and context	Event organizers create private events for specific participants
Changes in the context	Organizers share private event details with selected participants
System reaction	The app should ensure the privacy and security of private events by restricting access to authorized participants only.