This highly respected guide to object-oriented programming has been updated to reflect the most recent advances in this still-evolving methodology. New material includes updated terminology; finding lasses and objects; defining attributes; defining services; object-oriented analysis and CASE; moving to object-oriented design. 7 x 9 1/4.
Object Oriented Analysis is an interesting book that is worth checking out if you want an idea of the state of OO at the time of its publication (the 2nd edition was published in 1991). As an educational text on the topic matter, I think its age really hurts it, and many of the ideas of what we think of in regards to good object-oriented design are just not present here. While I enjoyed the use of SmallTalk as the language of choice for examples, most of the book uses pre-UML diagrams and theoretical ideas to explain the concepts.
What makes it an interesting read is the way the authors presented the industry at the time, and how relevant some of the issues like cargo-culting were even back then. The authors are also very pragmatic about their approach toward OOA, and they are very careful to suggest OOA as anything other than another way to draw up requirements for a project.
In the 80's and early 90's, Object Oriented Analysis and design was still an emergent discipline. It was before UML and before the Design Patterns. At this point in time, the emphasis was on the object identification up-front with a hierarchy graph. All thoses approaches combine a prescriptive approach going hand in hand with a notation. This book is a remarkable sample of the time. It gathers all the properties bellow. This is now an historical testimony and no longer a reference textbook. Take it for what it is. Ma note de lecture en Français ici
There is what design is after "design patterns" and there was the before. This is a book about "before". By this time, we use to think that design was a linear process, coming in continuity of analysis. And indeed there is a book from the sama authors about analysis. The process described here is less than convincing. The only vertue of this book is ana historical one. This is one of the many approach derived from the OO movement, before UML. It goes alonside OMT, for instance. Not so much to keep from that. Ma note de lecture en Français ici