loading...
Cover image for Announcing the Structurizr diagram review tool

Announcing the Structurizr diagram review tool

simonbrown profile image Simon Brown Updated on ・2 min read

Prior to the COVID-19 pandemic, I'd been running my software architecture diagramming workshops at organisations all around the world. With many offices closed, that's all been suspended temporarily, although a number of organisations have adopted my online workshop instead. Part of the workshop involves reviewing some diagrams, which is easy to do in-person (sticky notes work great on a whiteboard or flip chart paper), but reviewing diagrams online/remotely isn't as straightforward. Collaboration tools like Miro and Mural are an option (I've used them myself), but I wanted something a little more dedicated to my use case. So I built some tooling. 👨‍💻

Structurizr's new diagram review feature allows you to package up one or more diagrams for review by other people. It's designed to offer a quick and lightweight immutable review process, so there's no support for "resolving" comments, or having threaded discussions, for example. It's ideal for a quick general diagram review, or when you want to run a remote risk-storming session. The review feature can be used with diagrams from an existing Structurizr workspace, or any other PNG/JPG files (as illustrated below).

Alt Text

The minimal UI lets you add comments to a diagram, and submit them once you're done. Reviews with a single diagram are free to create after signing up for a Structurizr account, although reviewers don't need an account to leave comments. Structurizr users with premium accounts can create reviews that contain multiple diagrams. See Structurizr - Help - Diagram review for more details, and there's also a demo review.

I hope you find it useful!

Posted on by:

simonbrown profile

Simon Brown

@simonbrown

Author "Software Architecture for Developers" | Creator of the "C4 model for visualising software architecture" | Founder at Structurizr | Software architecture training at architectis.je

Discussion

markdown guide