View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Knowledge Mapping |  Delivery RAID Log |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | High | Medium | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-12 | 1-3 maintaining, briefing for everyone | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance | KnowledgeConceptsMappingSensemaking |