Buy Used
+ £2.80 UK delivery
Used: Very Good | Details
Condition: Used: Very Good
Comment: Expedited shipping available on this book. The book has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Object Oriented Software Engineering: A Use Case Driven Approach: A Use CASE Approach (ACM Press) Paperback – 30 Jun 1992

3.8 out of 5 stars 9 customer reviews

See all formats and editions Hide other formats and editions
Amazon Price
New from Used from
"Please retry"
"Please retry"
£17.99 £1.68
click to open popover

Special Offers and Product Promotions

Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.

  • Apple
  • Android
  • Windows Phone

To get the free app, enter your mobile phone number.

Product details

Product Description


"In this book Jacobson establishes a new direction for the future of software engineering practice. It is a thorough presentation of ideas and techniques that are both solidly proven and simultaneously at the leading edge of software engineering methodology." Larry L. Constantine, RODP, Organization & System Consultant

"Object-Oriented Software Engineering belongs in the book collection of every serious student of object methodologies." Larry O'Brien, Editor, COMPUTER LANGUAGE

"Perhaps the most profound and deeply revealing volume on object technology to date ... It is simply a must-own book." Steve Bilow, Journal of Object-Oriented Programming

"Jacobson is in my opinion one of the foremost methodologists in the field of Software Engineering ... I strongly recommend ... this book ... not only for software managers and designers but for anyone who wishes to understand how the next generation of Software Systems should be built." Dave Thomas, Object Technology International

From the Publisher

Object-oriented techniques for the whole software life cycle
"This is a book on industrial system development using object-oriented techniques. It is not a book on object-oriented programming. We are convinced that the big benefits of object orientation can be gained only by the consistent use of object orientation throughout all steps in the development process. Therefore the emphasis is placed on the other parts of development such as analysis, design and testing.

You will benefit from this book if you are a system developer seeking ways to improve in your profession. If you are a student with no pervious experience in development methods, you will learn a robust framework which you can fill with details as you take part in future development projects. Since the focus on the text is on development, the book will be convenient to use in combination with other texts on object-oriented programming. Many examples illustrate the practical application of analysis and design techniques.

From this book you will get a thorough understanding of how to use object orientation as well as the basic technique throughout the development process. You will learn the benefits of seamless integration between the different development steps and how the basic object-oriented characteristics of class, inheritance and encapsulation are used in analysis, construction and testing. With this knowledge you are in a much better position to evaluate and select the way to develop your next data processing system.

Even though object orientation is the main theme of this book, it is not a panacea for successful system development. The change from craftsmanship to individualization does not come with the change to a new technique. The change must come on a more fundamental level which also includes the organization of the complete development process. Objectory is one example of how this can be done.

This book does not present Objectory. What we present is the fundamental ideas of Objectory and a simplified version of it. In this book we call this simplified method OOSE to distinguish it from Objectory. To use the process in production you will need the complete and detailed process description which, excluding large examples, amounts to more than 1200 pages. Introducing the process into an organization needs careful planning and dedication. It also requires that the process be adapted to the unique needs of the organization. Such process adaptations must of course be carefully specified, which can be done in a development case description, as will later be explained.

It is our hope that we have reached our goal with this book, namely to present a coherent picture of how to use object-orientation system development in a way which will make it accessible both to practitioners in the field and to students with no previous knowledge of system development. This has been done within a framework where system development is treated as an industrial activity and consequently must obey the same requirements as industry in general. The intention is to encourage more widespread use of object-oriented techniques and to inspire more work on improving the ideas expounded here. We are convinced that using these techniques will lead to better systems and a more industrial approach to system development.

Part I: Introduction. The book is divided into three parts. The first part covers the background, and contains the following chapters:

System development as an industrial process The system life cycle What is object-orientation? Object-oriented system development Object-oriented programming This part gives an introduction to system development and summarizes the requirements of an industrial process. It also discusses the system life cycle. The idea of object orientation is introduced, and how it can be used in system development and during programming is surveyed.

Part II: Concepts. The second part is the core of the book. It contains the following chapters:

Architecture Analysis

Construction Real-time specialization Database specialization Components Testing The first chapter in this part introduces the fundamental concepts of OOSE and explains the reason why these concepts are chosen. The following chapter discuss the method of analysis and construction. The next two chapters discusses how the method may be adapted to real-time systems and database management systems. The components chapter discusses what components are and how they they can be used in the development process. Testing activities are discussed in a chapter of their own.

Part III: Applications. The third and last part covers applications of OOSE and how the introduction of the new development process may be organized and managed. This part ends with an overview of other object-oriented methods. This part comprises:

Case study: warehouse management system Case study: Telecom Managing object-oriented software engineering Other object-oriented methods Appendix. Finally we have an appendix which comments on our development of Objectory."

-from the preface

Customer Reviews

3.8 out of 5 stars
Share your thoughts with other customers

Top Customer Reviews

Format: Paperback
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.
Comment 2 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback Verified Purchase
I am reviewing many years after reading this book, so I won't say much.
But I remember it really helped me out when I had to develop a very complicate state machine representing a satellite.
This book gave me the idea to implement the state machine using the polymorphism, and all became not only much easier, but also architecturally very clear, with well separated software layers.
Thank you Jacobson.
Comment One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
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.
Comment One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
One of the best computer related books I have ever read. Comprehensive, well structured and well written.
Comment One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
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_.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse