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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Communication Plan
Delivery
Communication Plan
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
HighLowMediumLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope45-90 min1-3 Tage1-2 Tage
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-61-41-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Plan, Channel Matrix, Message CadenceArchitecture Views, Cross-view Notes, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
CommunicationStakeholdersDeliveryPlanning
DocumentationStakeholdersArchitecture
ArchitectureDocumentationCommunication
Add more methods