Goal Oriented Diagrams
A few years back we presented for the first time at the Open Group Architecture Practitioners Conference in Miami, FL. I spoke about a topic about which we are passionate: UML as an Enterprise Architecture diagramming notation. Read more
Not Convinced Yet? More Reasons to Diagram with UML
We have found UML to be an extremely powerful tool and frequently use it to understand problems, design solutions, and broker stakeholder agreement.
I previously shared the fundamental reasons why we use UML, and wanted to share some additional reasons we find it to be an enabler for creating top-quality architecture diagrams: Read more
“Zoom in” & “Zoom out” with UML
In architecture diagramming – its all about Scope.
Too often diagrams are stuffed to the brim with content in a desperate attempt to show a complete architecture. Instead, Systems Flow’s approach values clarity over completeness. It is more important to focus the lens of your diagram on on what is architecturally significant.
Using our preferred architecture notation (UML), its easy to “zoom in”, “zoom out” or – for that matter – zoom “left” or “right” on an architecture.
Here are some examples of different scoping levels using the same UML component diagram notation:
Why We Use UML
Our team has experienced great success with visual modeling based on the Unified Modeling Language. I am not going to define UML nor describe its origin in any detail, – you can review the UML section of our Leveraging UML as a Standard Notation for Enterprise Architecture presentation for that – but instead focus on what we perceive to be the foundation benefits of choosing UML as our “go to” diagramming notation.