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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
Paper illustration of VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalPreparation, scenario analysis, and findings review; effort depends on scopeHalf day90-180 min
Participantsdifferent
Designers, developers as users, and facilitationArchitecture experts and stakeholders for scenarios and weighting3-83-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesValue Chain Map, Lever ListVRIO Table, Strategic Actions
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureChangeAnalysisComparisonQuality
StrategyBusiness modelDiagnosisAnalysis
StrategyDiagnosisBusiness modelCapability
Add more methods