loading...
Cover image for Modelling software architecture with PlantUML

Modelling software architecture with PlantUML

simonbrown profile image Simon Brown Updated on ・3 min read

Software architecture diagrams as text (5 Part Series)

1) Modelling software architecture with PlantUML 2) Software architecture diagrams - which tool should we use? 3) Visio, draw.io, LucidChart, Gliffy, etc - not recommended for software architecture diagrams 4) Getting started with the Structurizr DSL 5) Getting started with the Structurizr CLI

Creating software architecture diagrams from text is becoming more popular. Text is easy to work with, and it's version controllable, so it can be stored alongside your source code. Tools like PlantUML, Mermaid, and WebSequenceDiagrams have auto-layout algorithms that allow us to focus on content too.

In conjunction with the C4 model, it's relatively straightforward to create a collection of diagrams to describe the project/product you're working on, at different levels of abstraction. For example, here's a System Context diagram to describe a pet clinic information management system.

An example System Context diagram

And here's a Container diagram showing the internals of the software system.

An example Container diagram

But wait!

Did you spot the two errors in the Container diagram? Let's look at the diagrams next to each other.

The two diagrams next to each other

  • "Clinic Employee" has changed to "Clinic Staff".
  • The arrow style has changed from dashed to solid.

Granted these are only minor differences, but the problem I want to raise is one of consistency. If you're defining two diagrams in two separate text files, it's easy to make mistakes. Also, perhaps we wanted to change the name of the user from "Clinic Employee" to "Clinic Staff", but perhaps we forgot to change both files or regenerate them both. Some of these problems can be partially solved with the global search and replace tooling we have at our disposal as software developers. And some problems can be solved by integrating the diagram generation process into a CI/CD pipeline. But there's a better way.

Make models, not diagrams

What we're missing here is a single definition of the elements and relationships across all of our diagrams. When writing code, we often talk about DRY (Don't repeat yourself), where we try to avoid unnecessary duplication through copy-pasting code. That's exactly how many people create their diagrams though, by copy-pasting diagram definition fragments. PlantUML does support the concept of an !include directive to include fragments, but this can become complicated.

What we really want to do is create a model of our software architecture, and then visualise it from different angles. The Structurizr DSL is an open source project that lets you do just this. Instead of writing two separate PlantUML files, we can define everything in a single file as follows.

workspace {

    model {
        clinicEmployee = person "Clinic Employee" "An employee of the clinic"
        springPetClinic = softwareSystem "Spring PetClinic" "Allows employees to view and manage information regarding the veterinarians, the clients, and their pets." {
            webApplication = container "Web Application" "Allows employees to view and manage information regarding the veterinarians, the clients, and their pets." "Java and Spring"
            database = container "Database" "Stores information regarding the veterinarians, the clients, and their pets." "Relational Database Schema"
        }

        clinicEmployee -> webApplication "Uses" "HTTPS"
        webApplication -> database "Reads from and writes to" "JDBC"
    }

    views {
        systemContext springPetClinic {
            include *
        }

        container springPetClinic {
            include *
        }
    }

}

This text defines a model containing: a user, a software system, two containers, and the relationships between everything. It also then defines two views of this model: one System Context view, and one Container view.

The DSL is a way to define software architecture models and views, but we still need a way to visualise that, and ultimately get some diagrams. We can do this with the Structurizr CLI, another open source project that has a number of features.

./structurizr.sh export -workspace spring-petclinic.dsl -format plantuml

Running the Structurizr CLI in this way will create two .puml files, which we can then render with PlantUML in the normal way.

Example System Context and Container diagrams

Because both diagrams are created from the same model, they remain in sync, both from a content and a presentation perspective. Changes can now be made to the original DSL source file, and the diagrams regenerated.

Summary

Creating software architecture diagrams from a textual definition is becoming more popular, but it's easy to introduce inconsistencies into your diagrams if you don't keep the multiple source files in sync. The open source Structurizr DSL and Structurizr CLI can help you create multiple diagrams from the same model.

Software architecture diagrams as text (5 Part Series)

1) Modelling software architecture with PlantUML 2) Software architecture diagrams - which tool should we use? 3) Visio, draw.io, LucidChart, Gliffy, etc - not recommended for software architecture diagrams 4) Getting started with the Structurizr DSL 5) Getting started with the Structurizr CLI

Posted on by:

simonbrown profile

Simon Brown

@simonbrown

Author "Software Architecture for Developers" | Creator of the "C4 model for visualising software architecture" | Founder at Structurizr | Software architecture training at architectis.je

Discussion

markdown guide
 

Good points! You convinced me! Damn! Now I have 3 more tools to learn...