We are super excited to have you here, so excited in fact that we have lined up international speaker and creator of the C4 Architectural model, Simon Brown!
Simon will be discussing the Art of Visualising Software Architecture. If you’ve ever had trouble communicating the architecture that’s in your head (or understanding what’s in someone else’s), then you are sure to get a lot out of it.
But before Simon hits the stage, why not get to know each other? The event will kick off with extended networking with topic tables, so you can strike up a conversation with someone new about a topic you are interested in.
18:00 – Welcome, food, drinks and topic tables
19:00 – Simon Brown: The Art of Visualising Software Architecture
19:50 – Q&A
20:10 onwards – More drinks, snacks and networking
Ask somebody in the building industry to visually communicate the architecture of a building and you’ll be presented with site plans, floor plans, elevation views, cross-section views and detail drawings. In contrast, ask a software developer to communicate the software architecture of a software system using diagrams and you’ll likely get a confused mess of boxes and lines. I’ve asked thousands of software developers to do just this over the past decade and continue to do so today. The results from these software architecture sketching workshops still surprise me, anecdotally suggesting that effective visual communication of software architecture is a skill that’s sorely lacking in the software development industry.
Of course, as an industry, we do have the Unified Modeling Language (UML), but asking whether this provides an effective way to communicate software architecture is often irrelevant because many teams have already thrown out UML in favour of much simpler “boxes and lines” diagrams. Abandoning UML is one thing but, perhaps in the race for agility, many software development teams have lost the ability to communicate visually. This talk explores the visual communication of software architecture based upon my experience of working with software development teams across the globe. We’ll look at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, the value of creating a model plus how to use tooling and static analysis techniques to automate diagram generation.
Simon is an independent consultant specialising in software architecture and the author of Software Architecture for Developers; a developer-friendly guide to software architecture, technical leadership and the balance with agility. He is also the creator of the C4 software architecture model (https://c4model.com/) and the founder of Structurizr (https://structurizr.com/), a collection of tooling to help software teams visualise, document and explore their software architecture.