<< 1 >>
Rating: 
Summary: Excellent OO Process Book.
Review: 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).
Rating:
Summary: Experience-based and it shows!
Review: 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
Rating:
Summary: Great book - detailed and simple
Review: 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.
Rating: 
Summary: Excellent OO Software Development Methodology
Review: Well-balanced, and easy to follow, this book is very well-written.Based on years of real-world projects, it strikes a balance between no documentation and a bureaucratic paper trail. It introduces the concept of a workbook which groups documentation under the following headings: Requirements, Project Management, Analysis, User Interface Model, Design, Implementation, Testing and Appendix, with detailed traceability information. The section dedicated to User Interface Model is a welcome change, acknowledging what so many have concluded: that UI design is a formal part of the design process, seperate from system architecture design. It's a light on exactly how to evaluate interfaces effectiveness, for this I refer you to usability guru Jacob Nielsen's book "Usability Engineering" also available at Amazon I'm sure. Notation draws from Booch and Rumbaugh. Lots of worked examples makes the first project using this book a pleasure, and following projects even easier. Thoroughly recommended.
Rating:
Summary: Well-organized, impressive scope
Review: ____________________ 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.
<< 1 >>
| 
