Concept of non-functional quality properties of systems that shape architectural decisions and evaluation criteria.
Quality attributes describe non-functional requirements such as performance, security, or maintainability and provide qualitative criteria for architectural decisions. They enable prioritization and trade-off analysis by defining measurable expectations and target states. In design, they drive trade-offs and inform testing and monitoring objectives.
Time within which 95% of requests are served; important for performance SLAs.
Percentage of uptime within a defined interval.
Average time to recover after an outage.
Requirement: maximum 200 ms response time under peak load to avoid checkout abandonment.
Requirement: 99.99% availability and defined recovery times for critical transactions.
Requirement: energy-optimized communication to ensure a minimum one-year operational lifetime.
Conduct stakeholder workshop to elicit quality attributes.
Formulate scenarios and derive metrics.
Ensure integration into design, testing, and monitoring processes.