How can software developers, programmers and managers meet the challenges of the 90s and begin to resolve the software crisis? This book is based on Objectory which is the first commercially available comprehensive object-oriented process for developing large-scale industrial systems. Ivar Jacobson developed Objectory as a result of 20 years of experience building real software-based products. The approach takes a global view of system development and focuses on minimizing the system's life cycle cost. Objectory is an extensible industrial process that provides a method for building large industrial systems. This revised printing has been completely updated to make it as accessible and complete as possible. New material includes the revised Testing chapter, in which new product developments are discussed.

Average Customer Review: ( 10 customer reviews )
Write an online review and share your thoughts with other customers.

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_.

11 of 11 found the following review helpful:

Really got my gears spinningSep 23, 1999

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.

8 of 8 found the following review helpful:

Jacobson is clearly a visionaryAug 03, 1999

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.

2 of 2 found the following review helpful:

A classic text on OO Analysis and DesignMay 20, 1997

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.
See all 10 customer reviews on Amazon.com