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)VRIO FrameworkLASR (Lightweight Approach for Software Reviews)Value Chain Analysis
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Business Strategy VRIO Framework |  Architecture LASR (Lightweight Approach for Software Reviews) |  Business Strategy Value Chain Analysis |
|---|---|---|---|---|
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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 90-180 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Half day |
Participantsdifferent | Designers, developers as users, and facilitation | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | VRIO Table, Strategic Actions | 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 | Value Chain Map, Lever List |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyDiagnosisBusiness modelCapability | ArchitectureQualityRiskAssessmentLean | StrategyBusiness modelDiagnosisAnalysis |