Developing Object-Oriented Software

by IBM Corporation, Ibm Object-Oriented Technology, IBM

This IBM book describes new techniques for evolving and documenting an appropriate object-oriented development process. It adopts a workbook approach, with detailed descriptions of planning,... This description may be from another edition of this product.

• Format: Hardcover
• Language: English
• ISBN: 0137372485
• ISBN13: 9780137372485
• Release Date: November 1996
• Publisher: Prentice Hall PTR
• Length: 636 Pages
• Weight: 2.55 lbs.
• Dimensions: 1.2" x 7.3" x 9.5"

Customer Reviews

Great book - detailed and simple

This book is simple for the beginner and covers some advanced concepts for not the beginner. Overall a must read for a serious OO programmer/designer. I recommend reading this book as a first or second book on OO design. The case study is great.

Excellent OO Process Book.

I found this book to be very thorough and well-written. It strongly emphasizes a separation between analysis and design, and describes every possible work product I can think of in an OO project. One small criticism is that the coverage of Use-cases is fairly weak (Scenarios should probably be requirements work products rather than analysis).

Well-organized, impressive scope

____________________This book is extremely well organized. It includes outlined summaries of techniques and products as well as detailed text. A refreshing emphasis on detailed implementation practices and case studies.Scope includes analysis, design, Use Cases, Design patterns, and reuse.

Experience-based and it shows!

The project management process described in this book iscentered around defining and producing a set of deliverables (WorkProducts) and has the following characteristics: · Focuses on Work Products organized into a logical repository known as a Work Book. Each Work Product is concisely defined in the text as to its content, structure, purpose, value and traceability (relationship to other Work Products). The list of Work Products is adaptable according to project needs and extensible in terms of defining additional WPs. The authors define WPs in terms of Objects in the Policy Management domain and present a class-definition style view of their properties and relationships. END