|
UML Toolkit
 |
Author: Hans-Erik Eriksson, Magnus Penker
List Price: $49.99
Our Price: Click to see the latest and low price
ISBN: 0471191612
Publisher: John Wiley & Sons (14 October, 1997)
Edition: Paperback
Sales Rank: 9,707
Average Customer Rating: 4.05 out of 5
|
Customer ReviewsRating: 3 out of 5
Basic Introduction
This book offers a good overall understanding of the UML. However the examples are shallow, and not necessarily on point or real world enough for me. I've read other books I would recommend before this one. If you'r new to UML this would be a good start, although it may be a bit confusing to the beginner. If you have UML experience and are looking for greater depth of knowledge, look elsewhere.
Rating: 4 out of 5
From boys to men!
If you are a VB guy, considering stepping into the .NET realm, then you need to get to grips with proper OO techniques and modelling.I think this is a good book, probably more relevant to C++/Java guys but not too heavy going.
Rating: 3 out of 5
Giving the author the benefit of the doubt.
I picked up the book after reviewing the discussion on Use Cases. It's the best intro to the various diagrams I have seen. Big problem though, the symbols he uses doesn't match the latest UML specifications. Anyone that has glanced at UML knows there is a confusing amount of different ways to illustrate the relations between items on a diagram. Lines with open triangles at the end, diamonds (open and filled), and arrow heads intermixed with solid and dashed lines. Each with a differnt meaning. Well, the book gets it wrong. Specifically he keeps using the open triangle at the end of the line to signify things like instantiating templates. Go ... and download the UML spec. He also adds stereotypes that don't seem to exists ( "uses" ? ). Or rather I could find any other reference that talks about them. This would be a major problem if you decided to use a tool like Rose. Design tools like Rose attach certain meanings to different shapes. I find myself constantly rechecking and re-looking up symbols. There is a possibility that some of this stuff is undefine or optional in the UML spec, but I don't want to read an 800 page document to understand this 400 page book. So good discussion, bad applications/examples.Try "The Unified Modeling Language User Guide" instead. Not as much discussion, but better accuracy.
Similar Products
· UML 2 Toolkit
· The Unified Modeling Language User Guide
· UML: A Beginner's Guide
· Software Engineering (6th Edition)
· The Elements of UML(TM) Style
|
