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 for Diary Study.
UX Research
Diary Study
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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
MediumHighMediumHigh
Timedifferent
1-4 Wochen2-6 h2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-203-102-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineFMEA Table, Risk Priority, Mitigation ActionsEvent Model, UI Flow, Commands, Read ModelsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
UX researchTrackingBehavior
RiskQualityOperationsRoot cause
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods