methodatlas
Method guideArchitecture

Quality Attribute Workshop

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time2-4 h
Participants5-15
FormatWorkshop
MaturityCanonical
Prepare plan
01

Prerequisite

What needs to be finished first

Complete firstClear scope

Early system or program stage with business drivers, diverse stakeholders, and architecture still open to change.

Without a boundary, data, perspectives, or flows become mixed.
Complete firstAccess to evidence

Relevant people and sources can be included.

Gaps remain visible; missing evidence must not be invented.
02

Preparation

What needs to be ready before start

Materials

Shared workspace, accessible sources, and a decision log.

People / roles

Facilitator · stakeholders · architecture · scribe

Pre-read

Clarify the question, timeframe, data access, roles, and known uncertainties in advance.

Time needed

A full facilitated workshop; additional stakeholder groups may require further workshops.

Setup

Create a shared version. Label facts, assumptions, and decisions separately.

03

Core question

The one question this method answers

Which quality scenarios matter architecturally to business goals and need clarification first?

04

Flow

Phases with goal, actions, output and pitfall

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.

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

  1. 1

    Drivers

    Understand drivers and stakeholders

    Goal

    Are important perspectives represented?

    Inputs for this step

    • Business drivers, users, and system context

    Actions

    • Present goals, business drivers, and current architecture; identify stakeholders.
    • Are important perspectives represented?

    Output

    Consolidated business and architecture drivers

    Consolidated business and architecture drivers

    Quality check

    Are important perspectives represented?

    Pitfall

    Quality term has no scenario Add stimulus, environment, and measurable response.

    Timing: Part of the agreed work block; research may be separate.

  2. 2

    Scenarios

    Elicit quality scenarios

    Goal

    Are scenarios observable and contextual?

    Inputs for this step

    • Stakeholder needs and quality scenarios

    Actions

    • Write concrete stimulus-environment-response scenarios rather than quality adjectives.
    • Are scenarios observable and contextual?

    Output

    Quality scenarios from stakeholder perspectives

    Quality scenarios from stakeholder perspectives

    Quality check

    Are scenarios observable and contextual?

    Pitfall

    Stakeholder group missing Check user, operations, and business roles against the drivers.

    Timing: Part of the agreed work block; research may be separate.

  3. 3

    Prioritization

    Consolidate and prioritize

    Goal

    Are conflicts and trade-offs visible?

    Inputs for this step

    • Scenarios and prioritization rationale

    Actions

    • Consolidate similar items; prioritize jointly using a transparent method.
    • Are conflicts and trade-offs visible?

    Output

    Prioritized scenarios with rationale

    Prioritized scenarios with rationale

    Quality check

    Are conflicts and trade-offs visible?

    Pitfall

    Priority mistaken for architecture decision Present QAW as requirements evidence; architecture decisions follow later.

    Timing: Part of the agreed work block; research may be separate.

  4. 4

    Refinement

    Refine key scenarios

    Goal

    Can results inform architecture, prototypes, or tests?

    Inputs for this step

    • Refined stimulus-environment-response measures

    Actions

    • Add stimulus, source, environment, response, and measure; record open questions.
    • Can results inform architecture, prototypes, or tests?

    Output

    Refined stimulus-environment-response measures

    Refined stimulus-environment-response measures

    Quality check

    Can results inform architecture, prototypes, or tests?

    Pitfall

    Too many scenarios remain equally prioritized Consolidate similar cases and document prioritization rationale.

    Timing: Part of the agreed work block; research may be separate.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

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
Form

Versioned result with question, evidence, open issues, next action, ownership, and review date.

Versioning / ownership

Record date, scope, sources, and changes. Preserve earlier observations.

Tool alternatives
  • Whiteboard or paper
  • Shared spreadsheet
  • Versioned project space

quality-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

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

quality-attribute-workshop-beispiel.md

Concrete filled scenario, fictional example

Fictional worked example

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.

All names and values are invented for illustration. Unresolved explanations remain questions.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Understand drivers and stakeholdersQuality term has no scenarioView in phase
  2. Elicit quality scenariosStakeholder group missingView in phase
  3. Consolidate and prioritizePriority mistaken for architecture decisionView in phase
  4. Refine key scenariosToo many scenarios remain equally prioritizedView in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The question or boundary remains ambiguous: narrow it first.
Key data or participants are missing: label the gap and arrange access.
The group mixes observation and explanation: revisit the evidence.
An immediate safety or operational risk appears: stop and use the responsible procedures.

Where to go next?

Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record

Records the architectural response chosen for a prioritized scenario.

A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42

Anchors the refined quality scenarios in the architecture documentation.

View in playbookSafeguard Architecture Quality Before ImplementationMove from the guardrails of an architecture initiative through prioritized quality scenarios to a solution put up for review.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods