This post is for everyone who draws computer pictures for a living…
The genesis for this post came from a comment on the diagrams-as-code post (via LinkedIn) that called out the C4 Model[1]:
I hadn’t heard of C4 Model before so I decided to check it out. A first look at the C4 Model web site piqued my interest – Continue reading
Is a picture really worth a thousand words? What if that picture was a diagram?
A colleague recently introduced me to Diagrams as Code, using PlantUML, and in this post we explore the concept of diagrams-as-code, and how to use PlantUML.
Let’s start with some background. Diagrams should engage their audience, informing them and encouraging collaboration. Understanding the knowledge and needs of your audience is critical to creating a successful diagram.
We adjust the diagram to suit the audience, using different views of people / process / technology to inform and engage them. Often, we will draw multiple views of the same system to suit the needs of different audiences, as per Figure 1.
Figure 1 – Example of Multiple Views of the Same System to Suit Different Audiences
Bits 'n Bytes 