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
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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
A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.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.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.
Complexitydifferent
LowHighLowLow
Timedifferent
30-90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h1-2 Tage
Participantsdifferent
2-10Evaluation team, architects, and relevant stakeholders1-51-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Rich Picture, Problem Framing NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Systems thinkingSoft systemsFramingVisualization
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
Add more methods