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 VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
MediumHighMediumHigh
Timedifferent
90-180 minPreparation, scenario analysis, and findings review; effort depends on scope1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-6Architecture experts and stakeholders for scenarios and weighting4-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
VRIO Table, Strategic ActionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesAlignment Map, Open Issues, Decision QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
StrategyDiagnosisBusiness modelCapability
ArchitectureChangeAnalysisComparisonQuality
AlignmentStakeholdersStrategyFacilitation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods