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 |  Architecture arc42 |  Operations Barrier Analysis |  Operations MORT 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. | 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 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 | Low | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-20 Reviewer | 1-4 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | Root causeSafetyIncident | Root causeSafetySystemicIncident |