View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Behavior Over Time GraphViews and BeyondATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)
| Criterion |  Systems Thinking Behavior Over Time Graph |  Architecture Views and Beyond |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 20-45 min | 1-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-10 | 1-4 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Behavior Over Time Graph, Trend Hypotheses, Key Events | Architecture Views, Cross-view Notes, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | Systems thinkingPatternsDynamics | DocumentationStakeholdersArchitecture | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean |