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 Teach-back.
Knowledge Modeling
Teach-back
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.
Complexitysame
LowLowLowLow
Timedifferent
5-20 min1-2 h1-4 h1-2 Tage
Participantsdifferent
2-83-101-51-4
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsArchitecture Canvas, Goals, Constraints, Quality AttributesContext Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
LearningUnderstandingCommunication
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
Add more methods