Features
- Cover Type: Paperback with 366 pages
- Published by: Microsoft Press March 10, 2004
- Written in: English
- ISBN 10 Number: 0735619654
- ISBN 13 Number: 978-0735619654
-
Book Dimensions:
9 x 7.4 x 1.2 inches
- Weighs: 1.6 pounds
Product Description
The foundation of all object-oriented
software design, including agile methods such as extreme programming, is object thinking. But many developers have not mastered its underlying concepts and principles—relying on methodology and process instead of fully exploiting the power of object thinking in
software design. In this essential, high-level reference, well-known object technologist David West provides a deep historical and contextual discussion of object thinking, including the behavioral approaches to object discovery and design. Readers will master the fundamental principles and learn how to apply object thinking to improve
software development at every phase of the process.
About The Author
Currently Dr. David West is a professor in the School of Business at New Mexico Highlands University, where he is developing an object-based curriculum in
software architectures, business engineering, and management information systems. He founded and served as the Director of the Object Lab, a cooperative effort with local corporations dedicated to researching and promoting object technology, at the University of St. Thomas.
Reader ReviewsI almost gave up on this book after the first 100 pages. I should have. I managed to hang on to within 25 pages of the end. That was where Mr. West presents the reader with the formula X=4q+(p*r), and solemnly announces (I'm not making this up) "4 represents a constant value," with the word 'constant' set in italics to emphasize its gravity. By the standards set elsewhere in this book, that qualifies as a technically profound statement. At least it's not just plain wrong, as were statements elsewhere in the book. For example, p.270 asserts that "Ensuring that it's possible for two objects to exchange messages is a matter of visibility: the objects have to be able to see each other." Well, no. Systems like Linda allow objects to leave messages for each other at anonymous drops. Component systems like the Bean Box count on some third party able to see both, a 'Mediator' in the Gang of Four terms that West generally disparages. Heck, anyone who's ever seen a Unix command pipeline would know how silly that claim is. He also asserts (p.253) that over-riding a superclass method causes "cognitive dissonance." For those not familiar with psycho-babble, that means it confuses him. Those are probably low points, since the rest of the book is so vague and philosophical that it neither informs nor misinforms. Mr. West goes on at length on the hermeneutics of objects and their postmodernist interpetations (p.59). He goes on about how Alexander's design patterns have been misunderstood by mere application, how their real purpose is personal transformation within the user. Mostly, he just goes on. By now, I guess my lack of fawning shows that I haven't been born again into the mysteries of "Object Thinking," whatever that is. True believers initiated into the mystery will probably say that I'm not competent toon the wonderfulness of The Way of West. Well, maybe that's a good thing. I wish Mr. West all success in his navel-gazing. Maybe if he's busy with that, he won't get in the way of people trying to get work done. //wiredweird
Search for books at
