View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fishbone DiagramMorphological AnalysisLASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Operations Fishbone Diagram |  Innovation Morphological Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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. | 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 | Low | Medium | Medium | High |
Timedifferent | 30-60 min | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Morphological Box, Concept Combinations, Idea Shortlist | 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 | 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 | Root causeQualityOperations | IdeationInnovationCreativity | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders |