An important outcome of software architecture work is a set of diagrams that help explain high level decisions on the system. Traditionally, these diagrams were built in complex UML modeling tools like Microsoft Visio or Enterprise Architect. More recently, the agile approach has moved a lot of these diagrams into hand drawings – for better and for worse, since hand drawings don’t necessarily look good, are difficult to change, and are not standard.
Another solution has emerged from this tension, a practical solution that appeals to programmers: using code to create the architecture models and diagrams.
In this webinar, Alex Bolboaca shows examples using PlantUML and Structurizr, discusses the advantages and disadvantages of this diagramming approach and answered questions about software architecture and diagrams.