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)
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Diary Study.
UX Research
Diary Study
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.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.
Complexitydifferent
HighMediumLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope2-6 h30 min Setup, dann laufend1-4 Wochen
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-81-3 maintaining, briefing for everyone5-20
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsEvent Model, UI Flow, Commands, Read ModelsRAID Log, Status Report SourceDiary Entries, Longitudinal Patterns, Experience Timeline
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
EventsBlueprintDomain-Driven DesignBehavior
RiskTrackingStakeholdersGovernance
UX researchTrackingBehavior
Add more methods