The Software Architecture Canvas is now part of arc42 🎉

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/.

In addition, INNOQ has developed the Tech Stack Canvas.

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").

Patrick Roos’s Architecture Inception Canvas template | Miroverse

Discover how Patrick Roos does Architecture Inception Canvas in Miro with Miroverse, the Miro Community Templates Gallery. View Patrick’s Miro Templates

Miroverse

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.

arc42 (Gernot Starke)’s Architecture Communication Canvas template | Miroverse

Discover how arc42 (Gernot Starke) does Architecture Communication Canvas in Miro with Miroverse, the Miro Community Templates Gallery. View arc42’s Miro Templates

Miroverse

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.

Joerg M.’s Tech Stack Canvas template | Miroverse

Discover how Joerg M. does Tech Stack Canvas in Miro with Miroverse, the Miro Community Templates Gallery. View Joerg’s Miro Templates

Miroverse

Resources

Software Architecture Canvas

As lean as architecture documentation can ever get

Software Architecture CanvasGernot Starke, Patrick Roos and arc42 contributors.

GitHub - arc42/canvas.arc42.org-site: Software Architecture Canvas

Software Architecture Canvas. Contribute to arc42/canvas.arc42.org-site development by creating an account on GitHub.

GitHubarc42

Tech Stack Canvas

Create, document and communicate your product’s tech stack.