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 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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a Strategy Canvas with several value curves
Business Strategy
Blue Ocean Strategy Canvas
Purposedifferent
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.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.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.The Blue Ocean Strategy Canvas shows how an offering is positioned relative to the market. Differentiation thereby becomes tangible in value factors instead of merely being claimed.
Complexitydifferent
MediumHighHighMedium
Timedifferent
1-2 hPreparation, scenario analysis, and findings review; effort depends on scopeSeveral meetings plus preparation and analysis; total effort depends on scope2-4 h
Participantsdifferent
2-8Architecture experts and stakeholders for scenarios and weightingEvaluation team, architects, and relevant stakeholders3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Business Model Canvas, Assumption List, Business HypothesesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsStrategy Canvas, Value Curve, ERRC Actions
Tagsno overlap
Business modelStrategyValueInnovation
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskTradeoffsStakeholders
StrategyPositioningInnovationValue
Add more methods