View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Cost of Delay | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Communication Canvas | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 90-180 min | 1-2 h | 60-120 min | 1-2 Tage |
Participantsdifferent | 3-8 | 3-10 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



