Identifying Who Needs UML | UML 2 For Dummies

Broadly speaking, UML users fall into three broad categories:

Modelers: Modelers try to describe the world as they see it—either the world as is, whether it’s a system, a domain, an application, or a world they imagine to come. If you want to document a particular aspect of some system, then you’re acting as a modeler—and UML is for you.
Designers: Designers try to explore possible solutions, to compare, to trade off different aspects, or to communicate approaches to garner (constructive) criticism. If you want to investigate a possible tactic or solution, then you’re acting as a designer—and UML is for you.
Implementers: Implementers construct solutions using UML as part of (or as the entire) implementation approach. Many UML tools can now generate definitions for classes or databases, as well as application code, user interfaces, or middleware calls. If you’re attempting to get your tool to understand your definitions, then you’re an Implementer—and (you guessed it) UML is for you.

To understand how you can benefit from UML, it will help to know how and why it was developed. It’s based on successful and working techniques proposed by groups of Software Technology Vendors before the Object Management Group, and voted upon by the members.