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)TRIZATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Innovation Contradiction Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Innovation TRIZ |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 60-120 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Evaluation team, architects, and relevant stakeholders |
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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ContradictionsInnovationProblem solving | ArchitectureChangeAnalysisComparisonQuality | InnovationProblem solvingContradictionsCreativity | ArchitectureQualityRiskTradeoffsStakeholders |