<< 1 >>
Rating: 
Summary: worst computer book i've read in ages
Review: I buy at least 25 technical/computer books a year and I can definitely say this is the worst one I've bought in the last year. I think I'll go and buy the Addison-Wesley one.This book is vague and littered with manager-speak. Not for developers at all (there is no code, for a start off). If you have ANY understanding of objects and classes you will find the first 4 chapters completely useless. It did have a reasonably good bibliography, but it's like they're saying, haha we tricked you into buying our book, now go read the good ones...
Rating: 
Summary: I bought the Harmon/Sawyer UML for Visual Basic book
Review: I recently purchased Paul Harmon's UML for Visual Basic 6 and found that it wasn't near as awful as some of the reviews I've seen. In fact it was an easy, entertaining read and after some of the more complex "Head Banger" Software books out there, this was a pleasant surprise.
Rating: 
Summary: It's not what the title says it is!
Review: On the positive side, there are some worthwhile areas of the book, particularly describing what the different types of UML diagrams are and what they represent in the development process. It's a helpful intro to UML, but there are better ones. On the negative side, they have huge amounts of the book dedicated to things like OO vocabulary, developing apps in VB, COM and DCOM, CRC Cards, and Object Model Design Patterns, that have NOTHING to do with the title. And, several of the designs in the book can't be done in Visual Modeler or Rose. What were they using, Visio? Then make it a Visio book! Other diagrams that look like Rose diagrams had features in them that Rose doesn't have. Several valuable UML discussions (extends and includes in Use Cases, how to add class properties and methods -- only 3 pages on this) are very skimpy or just not there. In short, this book is not at all what the title says. It is a very intro OO/VB/sort of Rose/a little Visual Modeler/UML book that doesn't give enough of what it says it will in the title, and presents a smattering of other topics that really aren't needed (and from which one can learn very little anyway).
Rating:
Summary: It's not what the title says it is!
Review: On the positive side, there are some worthwhile areas of the book, particularly describing what the different types of UML diagrams are and what they represent in the development process. It's a helpful intro to UML, but there are better ones. On the negative side, they have huge amounts of the book dedicated to things like OO vocabulary, developing apps in VB, COM and DCOM, CRC Cards, and Object Model Design Patterns, that have NOTHING to do with the title. And, several of the designs in the book can't be done in Visual Modeler or Rose. What were they using, Visio? Then make it a Visio book! Other diagrams that look like Rose diagrams had features in them that Rose doesn't have. Several valuable UML discussions (extends and includes in Use Cases, how to add class properties and methods -- only 3 pages on this) are very skimpy or just not there. In short, this book is not at all what the title says. It is a very intro OO/VB/sort of Rose/a little Visual Modeler/UML book that doesn't give enough of what it says it will in the title, and presents a smattering of other topics that really aren't needed (and from which one can learn very little anyway).
Rating:
Summary: A light introduction to UML
Review: This book is a fairly light introduction to UML. It is an ok overview for those who don't really need to use it, but its not enough for someone who does.
<< 1 >>
| 
