<< 1 >>
Rating: 
Summary: Important work but somewhat confusing and now outdated ...
Review: Although this book is seminal in as much as it presents use-cases, it is definitely not the clearest introduction to OO. It does however present Jacobson's OOSE methodology (which is a simplified version of the Objectory methodology). The book is due for an update - and I believe one has been in the pipeline for a while. However, with the release of UML and the new Rational methodology, it is perhaps best left as is.
Rating: 
Summary: Attempts to Describe Content Free OOSE
Review: An OO methodology book without an OO method. OOSE hides and/or conceals the most important aspects of use cases, for resale in the author's product. Frustratingly useless.
Rating:
Summary: Couldn't get very far
Review: I read 50 pages without ever seeing the word 'object' and gave up. I don't know why people think this is such a great book, it is abstract and impenatrable. The Booch book (OOA&D) is much clearer and easy to read
Rating: 
Summary: A classic text on OO Analysis and Design
Review: Jacobson's use case approach has had a profound impact on the field of object oriented analysis and design. Use cases represent a powerful means of capturing system requirements and driving the development of object-oriented software. Jacobson avoids software "dogma" and presents a comprehensive, powerful and practical process for OO software development. If you do any work in OO development, you need this book.
Rating:
Summary: Standard text for object oriented analysis
Review: Lucidly describes the fundamental principals of object-oriented analysis, design, and programming. Excellent coverage of object-oriented analysis including the introduction of use cases. Uses an awkward state transition graph that resembles a flow chart in the design methodology. Emphasizes traceability from analysis model to design model to source code. Describes how object-oriented technology impacts specialized topics such as real-time systems, relational databases, testing strategies, component reuse, and product management. The "warehouse management system" case study is more stimulating than the longer "telecom" case study. Compares the OOSE method with other standard object-oriented methods.
Rating:
Summary: I can only agree with all the others, a MUST have book!
Review: One of the best computer related books I have ever read. Comprehensive, well structured and well written.
Rating:
Summary: One of the best Computer Science Book I read.
Review: The book is very clear and, at the same time, very deep and sharp
Rating:
Summary: Provides some Good Contributions to OO Design
Review: This book is considered a classic by many. The key contribution of the book is the introduction of Use Cases for requirements capture. Jacobson also provides some good hints on how to develop an OO design after starting from Use Cases.There are two big weaknesses with this book. Firstly, the book is vague on the amount of detail that should go into a Use Case. This has led to a great amount of confusion and widely different usages in industry. Secondly, the book provides only weak design guidelines beyond those provided for extracting objects from the Use Cases. Another criticism of the book is that it is written in a very academic tone, which may be hard to understand for some readers. Another book that covers much of the same ground but in a clearer fashion is Ian Graham's _Migrating to Object Technology_.
Rating:
Summary: Jacobson is clearly a visionary
Review: This book was written in 92 yet continues to be a visionary text. The chapter on Components maps closely to the principles used today in distilling software patterns. The section on testing is key to understanding how to design objects properly (so they can be maintained over time). The appreciation of objects expressed in terms of data (entity) and tasks (operations) is crucial to good analysis and design. What Jacobson conveys is the essence of good software engineering. If you want to understand this book, read it several times as you gain knowledge and experience in the OO arena. Each time you will discover new pearls of wisdom.
Rating:
Summary: Really got my gears spinning
Review: This book, unlike others in the field, shows an indepth understanding of the software development process. Jacobson has definitely spent time designing real world apps. His view of OO as a mere component in the development of quality software is visionary and pre-dates the overemphasis and primacy given to it by latter day authors. If you understand the large picture he presents, you will go far in the pragmatic field of designing and deploying real systems.
<< 1 >>
| 
