View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Decision Making Decision Tree |  Operations Barrier Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 30-90 min | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-8 | 1-6 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Decision Tree, Option Map, Assumption List | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DecisionTreeOptions | Root causeSafetyIncident | Root causeSafetySystemicIncident |