Most helpful customer reviews
1 of 1 people found the following review helpful
1.0 out of 5 stars
Plain bad, Sep 16 2009
Don't be fooled, I'm not a newbie angry for not understanding something. I actually teach UML as part of classes I give as a consultant. I was looking for a reference book to suggest to groups of software engineers and I would never suggest a book I have not read. Turns out I've found many two pages tutorials on the web that were much more complete and interesting than this book. UML is about making large concepts intelligible and this book is sticking to relations a two year old can figure out in a snap. Worst, UML is a graphical language and this book sports plenty of textual descriptions of what a graphic element should look like. Imagine how inefficient (and boring) it is two spend two paragraphs explaining a line with a diamond and bits of text instead of just drawing the thing. The fact that no example in the book goes past a two cent situation means that even after reading the whole thing form cover to cover, students or inexperienced programmer have not a single idea in their mind of what a UML diagram can look like, let aside a positive feeling of it's power and uses. There's not even a single table listing the basic features of the language side by side and many a time, you read about a specific type of diagram and end up getting pretty much half of the information while the rest is scattered around in some parts of a discussion about something else absolutely not related. As many other books on the subject, this book claims to be about system modeling while it actually covers pretty much nothing else than class diagrams. If you're looking into making use of UML to describe system architecture and service definition (let alone real-time or embedded application) you've been fooled again, but this time, a little more than usual. It's so bad that many a time in the reading I wanted to just stop it there, which I didn't do in hope that things would get better. Now that I've gone through the whole thing, I feel really stupid for not having thrown the thing overboard.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
1 of 1 people found the following review helpful
2.0 out of 5 stars
The Reference Manual is a better buy, Mar 17 2004
This review is from: Unified Modeling Language User Guide, The (Hardcover)
I have read both the User's Guide and the Reference Manual, which are generally intended to be bought as a pair. The Reference Manual is better organized, and is an invaluable resource for anyone who does a lot of UML modeling. This book, however, is just a dump of UML information, fairly ecletic but not always in sufficient depth. It is good information, but the poor organization makes it useless after the initial reading. If you are looking to learn UML, it IS possible to get a good feel for it from this book. However, something like "UML for Dummies" will also give you a good introduction, at a better price. If you will be modeling a lot, and want a deep understanding of UML, then it would be wiser to buy the Reference Manual instead.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
1.0 out of 5 stars
More powerful than a barbiturate, Nov 17 2003
This review is from: Unified Modeling Language User Guide, The (Hardcover)
The guys who essentially invented UML wrote this book-the infamous 'Three Amigos'. You would think that given that their book is about design they would have taken the time to make it visually appealing. Needless to say I should have judged this book by its cover. It sucked. To start with each chapter begins with an analogy on how building a house is like software design. When I started the book the analogy seemed appropriate, by chapter 31 I wanted to break someone's nose. Outside of the horrible cover design and redundant analogies the book is poorly organized. The book constantly refers to terms that it doesn't expound upon or for that matter define anywhere. For example, the authors refer over and over again to CRC Cards, but they're not defined anywhere in the book. What's worse, however, are the partially defined lists. For example the authors go to the trouble of informing you that there are four kinds of events in UML, but only bother to discuss three of them. Maddening! The chapters don't really follow a logical flow. The Three Amigos constantly skip backwards and forward throughout the book. In the side margins, almost as an afterthought they have included chapter references in blue type. If you follow the chapter references you're reading all over the place. Moreover, and perhaps most annoying of all is when they keep referring to concepts that they cover later in the book. I was paranoid that I day dreamed my way over the whole concept of the state machine until I discovered it nested away in chapter 21. Last but not least, the book is poorly written. Seriously, if you have to read this piece of crap you better brew a big pot of coffee. Technical literature can be a bit dry at times, but this is an exceptionally horrid piece of work. Death to the Three Amigos and a pox on Rational for hiring them! Don't buy this book.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
|