Gernot Starke & Benjamin Wolf

Architecture Communication Canvas

Is your software documentation a 'denial of service attack'? Learn to capture an entire system's critical aspects on a single, pragmatic canvas.

Architecture Communication Canvas
#1about 3 minutes

The common problems with software architecture documentation

Most projects suffer from either no documentation, overwhelming documentation, or overly complex diagrams that are impossible to understand.

#2about 4 minutes

Understanding the canvas pattern for structured visualization

A canvas is a one-page, structured visualization tool that captures key elements of a complex topic, inspired by the Business Model Canvas.

#3about 3 minutes

A brief overview of the Arc42 documentation template

Arc42 is an open-source template with 12 chapters for structuring software architecture documentation, but it can still be too extensive for some teams.

#4about 5 minutes

Introducing the Architecture Communication Canvas

The Architecture Communication Canvas is a one-page tool structured into problem, solution, and risks sections to concisely communicate a system's design.

#5about 3 minutes

Three practical use cases for the canvas

The canvas can be used to kickstart system reviews, overcome the blank-page syndrome when starting documentation, and quickly capture essential knowledge in emergencies.

#6about 3 minutes

Real-world examples of the canvas in action

See examples of the canvas applied to a large CRM system, a small internal tool, and a simple link checker to show its scalability.

#7about 4 minutes

Team experiences and benefits of using the canvas

Teams report that creating a canvas is fast, fun, and leads to valuable insights and "aha" moments about their own system.

#8about 1 minute

Q&A on canvas implementation and maintenance

The most difficult section to write is often past "bad decisions," and the canvas should be reviewed periodically, such as every three months.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Articles

View all articles
BB
Benedikt Bischof
Humanizing Your Documentation
About the speaker:Carolyn Stransky is a journalist, software engineer, conference speaker and technical writer based in Berlin. This is how she describes herself on her website:Majority of the week, I'm a frontend engineer focused on accessibility, d...
Humanizing Your Documentation
DC
Daniel Cranney
The real reason we document our code
The world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
The real reason we document our code
BR
Benjamin Ruschin
What Developers Really Need to Create Great Code Demos
Every developer on earth has, at some point, had another developer to thank for a breakthrough, a success, an aha moment they wouldn’t have had without coming across that blog post, that open-source contribution, that reply on socials or that humble ...
What Developers Really Need to Create Great Code Demos
BB
Benedikt Bischof
Why You Shouldn’t Build a Microservice Architecture
Welcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Michael Eisenbart who talks about the pros and cons of microservice architecture.‍About the speaker:‍Michael has been working for Bosch as a sof...
Why You Shouldn’t Build a Microservice Architecture

From learning to earning

Jobs that call for the skills explored in this talk.

Software Architect

Software Architect

doubleSlash Net-Business GmbH
Friedrichshafen, Germany

Java
Azure
Agile Methodologies
Software Architecture
Continuous Integration
+1