Refine QRs based on feedback

[lkekana]

(Don't forget to close https://github.com/COS301-SE-2024/TuneIn/issues/32 before this)

Include:

• Details on maintainability and adaptability using loosely coupled components.
• Quantify each QR for each user type.

[lkekana]

Advice from Chat:

Quantifications for Quality Requirements

Quantifying quality requirements means specifying measurable criteria for non-functional requirements. This helps ensure that the requirements are clear, testable, and achievable. Here's how you can approach quantification for different user types:

1. Performance

   • Response time: "The system shall respond to user inputs within 2 seconds for regular users and 1 second for premium users."
   • Throughput: "The system shall process up to 100 transactions per second for end-users."

2. Security

   • Authentication: "The system shall support two-factor authentication for all users."
   • Data encryption: "All user data shall be encrypted using AES-256."

3. Usability

   • Accessibility: "The system shall comply with WCAG 2.1 Level AA for visually impaired users."
   • Interface response: "The dashboard shall load within 3 seconds for all users."

4. Reliability

   • Uptime: "The system shall have an uptime of 99.9% for all users."

[lkekana]

also found this in my notes from our meeting last week:

• [ ] maintainability
  • [ ] add code & development & deployment easier to understand & work on without reading docs

not too sure what it meant tbh

[lkekana]

note: Thabo also said you should only give estimates where it's possible & necessary to measure them (eg. probably unnecessary: 99.9% uptime) and also discuss strategies to achieve for QRs