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 arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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 strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
LowMediumHighHigh
Timedifferent
1-2 Tage1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
1-41-8Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArgument Map, Evidence Gaps, Decision RationalePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
ArchitectureDocumentationCommunication
SensemakingDecisionRationale
ArchitectureQualityRiskTradeoffsStakeholders
RiskDecisionSensemaking
Add more methods