People often joke about how software architecture is just about boxes and lines; and while this is true to some extent, being able to draw pictures doesn't make you a software architect. Pictures *are* invaluable during the entirety of the software development process but actually producing decent pictures is a skill in its own right, so much so that we spend some time talking about and practicing it on our 2-day Software Architecture for Developers training course.
I'll be presenting a session called "Effective Sketches" at Skills Matter (Thursday 1st September) and the Software Architect 2011 conference (Wednesday 19th October) where I'll be exploring this topic in more detail. Here's the abstract...
The code might be the architecture but at some point in time you’re going to have to explain how it works, and that’s when the whiteboard pens make their appearance. Where do you start though? How much detail should you include? Technology decisions included or omitted? UML or block diagrams? Join us as we look at some typical diagramming bloopers and show you how to produce effective sketches.
If you want to get a feel for what I'll be talking about in these sessions; take a look at Deliberate practice, effective sketches, Start with the big picture and C4: context, containers, components and classes.
Simon is an independent consultant specializing 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’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.