Updates
Latest Tweet
What's New?
Check out for latest innovation, a computer based training video collection
Like this Page
UML for Database Design Review by Philip R. Heath
Not Enough Of What It Is Supposed To Be
Less than half of this book really deals with what the title suggests. Chapters 6, 7, and 8 are the only things of value to someone already familiar with the UML. The previous chapters try to give the database designer an overview of using UML for all project aspects; however, this is done much more cleanly in other books like UML Distilled or Visual Modeling With Rational Rose 20XX and UML.
The authors also present things with assumptions made about how the organization is structured: separate application and database design teams. This slant requires that the reader translate what is written to their particular situation. A more useful book would have stated principles that can be applied to various organization structures with appropriate practices.
Also, there is no advice given as to how to actually implement any of these UML extensions for database design in the available tools. This makes the ideas presented hard to put in practice and makes the book much more theoretical than practical.
Bottom line, there is not enough unique information here for the book to stand on its own. It would be better to roll this information into texts like the ones I mentioned at the beginning, and also give examples using currently available tools.