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)RAID LogLASR (Lightweight Approach for Software Reviews)
| Criterion |  Innovation TRIZ |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium |
Timedifferent | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Async | 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 | RAID Log, Status Report Source | 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 | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean |