View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Engineering Goal Question Metric |  Business Strategy GAP Analysis |  Product Strategy SMART Goals |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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 goals are formulated too generally, it brings measurability, direction, and timing into shape. It prevents intentions from staying without clear verification. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 90-180 min | 1-3 h | 15-30 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 2-8 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 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 | GQM Table, Metric Profiles | Gap Matrix, Action Plan, Risk Notes | SMART Goal, Measurement Note, Deadline |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | MetricsMeasurementEngineeringAlignment | StrategyAnalysisPlanning | GoalsPlanningMeasurementAlignment |