View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Operations MORT Analysis |  Architecture arc42 |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Mehrere Tage bis Wochen | 1-2 Tage | 2-4 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 1-4 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Architecture Document, Context View, Runtime View, Deployment View | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causeSafetySystemicIncident | ArchitectureDocumentationCommunication | Root causePatternsIncidentSystemic |