Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Architecture Communication Canvas – Useful Docu...

Architecture Communication Canvas – Useful Documentation in less than 60 Minutes

Updated version of the original Canvas presentation

Avatar for Ben Wolf

Ben Wolf

July 29, 2026

More Decks by Ben Wolf

Other Decks in Programming

Transcript

  1. „Jedes Problem lässt sich mit gutem Kaffee lösen.“ Benjamin Wolf

    Coffee Consultant bei INNOQ Consultant für Architekturentwicklung / -dokumentation Trainer für iSAQB Foundation, IMPROVE und ADOC arc42-Fan und -Maintainer Kaffeegenussspecht
  2. Assumption You • need* to document • have limited time

    * if we were younger and naive, we would have written „want“
  3. once upon a time… best research system for authors online

    news media - php - old linux version structure daily content J Smith PO A Markov CTO - newsfeed aggregator comp - news validator comp - news summarizing comp J Smith PO A Markov CTO people leaving lib updates too often int news aggregato r - java - TS - node - headline viewer - layout preview Security advisory CSO DIY sec considered bad practice all libs and OS Github bot - Python - Bash - make - scanner - owasp-10 reader -
  4. explained by chatGPT 3 Canvas (1) k c o l

    B https://chat.openai.com/share/ce9455a9-4d17-4e32-a590-a53136ea481a In software engineering, a D i r canvas typically refers to a R t *!$§* E e NO P visual container where users can interact and manipulate elements to create or modify content.
  5. explained by us Canvas (2) ... A canvas is a

    structured D i visualization that r R t E k e c P YES! o facilitates understanding l B and analysis of key elements of specific topics..
  6. Thanks, Patrick! What should the software do? How can we

    achieve it? for new systems How do we evaluate the situation? https://canvas.arc42.org/architecture-inception-canvas
  7. arc42 in a nutshell 1. Introduction and Goals 1.1 Requirements

    Overview 1.2 Quality Goals Main requirements, especially quality goals 8. Crosscutting Concepts 3. System Scope and Context -> external interfaces Neighbouring systems and external interfaces 9. Architecture Decisions 4. Solution Strategy 1. Introduction and Goals 7. Deployment View 2. Constraints 3. System Scope and Context 4. Solution Strategy 10. Quality Requirements Core idea of the solution, suggestion: bullet points only 5. Building Block View Top-level structure of the code 8. Crosscutting Concepts Cross-cutting concepts, highly detailed 9. Architecture Decisions Important architecture decisions, incl. decision makers and date 5.1. Whitebox Overall System (Level 1) 5. Building Block View 11. Risks & Technical Debt 6. Runtime View 12. Glossary 29
  8. Use Canvas for: Reviews • Create canvas prior to review

    • Common understanding • Remind participants of „everything“
  9. B D i r R t E k e “Wow,

    that was fast!?” c P o l
  10. “Great, D i r R t E k e now

    I don’t have to talk c P o l B to people anymore!”
  11. “First time documenting D i r R t E k

    e architecture – and c P o l B I really enjoyed it!”
  12. “I never understood technical D i r R t E

    k e stuff, but this canvas? c P o l B It helps A LOT!”
  13. Things that didn’t work out Infrastructure Photo by Mika Baumeister

    on Unsplash People Photo by mauro mora on Unsplash
  14. Things that didn’t work out Infrastructure Photo by Mika Baumeister

    on Unsplash People https://atlassian.design/foundations/logos Photo by mauro mora on Unsplash
  15. Acht Inklusive neuem Ka pitel: AI Opportu nity Canvas •

    verschiedene Canvas-Ansätze • von neun Expert:innen erklärt
  16. D i “But… what about r R t E k

    e c P o l microservices?” B