Unified Modeling Language
Complex software designs and business processes can be articulated through visual models, such as the Unified Modeling Language. This series of posts describes the tools and methods I use to create my UML designs that are "good enough" to understand.
The UML standard is complicated, with several layers of specifications. There are many diagrams, connectors, elements, etc. Is it any wonder that the standards-setting body for this language is called OMG?
I am able to satisfy all of my modeling needs using just Use Case, Activity, State and Sequence diagrams. There are diminishing returns after this basic set of four; the remaining UML diagrams are too specialized. I can achieve the same results using Visio to draw a network or Wiki to describe deployment.
My UML diagrams are "good enough" for a developer to understand. They do not follow the complete specification and have modeling syntax mistakes. These syntax errors are OK, as no one using my UML designs has ever noticed them.