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 ATAM (Architecture Tradeoff Analysis Method) |  Architecture arc42 |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage | 1-3 h |
Participantsdifferent | 1-8 | Evaluation team, architects, and relevant stakeholders | 1-4 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Document, Context View, Runtime View, Deployment View | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDocumentationCommunication | KnowledgeMappingRisk |