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 of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
LowMediumHighLow
Timedifferent
1-4 hWochen bis Monate je LernzyklusSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
1-52-8Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramHypothesis list, MVPs, Learning reports, Pivot or persevere decisionPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ArchitectureCommunicationVisualization
LeanStartupValidationMVP
ArchitectureQualityRiskTradeoffsStakeholders
RiskArchitectureWorkshopValidation
Add more methods