View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Soft Systems Methodology |  Delivery RAID Log |  Architecture arc42 |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 0.5-3 Tage | 30 min Setup, dann laufend | 1-2 Tage | 1-3 Tage |
Participantsdifferent | 5-15 | 1-3 maintaining, briefing for everyone | 1-4 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture |