Quality tree
A general quality tree is a context-specific overview; the ATAM Utility Tree refines business goals into scenarios and rates their importance and difficulty.
- Quality goalDescribes the product behavior being sought.
- Quality scenarioMakes the stimulus, condition, and measurable response concrete.
- ATAM ratingRates business importance and technical difficulty separately.
Context
Why this is important
Distinguish a freely structured quality overview from the specific prioritization used in the ATAM Utility Tree.
A structured working and communication view of quality goals and their scenarios.
General quality tree and ATAM Utility Tree
The shop organises catalog performance and checkout availability as distinct goals with their own scenarios.
This is how you read the picture
- Quality goal Business goal
- Quality scenario Scenario leaf
- ATAM rating Prioritization
| Aspect | General quality tree | ATAM Utility Tree |
|---|---|---|
| Structure | Team-defined goals and scenarios. | Business goals are refined into quality scenarios. |
| Prioritization | Weighting based on the agreed product context. | Rate business importance and technical difficulty for each scenario. |
| What it tells you | Shows the overview and outstanding goals. | Focuses the architecture investigation on important, challenging scenarios. |
Benefits & limitations
Helps if:
- A team needs to organize quality goals and prioritize scenarios for a concrete product decision.
- For an ATAM analysis, stakeholders need to visibly rate the business importance and technical difficulty of selected quality scenarios.
Boundaries
- A team-defined quality overview does not prove that a system meets a goal in operation; each scenario needs a measurement or analysis for that.
- ATAM priority ratings depend on stakeholders and their rating scale; they replace neither architecture decisions nor investigation of risks and trade-offs.
In practice
- Collect quality goals with stakeholders and organise them in a structure the product team understands. Use product language and group related characteristics only when a shared category adds meaning.
- Link important leaves to measurable quality scenarios and make open goals visible. Assign each gap to a decision, an owner or later evidence.
- Prioritise scenarios with Product and Operations and check whether user and operational situations appear in the tree. Connect the order to actual usage cases and operational goals.
Read the detailed explanation
A general quality tree is a team-defined working overview: it organizes product goals, quality attributes, and concrete scenarios so priorities and open evidence are visible. Its categories and weighting reflect the product context and may overlap.
The Utility Tree in ATAM is a specific method for refining business goals into quality attributes and concrete quality scenarios. Participants rate selected scenarios separately for business importance and technical difficulty; these two ratings help focus the architecture investigation on important and challenging cases. A general quality tree may adopt this structure, but should then be explicitly identified as an ATAM Utility Tree and maintained with both ratings.
A leaf becomes concrete through a Quality Scenario; the quality overview organizes attributes and trade-offs. The parent Quality Attributes page places scenarios within quality goals.
Check your understanding
Test yourself in three stages
ReadingCheck in the picture
Which two ratings characterize prioritization in the ATAM Utility Tree?
View the solution with justification
The business importance and technical difficulty of a concrete quality scenario.
ApplyingTransferred to a new situation
A checkout scenario is important to the business but technically easy. How do you record it in the ATAM Utility Tree?
View the solution with justification
Rate its business importance and technical difficulty separately; together, the ratings help choose the analysis focus transparently.
EvaluateWeighing an alternative
When should a team overview be called a general quality tree rather than an ATAM Utility Tree?
View the solution with justification
When it groups and prioritizes goals freely without refining quality scenarios according to ATAM and rating business importance and technical difficulty.
Explore further
These building blocks continue the thoughts of this page.
References
- CMU SEI · Quality Attributes (opens in new tab)Research report on quality attributes and architecture decisions.
- CMU SEI · Scenario-Based Analysis of Software Architecture (opens in new tab)Describes scenarios for architecture evaluation.
- arc42 · Quality Requirements (opens in new tab)Practical guidance for quality scenarios and requirements.
- CMU SEI · ATAM: Method for Architecture Evaluation (opens in new tab)Primary source on the ATAM Utility Tree, quality scenarios, and their prioritization by importance and difficulty.