View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Shape-First Modeling |  Delivery RAID Log |  Architecture arc42 |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Halber Tag pro Domain Slice | 30 min Setup, dann laufend | 1-2 Tage | 60-90 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | Knowledge graphValidationSemantic | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | RiskArchitectureWorkshopValidation |