Simple sketches for diagramming your software architecture

Agility is about moving fast and this requires good communication. A consistent, shared vision is essential in order for teams to push in the same direction, but it's surprising that many teams struggle to effectively communicate the architecture of the software they are building. As an industry we do have the Unified Modeling Language (UML), yet many people favour informal boxes and lines sketches instead. The problem is that such diagrams rarely make any sense, usually need a narrative to accompany them and ultimately slow the team down. Although we can argue whether UML offers an effective way to communicate software architecture, that's often irrelevant because many teams have already thrown out UML or simply don't know it. Abandoning UML is one thing but, in the race for agility, many software development teams have lost the ability to communicate visually too.

YOU MAY ALSO LIKE:

• C4 models as code (SkillsCast recorded in December 2022)
• Do We Still Need Architects? (SkillsCast recorded in November 2022)
• Software Architecture in a DevOps World (SkillsCast recorded in February 2022)