View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:TRIZATAM (Architecture Tradeoff Analysis Method)Contradiction AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Innovation TRIZ |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Contradiction Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | High | High | Medium | Medium |
Timedifferent | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | 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 | InnovationProblem solvingContradictionsCreativity | ArchitectureQualityRiskTradeoffsStakeholders | ContradictionsInnovationProblem solving | ArchitectureQualityRiskAssessmentLean |