View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Stock and Flow DiagramLASR (Lightweight Approach for Software Reviews)ARID (Active Reviews for Intermediate Designs)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Stock and Flow Diagram |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | High | High | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-6 | 1 or a small team; particularly suitable for 3–4 people | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses | 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 | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | DynamicsSimulationFeedbackSystems thinking | ArchitectureQualityRiskAssessmentLean | ArchitectureEngineeringFeedbackValidationTasks |