Rating: 
Summary: Captures what I've been doing & trying to teach
Review: Database Modeling for Smarties is exactly that. This book captures the techniques that I have been using for a number of years but have not been able to capture concisely. I found the discussion of object-relational mapping very useful and would love to send copies to the database designers that I work with. The reading is easy and the only negative would be that the chapter on development team values & characteristics seems to be misplaced. However the chapter was good reading as an intermission in the middle of the book.
Rating:
Summary: Captures what I've been doing & trying to teach
Review: Database Modeling for Smarties is exactly that. This book captures the techniques that I have been using for a number of years but have not been able to capture concisely. I found the discussion of object-relational mapping very useful and would love to send copies to the database designers that I work with. The reading is easy and the only negative would be that the chapter on development team values & characteristics seems to be misplaced. However the chapter was good reading as an intermission in the middle of the book.
Rating:
Summary: UML and databases do live in the same world
Review: Excellent intermediate text, but you should know at least the basic Universal Modeling Language symbols and have some knowledge of database architectures.
I read it when I'd been programming Oracle for a few months and wanted to learn UML as well as more about db design. What a deal, the same two topics in one book!
I came away with a deeper, and useful, understanding of both the structure of databases, and some practical uses for UML.
Rating:
Summary: Outstanding synthesis of UML, OOD, & RDB design
Review: I always wondered where I was supposed to go next after I finished my object model and stood at the edge of the OO world; how I would get from there to the world of relational database design? Now I know! The world is indeed round, and OOA, OOD and UML actually lead you right through the land of RDB design. I've actually built large projects just feeling my way through this step, but now I know that this approach is valid, theoretically sound, and will even lead me to the nirvana of fifth normal form without pain!
Rating:
Summary: good introduction and high practical use
Review: I would recommend this book. I have experience with database design (ORACLE) but object oriented design was more a mystery for me. Mr. Muller showed me that there is only a little step from entity-relationship modelling to modelling with UML. UML design also solves a lot of database design problems like reaching a 3rd (or higher) normal form. Another plus of this book is his in depth tutorial to apply the technics of UML to a relational database, to a object-relational and a object oriented database. Examples are for oracle databases and POET ODL for an object oriented database.
Rating:
Summary: good introduction and high practical use
Review: I would recommend this book. I have experience with database design (ORACLE) but object oriented design was more a mystery for me. Mr. Muller showed me that there is only a little step from entity-relationship modelling to modelling with UML. UML design also solves a lot of database design problems like reaching a 3rd (or higher) normal form. Another plus of this book is his in depth tutorial to apply the technics of UML to a relational database, to a object-relational and a object oriented database. Examples are for oracle databases and POET ODL for an object oriented database.
Rating:
Summary: Excellent adaptation of the UML to database modelling
Review: Mr. Muller provides a succinct explanation of the UML and how it applies to database models and the realities of the major DBMS on the market. He doesn't mince words, each line and paragraph are thought provoking and insightful. Choose a quiet place to read and dive in!
Rating: 
Summary: lack summation for the UML symbols
Review: The book does NOT give a good summary on the explanations for the symbols used for UML, and thus creates difficulties understanding those symbols quickly. The book has a lot more to improve for readability.
Rating:
Summary: A cure for insomnia
Review: This book is turgid and poorly written. I could not manage to get more than 1/2 way through the text as the concepts are poorly explained and the use of UML is surprisingly bad. To summarise: Poor use of UML
Concepts and ideas badly explained.
Difficult to read. A colleague (an oracle DBA) did not even manage to get as far as I did before giving up!
Rating:
Summary: A cure for insomnia
Review: This book is turgid and poorly written. I could not manage to get more than 1/2 way through the text as the concepts are poorly explained and the use of UML is surprisingly bad. To summarise: Poor use of UML
Concepts and ideas badly explained.
Difficult to read. A colleague (an oracle DBA) did not even manage to get as far as I did before giving up!
| 
