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 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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.
Complexitydifferent
LowLowHighLow
Timedifferent
20-60 min1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage
Participantsdifferent
11-5Evaluation team, architects, and relevant stakeholders1-4
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesContext Diagram, Container Diagram, Component DiagramPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
LearningKnowledgeUnderstanding
ArchitectureCommunicationVisualization
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
Add more methods