View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Time Blocking |  Business Strategy GAP Analysis |  Operations Change Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 | Low | Medium | Medium | High |
Timedifferent | 15-30 min Planung, laufend | 1-3 h | 45-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1 | 2-8 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | Gap Matrix, Action Plan, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 | PlanningTime managementFocus | StrategyAnalysisPlanning | ChangeRoot causeTroubleshootingComparison | ArchitectureChangeAnalysisComparisonQuality |