Quality Attributes for Software Design and Architectures
Quality attributes, or non-functional requirements, are the properties that describe how well a system works rather than what it does: performance, scalability, availability, security, maintainability and more. Architects make them explicit and measurable because they usually drive the biggest structural decisions and are often in conflict.
Stage: Domain and Quality · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026
What to learn in Quality Attributes
- Write a measurable scenario for latency or availability
- Identify trade-offs between two competing quality attributes
- Rank attributes with stakeholders for a particular system
- Choose tactics such as caching or redundancy to meet a target
- Use fitness functions to check an attribute automatically
- Explain why an attribute cannot be bolted on late
Quality Attributes interview questions
What is an example of a trade-off between quality attributes?
Strong consistency across regions improves correctness but increases latency and reduces availability under partitions. Likewise, heavy encryption and auditing improve security but cost performance and add complexity. Architecture balances these against stated priorities.
What is an architectural fitness function?
It is an automated check that a system keeps a chosen quality, such as a test that fails if a module depends on a forbidden layer or if response time exceeds a limit. It guards architecture against gradual erosion.
Where Quality Attributes fits in the Software Design and Architecture roadmap
Quality Attributes belongs to the Domain and Quality stage (advanced level). Model the business.
Other units in this stage
Back to the full Software Design and Architecture roadmap