View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Knowledge Modeling Concept Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | High | Medium |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureChangeAnalysisComparisonQuality | KnowledgeConceptsMappingSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
