View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Contradiction AnalysisSAAM (Software Architecture Analysis Method)TRIZLASR (Lightweight Approach for Software Reviews)
| Criterion |  Innovation Contradiction Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Innovation TRIZ |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 | Medium | High | High | Medium |
Timedifferent | 60-120 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Contradiction Statement, Inventive Principles, Solution Concepts | 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 | ContradictionsInnovationProblem solving | ArchitectureChangeAnalysisComparisonQuality | InnovationProblem solvingContradictionsCreativity | ArchitectureQualityRiskAssessmentLean |