View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)DIBBSAAM (Software Architecture Analysis Method)Assumption Surfacing
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Strategy DIBB |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 h | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | DIBB document, Belief list, Bet list, Learning report | 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 alternatives | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyDecisionAssumptionsHypothesis | ArchitectureChangeAnalysisComparisonQuality | AssumptionsRiskDecisionDiscovery |