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 considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowLowMediumHigh
Timedifferent
15-45 min30–60 min per interview1-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-31 participant per interview1-4Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleInterview Notes, Themes, Insight SummaryArchitecture Views, Cross-view Notes, RationalePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
QualitativeResearchCustomerDiscovery
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods