Description: Of all the UML books out there, this is by far the most accessible, practical and useful. What's more, it comes in at a light 200-or-so pages.

If you're looking for a tome that dissects the minutae of UML, this book is not it - nor does it claim to be. But if you, like me, recognise the need for UML (or UML-based principles) in designing an application but have neither the time, resource nor inclination to read 800+ pages of dry text, this is perfect.

The book is aimed at developers who need to produce useful, workable UML diagrams in a reasonably short amount of time as a *means to an end* - not UML for UML's sake.

As the author correctly points out, "you don't have to be an English teacher to communicate effectively... you don't have to know every detail about the UML to use it effectively". To some, this borders on heresy and if you feel that way, this book certainly isn't for you. It's not an encyclopaedic treatment of UML and I have no doubt it glosses over certain details. However, it does one thing very well - it teaches the jobbing-programmer enough about UML (or UML-principles) to plan their project intelligently.

Of course, software development requires careful planning but some UML books - in my opinion - go too far, creating diagrams so convoluted and detailed that they defeat their original purpose - namely creating a development model that people will read, follow and find useful.

This book recognises that coders only need to know enough to do their job and it doesn't pretend otherwise. I believe it's the correct approach: programmers plan intelligently and then program; leave the overblown UML diagrams and theory to the "project managers".

Link 1

Link 2


Post a Comment

Your feedback is valuable.