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 scorecard with four perspectives, connected objective cards and columns for measures, targets and initiatives.
Business Strategy
Balanced Scorecard
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures.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.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
LowHighMediumHigh
Timedifferent
1-2 TageHalber Tag bis mehrere Wochen1-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-44-121-4Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewBalanced Scorecard, Strategic Measures, Initiative MapArchitecture Views, Cross-view Notes, RationalePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureDocumentationCommunication
StrategyMetricsExecution
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods