+
-
+
+
+
In our project, we have some quality goals or expectations that we want to be met. +These are: +* Performance: ability of the software system to respond well to user interactions and perform tasks efficiently.
+Security: protection of the system from unauthorized access, data breaches, and malicious activities, ensuring safety of sensitive information.
+Usability: intuitiveness of the software interface, making it easy for users to interact with the system.
+Maintainability: how easily the software system can be modified, updated, and extended without significant effort or risk.
+Quality
+Performance
+Response time
+Throughput
+Security
+Data encryption
+Access control
+Usability
+Intuitive interface
+User guidance
+Maintainability
+Code readability
+Documentation
+…Usage Scenarios
+| Aspect | Scenario | Sitmulus | Response +|---------------|---------------|---------------|---------------| +| Performance | The game responds fast to user interactions | While playing, an user selects a response to a question. | The system updates its interface very fast and the user knows if he responded correctly, so he can keep playing. +| Security | Usernames and passwords are encrypted before being stored in the MongoDB database. | A new user registers in the game by providing their username and password. | The server encrypts the user’s password before storing it in the MongoDB database, so it is safe from data leaks | +| Usability | User interface elements are intuitive and easy to understand, even for new users. | A new user starts playing the game. | The user interface displays available options and provides clear instructions on how to play, even a 'Help' button. | +| Performance | The game resets correctly and saves the user’s score | Some user is playing, and eventually loses, but wants to play again | The system ends the current game, shows the user his score and resets everything. After that, gives the player the option to start a new game.
+…Change Scenarios
+| Aspect | Scenario | Sitmulus | Response +|---------------|---------------|---------------|---------------| +| Security / Maintainability | Login system is well structured so it is easy to modify it or add new ways of logging in | We want to add the option of logging in with an e-mail instead of an username | The development team implements the new login method easily, ensuring that neither the current data or the new credentials will be compromised| +| Security | User data migration to a new database system is secured. | The decision is made to transition from MongoDB to another database system. | The system initiates a secure data migration process, ensuring all user data, including usernames and passwords, is transferred to the new database system intact and encrypted. | +| Maintainability | The game’s code is well-structured and documented, facilitating the incorporation of new features and the correction of errors. | Developers want to add a new game mode | Due to code being well-structured and documented, it is easy to add new functionality to our system without risking our already implemented functionality | +| Maintainability | The game’s code is well-structured and documented, facilitating the incorporation of new features and the correction of errors. | An error is identified in the game that needs to be corrected. | Due to code being well-structured and documented, developers can easily locate the error and correct it |
+