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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.
Complexitydifferent
MediumHighHighMedium
Timedifferent
1-3 h2-4 hPreparation, scenario analysis, and findings review; effort depends on scope1-3 h
Participantsdifferent
3-123-8Architecture experts and stakeholders for scenarios and weighting3-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesSystem Map, Dependencies, Leverage Points
Tagsno overlap
KnowledgeMappingRisk
Theory of ConstraintsSystems thinkingChange
ArchitectureChangeAnalysisComparisonQuality
Systems thinkingMappingBoundariesChange
Add more methods