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 of Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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
LowMediumLowHigh
Timedifferent
1-2 Tage90-180 min30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-44-121-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPlanning Levels Map, Cadence Model, Planning Artifact InventoryRAID Log, Status Report SourcePrioritized 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
CadenceGovernanceExecution
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods