If you’re reading this, we can safely assume that not only have you already opened the book, you’re probably also a developer of software, systems, or databases, and you want to read or write UML 2 diagrams. Perhaps you’re a manager or business analyst in the same boat.
We won’t assume that you know any particular computer language, although knowing one will certainly help.
For the most part, we assume that you fall into one of two major categories: Either you’re a modeler (with a yen to communicate requirements or how you think the world works), or you’re a developer (looking to explore alternative designs or communicate your results). Either way, this book is for you.
We assume that you’re capable of using a tool to draw UML diagrams — we don’t care which one. If the only tool that you have your hands on is in your hands (as opposed to on-screen), you won’t be at a disadvantage when you use this book (although your diagrams won’t be quite as tidy if you’re drawing with a stick on wet sand). You may even be better off doing some diagrams by hand; electronic UML tools are often expensive and may not yet be up to date with all the neat UML 2 features that we cover. If you’re itching for a high-tech UML tool, take a look at Chapter 23 where we list of some of the more useful examples (in all price categories).