View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Family Tree Analysis |  Architecture arc42 |  Architecture Views and Beyond |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | Medium | High |
Timedifferent | 2-4 h | 1-2 Tage | 1-3 Tage | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 1-4 | 1-4 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causePatternsIncidentSystemic | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture | Root causeSafetySystemicIncident |