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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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
1-2 h15-45 min1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-81-33-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeADR File, Decision Log, RationaleKnowledge Map, Critical Knowledge Areas, Transfer PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureRationaleDocumentationGovernance
KnowledgeMappingRisk
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods