View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:5-Minuten VC-CheckChange AnalysisFault IsolationSAAM (Software Architecture Analysis Method)
| Criterion |  Business Strategy 5-Minuten VC-Check |  Operations Change Analysis |  Engineering Fault Isolation |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 5-15 min | 45-120 min | 30-180 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-5 | 2-6 | 1-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | 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 |
Tagsno overlap | StartupValidationCompetition | ChangeRoot causeTroubleshootingComparison | TroubleshootingDiagnosisEngineering | ArchitectureChangeAnalysisComparisonQuality |