Purpose
A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.
Architecture Workshop method
Quality Attribute Workshop
Derives prioritized, testable quality scenarios for an early system architecture from business goals.
Quality Attribute Workshop translates business goals into prioritized, testable scenarios that make architectural trade-offs and quality risks discussable early. The resulting scenarios provide a focused basis for architecture decisions and validation.
Which quality scenarios matter architecturally to business goals and need clarification first?
- Participants
- 5-15
- Time
- 2-4 h
Phases may be revisited; their order supports the work but does not replace domain judgment.
Drivers
Understand drivers and stakeholders
Present goals, business drivers, and current architecture; identify stakeholders.
Scenarios
Elicit quality scenarios
Write concrete stimulus-environment-response scenarios rather than quality adjectives.
Prioritization
Consolidate and prioritize
Consolidate similar items; prioritize jointly using a transparent method.
Refinement
Refine key scenarios
Add stimulus, source, environment, response, and measure; record open questions.
Review the result and open assumptions at the next suitable checkpoint. Record changes, ownership, and new evidence.
A good fit when
Use when: Early system or program stage with business drivers, diverse stakeholders, and architecture still open to change.
Ideal for
- Early Architecture
- Mission-critical Systems
- Quality Attribute Discovery
Not good for
- Cosmetic optimization
- Tiny systems
Outputs
Working picture
Goals, business drivers, current architecture, and relevant stakeholders.
Testable evidence
Consolidated similar scenarios with joint prioritization using a transparent method.
Next step
Quality scenarios with stimulus, source, environment, response, measure, and open questions.
Prioritized quality scenarios, not a finished architecture
Fictional worked example
Derive prioritized, testable quality scenarios for an early system architecture from business goals.
Driver
Record business goals, system context, and represented roles.
Enrollment week must provide reliable access.
Scenario
Write concrete stimulus, context, and response scenarios.
900 requests/min; p95 <2 s; 99.9% successful sign-ins; no duplicate loans.
Priority
Record consolidated scenarios and prioritization rationale.
Priority 1 of 8 because access is time-critical; stakeholders: operations, library, students.
Open question
Add source, quality attribute, and testable response.
Load test should verify data integrity at peak; architecture is not decided by this alone.
Fictional library platform. Scenario: during enrollment week requests rise to 900/min; service maintains 99.9% successful sign-ins and p95 response under 2 s without duplicate loans. Prioritized above “dashboard loads faster” because access is operationally critical.
Quality Attribute Workshop Collection · Software Engineering Institute
First step
Start with a bounded question, clarify access and participants, and collect available evidence. Derive prioritized, testable quality scenarios for an early system architecture from business goals.
Deep dive
How it works
The group first gathers the key quality goals and refines them into measurable scenarios. Priorities, risks, and architectural consequences are then evaluated together. The result is clear qualities that can be pursued further in architecture and implementation.
In detail
The workshop holds up because quality goals only gain architectural sharpness once they are translated into concrete scenarios and trade-offs. Good facilitation keeps availability, security, changeability, or performance not as buzzwords but as checkable expectations in real usage situations. This makes architecture decisions more solid, because it becomes visible which quality takes precedence in which situation and what it costs.
Facilitation
Prepare a few realistic scenarios where quality requirements come under pressure so the conversation doesn't stay generic. The tipping point comes when two important qualities visibly conflict. Close with prioritized scenarios, named trade-offs, and a follow-up trail for the riskiest quality question.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Quality Attribute Workshop: WorksheetPrepare Quality Attribute Workshop with a clear question, roles, and sources.markdown
Quality Attribute Workshop: WorksheetPrepare Quality Attribute Workshop with a clear question, roles, and sources.
markdownquality-attribute-workshop-working-template.md
Prepare Quality Attribute Workshop with a clear question, roles, and sources.
Quality Attribute Workshop: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Plan the full method Time: Set according to scope and available evidence
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared workspace, accessible sources, and a decision log.
- Roles: Facilitator · stakeholders · architecture · scribe
- Advance information: Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
- Overall time needed: A full facilitated workshop; additional stakeholder groups may require further workshops.
- Setup: Create a shared version. Label facts, assumptions, and decisions separately.
Prepare for the work steps
Drivers: Understand drivers and stakeholders
- Business drivers, users, and system context
Scenarios: Elicit quality scenarios
- Stakeholder needs and quality scenarios
Prioritization: Consolidate and prioritize
- Scenarios and prioritization rationale
Refinement: Refine key scenarios
- Refined stimulus-environment-response measures
Prioritized quality scenarios, not a finished architecture
Driver
Record business goals, system context, and represented roles.
...
Scenario
Write concrete stimulus, context, and response scenarios.
...
Priority
Record consolidated scenarios and prioritization rationale.
...
Open question
Add source, quality attribute, and testable response.
...
Blank worksheet: start with a bounded question. Enter observed facts only, mark assumptions, and record open questions and sources.
Quality Attribute Workshop Collection · Software Engineering Institute
Drivers: Understand drivers and stakeholders
Expected artifact: Consolidated business and architecture drivers
Consolidated business and architecture drivers
Entry:
...
- Are important perspectives represented?
Scenarios: Elicit quality scenarios
Expected artifact: Quality scenarios from stakeholder perspectives
Quality scenarios from stakeholder perspectives
Entry:
...
- Are scenarios observable and contextual?
Prioritization: Consolidate and prioritize
Expected artifact: Prioritized scenarios with rationale
Prioritized scenarios with rationale
Entry:
...
- Are conflicts and trade-offs visible?
Refinement: Refine key scenarios
Expected artifact: Refined stimulus-environment-response measures
Refined stimulus-environment-response measures
Entry:
...
- Can results inform architecture, prototypes, or tests?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/quality-attribute-workshop/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Architecture
Architecture Inception Canvas
Instead of Quality Attribute Workshop, when you want to bundle the first architecture questions into a concise kickoff sheet.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Examines how architecture decisions support important quality goals and makes risks and trade-offs visible.
Architecture
SAAM (Software Architecture Analysis Method)
Uses concrete tasks to show how well an architecture supports use and change.
Architecture
Risk Storming
Moves architecture context, options, and consequences toward a concrete result through "place the architecture diagram or plan in the center", "set risk categories such as technical, organizational, and external", and "assign an owner and next steps for each top risk".
Architecture
Software Architecture Canvas
Gathers system goals, constraints, and building blocks into a compact view for early architecture decisions.
Architecture
LASR (Lightweight Approach for Software Reviews)
Helps a small team assess the main quality risks in its software and choose where to investigate further.
Constraints and origin
MediumWorkshop2-4 h
Profile
- Method form
- Workshop method
- Participants
- 5-15
- Time
- 2-4 h
- Maturity
- Canonical
Next up: Architecture Decision Record