|
Amazon.co.uk Trade-In Store
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Books Trade-In Store for more details. Special Offer until June 30, 2013: Receive an additional £5 promotional Gift Certificate, when you trade-in at least £10 worth of books. Learn more. |
Product details
Would you like to update product info or give feedback on images?
|
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
The main problem is the over-emphasis on use cases driving the whole project. Use cases are fine for functional requirements, but only in the middle of the project did we realise that these represent a mere part of a whole project. For example, design patterns (e.g. Observer, Factory, State etc etc) and other architectural constructs tend to slip out of a Use-Case driven approach, leading to a very poor quality OO design.
The process outlined here looked good in the book, but it's value depends on the nature of the project. Having used it, I'm very skeptical of having Use Cases drive a software project.
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_.
|
This product's forum
Search Customer Discussions
|
Related forums
|
|
|
|