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
Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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
MediumLowMediumHigh
Timedifferent
1-2 h1-2 Tage1-3 Wochen vom Draft bis zur EntscheidungSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-121-43-20 ReviewerEvaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsArchitecture Document, Context View, Runtime View, Deployment ViewRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureDocumentationCommunication
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods