Quality attributes (QAs) are the traits of your solution, such as performance, maintainability, and user-friendliness. There are dozens, if not hundreds, of different qualities your software can have. Try to focus just on the important ones instead of listing all that come to your mind when choosing which ones your software should have. Examples of quality attribute requirements include the following:
- The system will respond in under 500 ms for 99.9% of all requests under usual load (don't forget to specify what the usual load is or will be).
- The website will not store customer credit card data used in the payment process (an example of confidentiality).
- When updating the system, if updating any component fails, the system will be rolled back to a state prior to the update (survivability).
- As a user of Windows, macOS, and Android, I want to be able to use the system from all of them (portability; try to understand whether it's needed to support platforms...