methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
1-3 Tage2-4 h60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Internes Team5-154-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesQuality Scenarios, Priority List, Architecture ConcernsAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ResearchCustomerSynthesis
RequirementsArchitectureWorkshop
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods