Strength:

Very concise, practical description of OOA/D and UML.



Level:

Beginning to intermediate developers



Key Dev. Method:

Use case driven, Architecture centric, Evolutional



Example Used:

Enterprise/Business application ( car rental )



Languages:

C++, Java, Smalltalk

Strength:
Very concise, practical description of OOA/D and UML.

Level:
Beginning to intermediate developers

Key Dev. Method:
Use case driven, Architecture centric, Evolutional

Example Used:
Enterprise/Business application ( car rental )

Languages:
C++, Java, Smalltalk

Surely this book is not the absolute reference for the UML. Someone seeking for such a book, should check up on: "The Unified Modeling Language User Guide", "The Unified Modeling Language Reference Manual" both by the 3 amigos, and "UML Distilled, Second Ed." by Martin Fowler et al.

I gave 5 stars because, to my opinion, the author has catched the main need of someone who uses the UML for the first time; to design/develop software. Formalizations and abstractions are absolutely necessary in real applications, but really destructing during the first steps simply because anything usefull is interspersed in several chapters. On the other hand, the coverage of both the UML and the OO S/W development in this book is definitely not shallow.

"Developing Software with UML" is perhaps the best choise for beginning with UML. It is well-structured, intuitive and easy.

Surely this book is not the absolute reference for the UML. Someone seeking for such a book, should check up on: "The Unified Modeling Language User Guide", "The Unified Modeling Language Reference Manual" both by the 3 amigos, and "UML Distilled, Second Ed." by Martin Fowler et al.

I gave 5 stars because, to my opinion, the author has catched the main need of someone who uses the UML for the first time; to design/develop software. Formalizations and abstractions are absolutely necessary in real applications, but really destructing during the first steps simply because anything usefull is interspersed in several chapters. On the other hand, the coverage of both the UML and the OO S/W development in this book is definitely not shallow.

"Developing Software with UML" is perhaps the best choise for beginning with UML. It is well-structured, intuitive and easy.

Of the several books I've read on UML and more importantly object-orientation I've found this one to be concise and well thought out. Discussions on what objects do and don't do are well described. Some of these discussions I've picked up just in my own experience and it was nice to see it formally described in the text.

The book explains in a nice form the "Object-Orientation for Beginners", but I don't know if OO beginners understand everything directly. The chapter about the Project Management needs to be reworked because there is a possibility to fall into a slumber... The rest part II (Example: Analysis; Design) and part III (Fundamentals of the UML), for which I decided to buy the book, is excellent. A book, nice to have! Thanks for the book! [Romain Cloos; MSc Computer Science; Société Européenne des Satellites...

This book explains complicated details of Object-Oriented Analysis/Design and Object-Oriented Programming in ways that are comprehendible without losing meaning. The book contains a good differentiation between Aggregation and Composition. Author does a good job of using sample code and UML diagrams to explain his points. That said I felt there were things in the book that should not have been there since it is mainly geared toward novices. He sort of explains the reasons why a square should not inherit from a rectangle and then goes ahead and shows a UML diagram of a square inheriting from a rectangle. Things like this could confuse novices who are just learning these principles. A better discussion of the Liskov Substitution principle would have illustrated the point of why a square should probably not inherit from a rectangle. The book also contained some annoying typos.