View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Argument Mapping |  Knowledge Modeling IBIS |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 h | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | 1-3 h |
Participantsdifferent | 1-8 | Architecture experts and stakeholders for scenarios and weighting | 1-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | 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 | Argument Map, Evidence Gaps, Decision Rationale | Issue Map, Positions, Argument Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ArchitectureChangeAnalysisComparisonQuality | SensemakingDecisionRationale | RationaleKnowledgeDecision |