Title: Too Many Errors to be Useful
Product review: I bought this book for its value as a "quick read" of UML 2.0, and as prep for the OMG UML Certification.I'm just on Chapter 1, and have found so many glaring errors so far that I suspect everything in the book has to be carefully read and re-read to identify the errors.Examples: page 12 - the definitions for "precondition: and "postcondition" are EXACTLY the same. Page 17 - the graphic does not support the text that the notation for aggregation and composition are different. I suspect that the book was rushed to publication without adequate proofreading, which is too bad because, other than the errors, it's very consice and read-able.
Would you say this review depicts the product in a flattering or unflattering light?
