Most projects suffer from either no documentation, overwhelming documentation, or overly complex diagrams that are impossible to understand.
A canvas is a one-page, structured visualization tool that captures key elements of a complex topic, inspired by the Business Model Canvas.
Arc42 is an open-source template with 12 chapters for structuring software architecture documentation, but it can still be too extensive for some teams.
The Architecture Communication Canvas is a one-page tool structured into problem, solution, and risks sections to concisely communicate a system's design.
The canvas can be used to kickstart system reviews, overcome the blank-page syndrome when starting documentation, and quickly capture essential knowledge in emergencies.
See examples of the canvas applied to a large CRM system, a small internal tool, and a simple link checker to show its scalability.
Teams report that creating a canvas is fast, fun, and leads to valuable insights and "aha" moments about their own system.
The most difficult section to write is often past "bad decisions," and the canvas should be reviewed periodically, such as every three months.
28:11Simon Lasselsberger
24:52Hendrik Lösch
27:56Benjamin Wolf & Dr. Gernot Starke
42:02Simon Lasselsberger
43:13Carola Lilienthal
29:35Markus Harrer
30:14Eberhard Wolff
20:28Bastian Heilemann & Akash Manjunath
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Vesterling Consulting GmbH
Lionstep AG
Berlin, Germany
Vesterling Consulting GmbH
Akros Ag