Introduced in 1997, the Unified Modeling Language (UML) has rapidly been accepted throughout the software industry as the standard graphical language for specifying, constructing, visualizing, and documenting software-intensive systems. The UML provides anyone involved in the production, deployment, and maintenance of software with a standard notation for expressing a system's blueprint. The UML covers conceptual things, such as business processes and system functions, as well as concrete things, such as programming-language classes, database schemas, and reusable software components. In The Unified Modeling Language User Guide, the original developers of the UML-Grady Booch, James Rumbaugh, and Ivar Jacobson-provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning. Starting with a conceptual model of the UML, the book progressively applies the UML to a series of increasingly complex modeling problems across a variety of application domains. This example-driven approach helps readers quickly understand and apply the UML. For more advanced developers, the book includes a learning track focused on applying the UML to advanced modeling problems.
With The Unified Modeling Language User Guide, readers will:
understand what the UML is, what it is not, and why it is relevant to the development of software-intensive systems
master the vocabulary, rules, and idioms of the UML in order to "speak" the language effectively
learn how to apply the UML to a number of common modeling problems
see illustrations of the UML's use interspersed with use cases for specific UML features
gain insight into the UML from the original creators of the UML
Grady Booch is an American software engineer, best known for developing the Unified Modeling Language (UML) with Ivar Jacobson and James Rumbaugh. He is recognized internationally for his innovative work in software architecture, software engineering, and collaborative development environments.
UML is just about the driest of all dry topics, even for technical people. It shouldn't really be a surprise that this isn't a real page-turner.
I picked up this book because it was recommended in another book on design patterns and I wanted a deeper understanding of UML. It is a good reference and I'd recommend as such it to anyone who needs to add more formality to a software design process. I particularly like the fact that the author focuses on providing the appropriate level of detail (not too much, not too little) where other UML books seem to treat UML as the Universal Answer To All Design Problems.
The book is very structured and almost all the chapters have the same sub-sections, which would make it more useful as a reference tool. On the other hand there are a couple of chapters (on state machines and state diagrams) which are almost the same and I have to wonder why there are two different chapters.
Overall, I'd say this is a useful reference, but I'll not recommend anyone read it straight through.
1er volet de la trilogie UML. Cet ouvrage de bonne facture (couverture rigide, impression bicolore !) présente les différents concepts d'UML, ainsi que les diagrammes associés. Les éléments les plus importants de la notations (tels que les classes) sont partagés en 2 chapitres : Notions de bases et concepts avancés. Lecture agréable, aussi bien par le style que grâce au partitionnement en de nombreux chapitres de taille raisonnable. Ce n'est pas un manuel d'initiation destiné aux néophytes en modélisation. Pour ceux ci, le livre pourra paraître trop complexe du fait de son exhaustivité, dans ce cas un ouvrage tel que celui de Pierre-Alain Muller sera plus approprié.