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)GAP AnalysisStakeholder MappingSAAM (Software Architecture Analysis Method)
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Business Strategy GAP Analysis |  Facilitation Stakeholder Mapping |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Medium | Medium | Low | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 60–90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-8 | Architecture experts and stakeholders for scenarios and weighting |
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 | Gap Matrix, Action Plan, Risk Notes | Stakeholder Map, Engagement Plan, Risk Notes | 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 |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyAnalysisPlanning | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality |