View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Operations Fault Tree Analysis | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Low | High | Low |
Timedifferent | 30 min Setup, dann laufend | 2-6 h | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskRoot causeSafety | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






