UML Toolkit [With Contains a Demo on a Combination of 3 Program Lang]

As professional with 14 yeras experiences, I recommend this book for everyone who have allready study the base of UML, and are looking for a guideline and a quick reference card.As Project manager, I have read and study more than 30 books about UML.For the first two projects, this book was for me very useful, because I serve it like a quick reference card for all the design tool, and as a guide line for the sequence of the phases (I followed the chapter 10, and the result was eloquent ! although today I have found a different one !)More over the case study is one of the only one I have encounter in books which is ampler than a school case study.I think the other comments are not very helpfull for who look for what is different in this book.

When considering which UML book to buy it should be obvious that some complement each other depending on the skill level (novice, experienced) and background of the reader (student, software/embedded engineer, manager). However, having read more than 10 books on UML, I suggest that if you must only buy one book make it this one. There is no other book that real-time extensions, process for UML, design patterns, discussion on UML tools and a complete case study with implementation in Java. In addition, the accompanying CD amongst other things includes a demo version of Rational Rose 4.0. My only wish is that a second/updated version of the book comes out (covering UML 1.3, providing Rose 98i and correcting some of the inevitable mistakes that one finds in detailed books). END

Having read both Instant UML, and UML toolkit, found toolkit to add the most value in teaching fundamentals of UML design. The description of the processes, components and application to real business cases did not tax my brain too much. Instant UML much more suited as a reference book. Learning the art of designing object oriented business applications requires a robust methodology to relate business events to the OO architecture. UML provides a process flow from the use-case stage right through to the deployment stage to facilitate this process. Also a great productivity tool with DDL, C++, Java code generation functions.

I have been programming in C++ for while. However, whenever I implemented any of my ideas of my research as a C++ program (some are big and some are small) and tried to put down my implementation idea in a systematic manner that follows Object Oriented paradigm, I was finding it enormously difficult! But this book gave me thorough concept of different types of diagrams as described in UML. Now I think UML is the best thing ever happened among OO community. The users of a developer's software will have least difficulty in getting to know the software from his perspective. UML would not have been famous if books like this were not published! Believe me, this book helps you if you are lost in OO programming (but I would recommend readers to have knowledge about C++ or other OO languages before they start this book).

I wanted a book that summarized UML quickly and also functioned as a cookbook for all the diagramming techniques. This book filled the bill very nicely. I looked at several others and they were lacking on examples or implementation details. Some of these other books were smaller, and some larger. But, this book hit the sweetspot in coverage and readability. I gave this book a "10" rating because it is the best of the practical books that I have found so far on the complete UML approach. It's certainly not the best book that I've read this year... but for it's purpose of covering UML it is truly great. It's about 1 inch thick, includes lots of diagrams and examples, and is easy to read. I keep it handy to help me draw my entity-relationship type diagrams using the new UML formats. For those of you who don't know what UML is, it's the "Unified Modeling Language". It consolidates the previously competing approaches to systems analysis... particularly of Booch, Rumbaugh and Jacobson. They have now collaborated and standardized how you should analyze various types of software systems.