methodatlas
Architecture

Quality Attribute Workshop

Turns architecture context, options, and consequences into a tangible result by collecting stakeholder goals, eliciting quality scenarios, and documenting architecture implications.

Core question
Which Quality Attributes with which concrete scenarios are architecture-critical for the system, and in which order must they be addressed?
MediumWorkshop2-4 h
Open runsheetPlan sessionStart comparison
Purpose

The method helps clarify architecture context, options, and consequences concretely. It structures technical context, alternatives, and implications. The outcome is captured as quality scenarios, priority list, and architecture concerns.

How it works

The team follows the steps: collect stakeholder goals, elicit quality scenarios, prioritize scenarios, discuss trade-offs, and document architecture implications. Each step is captured visibly. At the end, quality scenarios, a priority list, and architecture concerns are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Quality Attribute Workshop · Utility TreeStakeholder-Szenarien in Qualitätsattribute, Utility Tree und priorisierte Architekturtreiber übersetzen
Quality Attribute WorkshopDas Visual zeigt Stakeholder-Szenarien, Utility Tree, Qualitätsattribute und Priorisierung nach Business Value und Risiko.Qualitätsanforderungen als Architekturtreiber priorisierenQAW verbindet konkrete Szenarien mit Attributen und bewertet, welche Qualität architekturrelevant ist.sammelnbewertenverfeinernTreiberStakeholder-SzenarienStimulus, Umgebung, Antwort,MaßUtility TreeQualitätsattribute strukturierenPrioritätBusiness Value × RisikoPerformancep95 < 200 msAvailabilityFailover < 2 minSecurityAuthZ geprüft

Flow

  1. 1Collect stakeholder goals
  2. 2Elicit quality scenarios
  3. 3Prioritize scenarios
  4. 4Discuss trade-offs
  5. 5Document architecture implications

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Early Architecture
  • Mission-critical Systems
  • Quality Attribute Discovery

Not good for

  • Cosmetic optimization
  • Tiny systems

Deep dive

In detail

Quality Attribute Workshop follows a clear working logic: collect stakeholder goals, elicit quality scenarios, prioritize scenarios, discuss trade-offs, and document architecture implications. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, quality scenarios, priority list, and architecture concerns support decisions, learning, or further planning.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan about 2-4 h with 5-15 people and use the format in a facilitated workshop. The method needs clear structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Quality ScenariosPriority ListArchitecture Concerns
Tags
quality attributesrequirementsarchitectureworkshop

Sources

Quality Attribute Workshop Collection | CMU Software Engineering Institutesei.cmu.eduWhat is Quality? Definition of Quality by Different Authorsqualityze.com
Artifact templates
Quality Attribute Workshop Working TemplateCompact working template for Quality Attribute Workshop with context, input, output artifacts, and next step.
markdown

quality-attribute-workshop-working-template.md

Compact working template for Quality Attribute Workshop with context, input, output artifacts, and next step.

Quality Attribute Workshop Working Template

Goal

A structured workshop for architecture-critical quality attributes and scenarios.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Quality Scenarios:
  • Priority List:
  • Architecture Concerns:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Architecture Inception Canvas

Statt Quality Attribute Workshop, wenn du die ersten Architekturfragen in einer knappen Startfolie bündeln willst.

Similar methods

All methods
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

Turns architecture context, options, and outcomes into a tangible result by naming the system and goals, gathering stakeholders and constraints, and documenting decisions and questions.

Architecture
Request for Comments

Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.

Architecture
Views and Beyond

Turns architecture context, options, and outcomes into a tangible result by identifying stakeholders, selecting views, and validating completeness.

Architecture
arc42

Turns architecture context, options, and consequences into a tangible result by capturing goals and stakeholders, scoping context, and linking risks and decisions.

Architecture
Architecture Decision Record

Turns architecture context, options, and consequences into a tangible result by naming the decision, describing context, and capturing consequences.