Amazon.com
Pressestimmen
Kurzbeschreibung
Synopsis
Buchrückseite
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.
Reviews"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
0201544350B04062001
Über den Autor
Dr. Ivar Jacobson,Vice President of Business Engineering, is the inventor of the OOSE method, and he is also the founder of Objectory AB in Sweden, which recently merged with Rational Software Corporation. Dr. Jacobson is the principal author of two influential and best-selling books Object-Oriented Software Engineering--A Use Case Driven Approach (Computer Language Productivity award winner in 1992) and The Object Advantage--Business Process Reengineering with Object Technology. He has also authored several widely referenced papers on object technology. One of the most famous papers is his first OOPSLA '87 paper entitled "Object-Oriented Development in an Industrial Environment," which presented the first truly object-oriented method ever published. Ivar Jacobson's use-case driven approachhas had a very strong impact on the entireOOAD industry, and he himself has become one of its "icons." Consequently, he isa frequently invited keynote speaker and panelist, debating OOAD topics withcolleagues and methodologists such as Grady Booch, Jim Rumbaugh, StevenMellor, and Rebecca Wirfs-Brock at major OO conferences around the world.
He is well known for his pioneering work and more than 20 years of experience inusing object methods for the design of large real-time systems. His earlyobject-based design technique has evolved into the international standardITU(formerly CCITT)/SDL.
Dr. Jacobson also regularly serves on the OOPSLA, ECOOP, and TOOLSprogram committees, and he is a member of the advisory board of the Journal ofObject-Oriented Programming.
In 1994, Ivar Jacobson received the first Swedish Computer Association (SCA)award (the Kjell Hultman prize) for "extraordinary achievement in promotingefficiency and productivity in the development and use of informationtechnology."
Patrik Jonsson works at Rational Software Corporation in Sweden as a Senior Consultant where he has been developing the architecture and method of the Objectory process with a current focus on reuse and user interface development.
0201544350AB04062001
Prolog. Abdruck erfolgt mit freundlicher Genehmigung der Rechteinhaber. Alle Rechte vorbehalten.
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.
So, how should you read this book? Of course, to get a complete overview, the whole book should be read, including the appendix. But if you want to read only selected chapters the reading cases below could be used.
If you are an experienced object-oriented software engineer, you should be familiar with the basics. You could read the book as suggested in Figure P.1.
If you are a newcomer to object-orientation and software engineering you could read the book as in Figure P.2
If you are an experienced software engineer you could read the book as in Figure P.3
If you are a manager you could read the book as proposed in Figure P.4. Although the book is not object-oriented, it is written in a modularized way and can be configured in several different ways. Building systems in this way is the theme of the book, and the technique and notation used above is very similar to the technique used in this book.
A short history and acknowledgments
The work presented in this book was initiated in 1967 when I proposed a set of new modeling concepts (notation with associated semantics) for the development of large telecommunication switching systems. The main concepts were signals and blocks. A real-time system is an open system communicating with its environment by signals alone. A signal models the physical stimulus/response communication which a concrete system has when interacting with the outside world. Given a signal as input, a system performs internal actions such as executing algorithms, accessing internal information, storing results and sending output signals to the environment. This view presents the system in a very abstract way - as a black box. A less abstract view on a lower level models the system as a set of interconnected blocks. Blocks are modules which can be implemented in hardware or software or any combination of both. A block communicates with its environment only through signals. Signals between two blocks are internal, whereas signals modeling physical communication, that is, signals between a block and the environment of the system, are external. Internal signals are messengers conveying data from one block to another within the same system. All entries of a block were labelled and constituted the signal interface of that block, to be specified in a separate interface document. Hence the system can now be viewed as a set...
