Object-Oriented Modeling and Design

Rating:
Summary: One of the OO bibles
Review: A landmark in OO literature: always was and always will be. Taking things from step zero to discussing very advanced issues. The notation used is the one where UML has borrowed most of its elements (especially the class diagrams). The process it describes has become the typical process for OO development (especially 2nd generation OMT as described through a series of articles in JOOP by Rumbaugh). In all, a book that leaves nothing uncovered from notation to process and more importantly in depth discussions on OO concepts and techniques that will always be true. Finally, this is one of the few books that discuss how to implement an OO design into a non-OO language such as C, Pascal, Fortran etc. END

Rating:
Summary: OMT is still the best
Review: I still maintain this book is the best. I believe Rumbaugh sold out when he joined Booch. Now its a commerical venture. This book was an educational delight.

Rating:
Summary: OMT is still the best
Review: I still maintain this book is the best. I believe Rumbaugh sold out when he joined Booch. Now its a commerical venture. This book was an educational delight.

Rating:
Summary: Get started!
Review: Lets face it, this is the best book to get started on Object Oriented Programming. An object is still an object, whether you show it in a cloud or in a box. Plus this book has some valuable tips on programming the right way, and puts reusability in perspective. Its written in extremely readable fashion, quite unlike some of the UML documents out there. The only thing that bothers me is the price tag, which seems to be a bit high.

Rating:
Summary: Really nice book, got to find something like after 10 years
Review: The chapters on object -> RDBMS mapping and implementation using non-OO languages are worth the whole book!

It's outdated because it uses the OMT, I would really thanks Rambaugh if he could write a new edition!

Rating:
Summary: Really nice book, got to find something like after 10 years
Review: The chapters on object -> RDBMS mapping and implementation using non-OO languages are worth the whole book!

It's outdated because it uses the OMT, I would really thanks Rambaugh if he could write a new edition!

Rating:
Summary: Lots of fluff, very little content
Review: This book gives what seems like a reasonably good description of each of the three OMT models: object, functional and dynamic. Unfortunately, when attempting to use the ideas presented, one becomes immediately aware that no explanation of how to use all three models together is given.

Looking at the examples, one finds that the examples in each model's section are totally unrelated to the examples in the other two model's sections. Essentially, the authors have fabricated example systems for each section that are easy to describe using that particular model, but have failed to show the other two models for those systems. This book would have been far better if the same set of examples were carried through the three types of models, showing how they interrelate.

The primary problem with the book, however, seems to be that it's about OMT. OMT has many serious flaws. OMT's object model notation is reasonable. The functional model notation is satisfactory. The dynamic model is incomplete. And the three models are not related to eachother in any clear way by this book. Without fixing the flaws inherent in OMT, any book on OMT is going to be mostly useless.

Rating:
Summary: An excellent book for OOAD
Review: This book is an excellent book for beginners as well as advanced guys in the charismatic field of OMT and OOAD. The book gives an excellent description of Object Modelling, Functional modelling and Dynamic modelling. The examples are good and understandable but they can be simplified. Over all an interesting and good book.