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 for Golden Path
Engineering
Golden Path
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
When teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.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.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-3 Tage Setup, laufendSeveral meetings plus preparation and analysis; total effort depends on scopePreparation, scenario analysis, and findings review; effort depends on scope30 min Setup, dann laufend
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholdersArchitecture experts and stakeholders for scenarios and weighting1-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Golden Path Guide, Templates, Quality ChecksPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesRAID Log, Status Report Source
Tagsno overlap
EngineeringProductivityGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureChangeAnalysisComparisonQuality
RiskTrackingStakeholdersGovernance
Add more methods