The story behind it: Interestingly, Gernot Starke and Patrick Roos developed a canvas for software architecture work in parallel: The Architecture Communication Canvas and the Software Architecture Canvas.
We found that both "canvases" for software architecture work can be used in different phases of the software product lifecycle and complement each other.
Therefore, over the past few weeks, we have created https://canvas.arc42.org/.
Below, I briefly introduce each canvas and its goals.
Architecture Inception Canvas
The Architecture Inception Canvas is an efficient and collaborative way to define software architecture.
It's perfect for architecting new applications and software systems because it focuses heavily on the problem domain to understand it, identify risks, and collaboratively create initial architecture hypotheses.
This canvas was originally developed by Patrick Roos (also known as the "Software Architecture Canvas").
Architecture Communication Canvas
The Architecture Communication Canvas, as the name implies, is intended for the communication of existing architectures.
The Architecture Communication Canvas is the elevator pitch of software architecture and offers the most compact way to explain and communicate your system.
It was originally developed by Gernot Starke.
Tech Stack Canvas
The Tech Stack Canvas has a strong focus on the technology selection of a software system.
It often happens that the entire product team doesn't have a good overview of the entire tech stack in use. This is exactly where the Tech Stack Canvas can help.
It's also a good way to give other software engineers and/or software architects on other teams or stakeholders a quick overview of the tech stack and where the technology decisions are coming from.
So this canvas is used to create, document, and communicate the product's tech stack.