View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Argument MappingLASR (Lightweight Approach for Software Reviews)Risk Matrix
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Argument Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Risk Matrix |
|---|---|---|---|---|
Purposedifferent | 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-8 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Argument Map, Evidence Gaps, Decision Rationale | 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 | Risk Matrix, Top Risk List |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | SensemakingDecisionRationale | ArchitectureQualityRiskAssessmentLean | RiskDecisionPrioritizationAssessment |