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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Communication Plan
Delivery
Communication Plan
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.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.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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
MediumMediumLowHigh
Timedifferent
1-2 h1-3 Wochen vom Draft bis zur Entscheidung45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-103-20 Reviewer2-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Radar Map, Capability Scores, Action AreasRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCommunication Plan, Channel Matrix, Message CadencePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
AssessmentPortfolioCapability
ArchitectureDecisionAsyncGovernance
CommunicationStakeholdersDeliveryPlanning
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods