View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:GAP AnalysisSAAM (Software Architecture Analysis Method)Getting Things DoneATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy GAP Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Getting Things Done |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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 | Medium | High | Medium | High |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h Setup, laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 1 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Gap Matrix, Action 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 | Action Lists, Project List, Review Routine | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureChangeAnalysisComparisonQuality | ProductivityPlanningTasksExecution | ArchitectureQualityRiskTradeoffsStakeholders |