The author applies standard project management techniques to object-oriented projects. In particular, the assumptions and techniques underlying UML and the Unified Process are to be found in the various chapters in the book. For example, the author advocates managing complexity by using packages, use cases, encapsulation, inheritance and aggregation. The main strengths of the book are: It attempts to integrate OOT with project management techniques using the standard UML and this integration process lasts for the duration of the full software lifecycle. The book may or may not be useful depending on what you are looking for. For example, it is (very) superficial in places and in general I would say that it lacks 'meat' in the following places: Traceability issues Useful checklists and tables Quantitative treatment (measurement) Furthermore, the chapter on lifecycle models is not convincing. The author suggests that we should NEVER use the Waterfall model while he suggests that the Controlled Iteration model. Why? I have not understood this latter model when reading the boook. I think that it is too complex. Concluding, this book serves as a baseline for further research and should be complemented by other sources, for example from Boehm, Air force and IEEE. Finally, the title is an attention-grabber and in my opinion incorrect. Project management is independent of the technology used (in this case OOT). A better name would have been "Project management of software projects that use UML". Almost all software projects are risky. The goal of every project manager is to somehow deal with the cost and schedule uncertainty while meeting your customer's needs. In Object-Oriented Project Management with UML, Murray Cantor describes an elegant, UML-based approach to managing object-oriented projects guaranteed to deliver high-quality software on time and within budget. Drawing on his experience managing major software projects at IBM and TASC, Cantor supplies you * Proven ways to reap the benefits of using UML tools to tame most project demons and deliver optimal OO systems * Tips on integrating object-based techniques with traditional methods for project planning, risk management, scheduling, time-phased budgeting, and more * Expert advice on how to handle all the important "people" issues that crop up during a development project * Real-life war stories that let you see firsthand what worked and what didn't on several major development projects * A full-length project example that walks you through every phase of a project told in terms of problems and solutions Visit the companion Web site at (http://www.wiley.com/compbooks/cantor) www.wiley.com/compbooks/cantor to * Sample project schedules, budgets, database templates for managing use cases, and a work-breakdown structure * A spreadsheet workbook for managing incremental development * A development tracking diagram Prior to joining TASC, Dr. Cantor was a development manager at IBM, where he oversaw the development of high-end graphics and multimedia systems. Almost all software projects are risky. The goal of every project manager is to somehow deal with the cost and schedule uncertainty while meeting your customer's needs. In Object-Oriented Project Management with UML, Murray Cantor describes an elegant, UML-based approach to managing object-oriented projects guaranteed to deliver high-quality software on time and within budget. Drawing on his experience managing major software projects at IBM and TASC, Cantor supplies you with: * Proven ways to reap the benefits of using UML tools to tame most project demons and deliver optimal OO systems * Tips on integrating object-based techniques with traditional methods for project planning, risk management, scheduling, time-phased budgeting, and more * Expert advice on how to handle all the important "people" issues that crop up during a development project * Real-life war stories that let you see firsthand what worked and what didn't on several major development projects * A full-length project example that walks you through every phase of a project told in terms of problems and solutions Visit the companion Web site at www.wiley.com/compbooks/cantor to find: * Sample project schedules, budgets, database templates for managing use cases, and a work-breakdown structure * A spreadsheet workbook for managing incremental development * A development tracking diagram Prior to joining TASC, Dr. Cantor was a development manager at IBM, where he oversaw the development of high-end graphics and multimedia systems