View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisIBISLASR (Lightweight Approach for Software Reviews)Architecture Decision Record
| Criterion | ![]() Systems Thinking CATWOE Analysis | ![]() Knowledge Modeling IBIS | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-45 min |
Participantsdifferent | 3-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Issue Map, Positions, Argument Notes | 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 | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingFramingStakeholders | RationaleKnowledgeDecision | ArchitectureQualityRiskAssessmentLean | ArchitectureRationaleDocumentationGovernance |



