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 two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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)
Purposedifferent
The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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.
Complexitydifferent
LowMediumHighHigh
Timedifferent
45-90 min15-60 min je ZyklusSeveral meetings plus preparation and analysis; total effort depends on scopePreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-81-8Evaluation team, architects, and relevant stakeholdersArchitecture experts and stakeholders for scenarios and weighting
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Ansoff Matrix, Growth Options, Risk NotesSituation Assessment, Decision Loop, Action UpdatesPrioritized 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 alternatives
Tagsno overlap
GrowthStrategyMarketPortfolio
DecisionChangeLearningStrategy
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureChangeAnalysisComparisonQuality
Add more methods