View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Knowledge Modeling Concept Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 45-120 min | 1-2 h | Preparation, scenario analysis, and findings review; effort depends on scope | 30-60 min |
Participantsdifferent | 2-6 | 1-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | KnowledgeConceptsMappingSensemaking | ArchitectureChangeAnalysisComparisonQuality | Root causeQualityOperations |