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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of a Business Model Canvas with nine connected compartments, a few notes and symbols for customers, delivery and economic relationships.
Business Strategy
Business Model Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Purposedifferent
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.The Business Model Canvas condenses a business model to its key building blocks and assumptions. It makes variants quickly comparable and reveals gaps before validation or implementation begins.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.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.
Complexitydifferent
HighMediumHighHigh
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope1-2 hSeveral meetings plus preparation and analysis; total effort depends on scopeHalf day
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting2-8Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesBusiness Model Canvas, Assumption List, Business HypothesesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsStress Test Report, Action Plan per Scenario
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Business modelStrategyValueInnovation
ArchitectureQualityRiskTradeoffsStakeholders
StrategyBusiness modelRiskDiagnosis
Add more methods