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 ABC Analysis
Operations
ABC Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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.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.
Complexitydifferent
LowLowHighHigh
Timedifferent
1-4 h30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
1-51-5Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramABC Classification, Focus Rules, Control ListPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureCommunicationVisualization
PrioritizationOperationsPortfolio
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Add more methods