For practically every profession under the sun there are tools that make the job easier. From bakers to builders, everyone has their choice of implements to ply their trade. Naturally these tools will range from entry level, toy tools to expensive gadgets with more features and sophistication. Enterprise architecture is certainly no exception.
One of our primary tools for designing architecture, of course, is a modeling tool. Modeling tools help us visualize our design into standard, in our case UML, models. There are a variety of these tools in the marketplace, ranging from basic “drawing style” tools to far more advanced suites with “model awareness”, version control, team collaboration capabilities, etc.
Diagramming software systems is still a largely undisciplined activity, despite the many advancements in notation and methodology made over the last 10-15 years.
The typical “Systems Architecture Diagram” profile of a large organization goes something like this: Read more
“Investigative Architecture” is a term we at Systems Flow coined a few years ago for a core, overarching discipline of ours. It describes – and prescribes – the sometimes tedious, but always challenging, process that a working architect employs to locate and absorb information about a problem space in order to create usable, professional visual work products that best communicate a solution. Read more
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
We have found UML to be an extremely powerful tool and frequently use it to understand problems, design solutions, and broker stakeholder agreement.
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:
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.