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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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.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.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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h1-2 h
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholders3-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsKnowledge Map, Critical Knowledge Areas, Transfer PlanConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureQualityRiskTradeoffsStakeholders
KnowledgeMappingRisk
KnowledgeConceptsMappingSensemaking
Add more methods