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 arc42 | ![]() Operations Scatter Diagram | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | Low | High |
Timedifferent | 1-2 Tage | 30-90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-4 | 1-4 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 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 | ArchitectureDocumentationCommunication | Root causeQualityVisualization | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






