Diagrams as code is becoming a popular way to diagram software architecture, peculiarly for long-lived high-level documentation - compose the diagram origin in a text-based domain circumstantial language (e.g. PlantUML or Mermaid) or a programming language, and render diagrams utilizing web-based or command line tooling. The benefits are well understood - writing the diagram origin as text allows for easy integration into software improvement practices and toolchains, plus the automatic layout facilities let authors to focus on content. The problem with this approach is that it's easy for diagrams to get out of sync. Enter "diagrams as code 2.0" and the open origin Structurizr DSL - a Java-based library providing a way to specify a model of our software architecture and the views that we'd like to see, yet resulting in a consistent set of diagrams that are generated for us.
Lecture took place on Wednesday, 22nd June at 10:30 in area 3
Simon is an independent consultant specialising in software architecture, and the author of “Software Architecture for Developers” (a developer-friendly guide to software architecture, method leadership and the balance with agility). He is besides the creator of the C4 model for visualising software architecture, and the founder of Structurizr. Simon is simply a regular talker at global software improvement conferences, and travels the planet to aid organisations visualise and paper their software architecture.
#IT #Development #SoftwareDevelopment
