Customer Reviews

UML Pocket Reference

5 star:		(4)
4 star:		(2)
3 star:		(0)
2 star:		(1)
1 star:		(0)

 

 

I agree with the reviews that praised this book a couple of years ago. It is just as good as other O'Reilly quick reference books, but the standard has changed to UML 2.0 and you might want to consider that strongly when you make a purchase. UML 2.0 is not covered in this book.

Design plays a quintessential role in the software development life cycle. Pilone provides a well-structured succinct account of proper conventions for UML. The text is well organized and will allow a programmer to quickly find the proper format for their UML diagrams. Following the text will give anyone's design documentation a professional edge.

Moreover, Pilone gives attention to use case documentation. He describes a higher level of design then UML. Thus he lays out a more efficient way to conduct the software development life cycle: first, creating use case documentation, secondly construct class diagrams, thirdly designing sequence and behavior diagrams. Attention to the design process produces more efficient-less buggy code.

The book is designed to be a `dictionary' of UML terms and techniques that can easily be used in a classroom environment in addition to a standard object oriented language textbook. Though extremely informative, the text is only a pocket reference and should not stand by itself. The book is essential to any student or seasoned programmer to be used as a `pocket reference' guide.

Like O'Reilly's other Pocket Reference books, this book is designed as a quick reference with an ultimate goal of making the reader as productive as possible. It is really useful for people with knowledge of UML but need a quick refresher.

I found it to not only be a very quick read, but a good reference on UML syntax and usage. The book is divided up into sections, which cover the various UML diagrams you might encounter. The brief discussion in each section will quickly bring the reader up to speed.

Again, if you are already familiar with UML and need a sort of quick reference book, then I would recommend this as an addition to your library. If you are looking for a more thorough UML explanation or are not as comfortable with it as you would like to be, I would recommend a more involved book, like O'Reilly's Learning UML.

This is a great little guide to keep on hand as you gain experience with UML. The author targets the experienced UML person who knows there is a way to do something but is unsure of the syntax. By no means would you buy this book to learn UML from the ground up. But once you work your way through a book such as Learning XML by Sinan Si Alhir, you would benefit from a short guide to point you in the right direction when stumped.

Conclusion
If you're going to be UML on a regular basis and you've worked through the basics, I recommend this book as a very good index to everything in the UML diagram world.

Wow. I'd been looking for this book. A long overdue addition
to the C and C++ pocket reference. This book is just what it said it would be - a UML reference book. Easily fits in the
backpack (or lost on the desk). I look forward to other books written by Mr. Pilone. This one is easy to read, informative
and well worth what I paid for it. It would have been a five star book, but it's a pocket reference!

Great UML reference.

If you are in software development, and get a stack of UML diagrams handed to you and have any doubt about how to interpret their content, this book is for you.

If you are a software developer or designer and need to diagram UML and get it right the first time, this book is for you.

It is quite a bit more comprehensive than the other UML books by O'Reilly and others, and it WILL fit in your pocket with room to spare.

As a system architect I find this reference guide pretty useful in case I need to quickly refresh my memory on how some UML notation goes again. Small pocket size is handy and travels easily in the laptop case, for example. Have this essential guide always at your hand, especially when learning UML or using the notation for the first time in real software engineering cases.