 |
GetTextbooks.co.uk
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Object Oriented Software Engineering: A Use Case Driven Approach (ACM Press) by Ivar Jacobson ISBN-10: 9780201544350 ISBN-10: 0-201-54435-0 ISBN-13: 9780201544350 ISBN-13: 978-0-201-54435-0 Hardcover 1992-07-10 Addison-Wesley Professional Find Lowest Price |
Editorials | ||
Amazon.com A text on industrial system development using object- oriented techniques, rather than a book on object-oriented programming. Will be useful to systems developers and those seeking a deeper understanding of object orientation as it relates to the development process. | ||
Reviews | ||
Standard text for object oriented analysis 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. | ||
Really got my gears spinning 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. | ||
Jacobson is clearly a visionary 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. | ||
Important work but somewhat confusing and now outdated ... 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. | ||
Provides some Good Contributions to OO Design 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_. | ||