methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.
Complexitydifferent
HighLowLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope20-60 min1-4 h1-2 Tage
Participantsdifferent
Evaluation team, architects, and relevant stakeholders11-51-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPlain-language Explanation, Knowledge Gaps, Study NotesContext Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
LearningKnowledgeUnderstanding
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
Add more methods