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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
HighLowLowHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope45-90 min30-60 min2-6 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-122-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsExpectation Map, Alignment Notes, AgreementsFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
AlignmentStakeholdersTeam
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods