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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.
Complexitydifferent
LowLowHighHigh
Timedifferent
1-4 h5-20 min2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-52-83-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramUnderstanding Check, Clarification Notes, Learning GapsFMEA Table, Risk Priority, Mitigation ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureCommunicationVisualization
LearningUnderstandingCommunication
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods