The Object-Oriented Thought Process (3rd Edition) Paperback – Aug 25 2008
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
About the Author
Matt Weisfeld is an associate professor in business & technology at Cuyahoga Community College (Tri-C) in Cleveland, Ohio.A member of the information technology faculty, he focuses on programming, web development, and entrepreneurship. Prior to joining Tri-C,Weisfeld spent 20 years in the information technology industry gaining experience in software development, project management, small business management, corporate training, and part-time teaching. He holds an MS in computer science and an MBA in project management. Besides the first two editions of The Object-Oriented Thought Process, he has published two other computer books and articles in magazines and journals such as developer.com, Dr. Dobb’s Journal, The C/C++ Users Journal, Software Development Magazine, Java Report, and the international journal Project Management.
Excerpt. © Reprinted by permission. All rights reserved.
This Book's Scope
As the title indicates, this book is about the object-oriented (OO) thought process. Obviously, choosing the theme and title of the book are important decisions; however, these decisions were not all that simple. Numerous books deal with various levels of object orientation. Several popular books deal with topics including OO analysis, OO design, OO programming, design patterns, OO data (XML), the Unified Modeling Language (UML), OO Internet development, various OO programming languages, and many other topics related to OO development.
However, while pouring over all of these books, many people forget that all of these topics are built on a single foundation: how you think in OO ways. It is unfortunate, but software professionals often dive into these books without taking the appropriate time and effort to really understand the concepts behind the content.
I contend that learning OO concepts is not accomplished by learning a specific development method or a set of tools. Doing things in an OO manner is, simply put, a way of thinking. This book is all about the OO thought process.
Separating the methods and tools from the OO thought process is not easy. Many people are introduced to OO concepts via one of these methods or tools. For example, years ago, most C programmers were first introduced to object orientation by migrating directly to C++before they were even remotely exposed to OO concepts. Other software professionals were first introduced to object orientation by presentations that included object models using UMLagain, before they were even exposed directly to OO concepts. It is not unusual to find that programming books and courses defer OO concepts until later in the learning process.
It is important to understand the significant difference between learning OO concepts and using the methods and tools that support the paradigm. This came into focus for me before I worked on the first edition of this book when I read articles such as Craig Larman's "What the UML Isand Isn't," In this article he states,
Unfortunately, in the context of software engineering and the UML diagramming language, acquiring the skills to read and write UML notation seems to sometimes be equated with skill in object-oriented analysis and design. Of course, this is not so, and the latter is much more important than the former. Therefore, I recommend seeking education and educational materials in which intellectual skill in object-oriented analysis and design is paramount rather than UML notation or the use of a case tool.
Although learning a modeling language is an important step, it is much more important to learn OO skills first. Learning UML before OO concepts is similar to learning how to read an electrical diagram without first knowing anything about electricity.
The same problem occurs with programming languages. As stated earlier, many C programmers moved into the realm of object orientation by migrating to C++ before being directly exposed to OO concepts. This would always come out in an interview. Many times developers who claim to be C++ programmers are simply C programmers using C++ compilers. Even now, with languages such as C# .NET, VB .NET, and Java well established, a few key questions in a job interview can quickly uncover a lack of OO understanding.
Early versions of Visual Basic are not OO. C is not OO, and C++ was developed to be backward compatible with C. Because of this, it is quite possible to use a C++ compiler (writing only C syntax) while forsaking all of C++'s OO features. Even worse, a programmer can use just enough OO features to make a program incomprehensible to OO and non-OO programmers alike.
Thus, it is of vital importance that while you're on the road to OO development, you first learn the fundamental OO concepts. Resist the temptation to jump directly into a programming language (such as VB .NET, C++, C# .NET or Java) or a modeling language (such as UML), and take the time to learn the object-oriented thought process.
In my first class in Smalltalk in the late 1980s, the instructor told the class that the new OO paradigm was a totally new way of thinking (despite the fact that it has been around since the 60s). He went on to say that although all of us were most likely very good programmers, about 10%20% of us would never really grasp the OO way of doing things. If this statement is indeed true, it is most likely because some people never really take the time to make the paradigm shift and learn the underlying OO concepts.
What's New in the Third Edition
As stated often in this introduction, my vision for the first edition was primarily a conceptual book. Although I still adhere to this goal for the second and third editions, I have included several application topics that fit well with object-oriented concepts. For the third edition I expand on many of the topics of the second edition and well as include totally new chapters. These revised and updated concepts
XML is used for object communication.
Object persistence and serialization.
XML integrated into the languages object definition.
Adding properties to attributes.
XML-based Internet applications.
Expanded code examples in Java, C# .NET and VB .NET.
The chapters that cover these topics are still conceptual in nature; however, many of the chapters include Java code that shows how these concepts are implemented. In this third edition, a code appendix is included that presents the chapter's examples in C# .NET and Visual Basic .NET.
The Intended Audience
This book is a general introduction to fundamental OO concepts with code examples to reinforce the concepts. One of the most difficult juggling acts was to keep the material conceptual while still providing a solid, technical code base. The goal of this book is to allow a reader to understand the concepts and technology without having a compiler at hand. However, if you do have a compiler available, then there is code to be investigated.
The intended audience includes business managers, designers, developers, programmers, project managers, and anyone who wants to gain a general understanding of what object orientation is all about. Reading this book should provide a strong foundation for moving to other books covering more advanced OO topics.
Of these more advanced books, one of my favorites remains Object-Oriented Design in Java by Stephen Gilbert and Bill McCarty. I really like the approach of the book, and have used it as a textbook in classes I have taught on OO concepts. I cite Object-Oriented Design in Java often throughout this book, and I recommend that you graduate to it after you complete this one.
Other books that I have found very helpful include Effective C++ by Scott Meyers, Classical and Object-Oriented Software Engineering by Stephen R. Schach, Thinking in C++ by Bruce Eckel, UML Distilled by Martin Flower, and Java Design by Peter Coad and Mark Mayfield.
The conceptual nature of this book provides a unique perspective in regards to other computer technology books. While books that focus on specific technologies, such as programming languages, struggle with the pace of change, this book has the luxury of presenting established concepts that, while certainly being fine-tuned, do not experience radical changes. With this in mind, many of the books that were referenced several years ago, are still referenced because the concepts are still fundamentally the same.
This Book's Scope
It should be obvious by now that I am a firm believer in becoming comfortable with the object-oriented thought process before jumping into a programming language or modeling language. This book is filled with examples of code and UML diagrams; however, you do not need to know a specific programming language or UML to read it. After all I have said about learning the concepts first, why is there so much Java, C# .NET, and VB .NET code and so many UML diagrams? First, they are all great for illustrating OO concepts. Second, both are vital to the OO process and should be addressed at an introductory level. The key is not to focus on Java, C# .NET, and VB .NET or UML, but to use them as aids in the understanding of the underlying concepts.
The Java, C# .NET and VB .NET examples in the book illustrate concepts such as loops and functions. However, understanding the code itself is not a prerequisite for understanding the concepts; it might be helpful to have a book at hand that covers specific languages syntax if you want to get more detailed.
I cannot state too strongly that this book does not teach Java, C# .NET, and VB .NET or UML, all of which can command volumes unto themselves. It is my hope that this book will whet your appetite for other OO topics, such as OO analysis, object-oriented design, and OO programming.
This Book's Conventions
The following conventions are used in this book:
Code lines, commands, statements, and any other code-related terms appear in a monospace typeface.
Placeholders that stand for what you should actually type appear in italic monospace . Text that you should type appears in bold monospace .
Throughout the book, there are special sidebar elements, such as
Note - A Note presents interesting information related to the discussiona little more insight or a pointer to some new technique.
Tip - A Tip offers advice or shows you an easier way of doing something.
Caution - A Caution alerts you to a possible problem and gives you advice on how to avoid it.
Source Code Used in This Book
You can download all the source code and examples discussed within this book from the publisher's website.
© Copyright Pearson Education. All rights reserved.
Inside This Book(Learn More)
Top Customer Reviews
Most Helpful Customer Reviews on Amazon.com (beta)
If you read the third edition, the same errors are there in this fourth. The editing problems are disappointing. Like on page 223 he says, "By now you should realize that this is an actual application...The fact that the code has a main method in it is a sure tip." OK, well, the code doesn't have a main method. It leaves you wondering, "What planet am I on, did I miss something?" Another example: At the end of chapters it seems like he inserts the wrong portions or odd choices of code. Just really inconsistent stuff like that. And then there are things like sentences from previous paragraphs that reappear again almost word for word. Not to mention things like sentences from previous paragraphs that seem to appear again almost word for word.
I was tempted to give this book three stars because some of it is repetitious or pointless and especially because of the editing issues. Despite its generous portions of brilliance, I just didn't think the author should be rewarded for putting so little care into it as a whole, especially for what you would expect by a fourth rewrite! But I'll tell you, a lot of chapters are really excellent for the right audience. Also on the positive side, the code examples are very clear and to the point. While ideas are usually introduced with java samples, he also includes C# code and gives nice context to C++. It would be nice if the coding in the book was more practical, but it's usually the "model the world" kind of stuff which doesn't help you learn how object-oriented thinking applies to real coding.
I should note that practically every chapter references "Object Oriented Design in Java" by Gilbert and McCarty, published in 1998. That book obviously really influenced the author's life.
The author continually references a very old book and expects you to use it as you read his book but the book is out of print and it is annoying to keep reading the author's suggestion to read that book:
"In Chapters 7 and 8 of their book Object-Oriented Design in Java, Stephen Gilbert and Bill McCarty present many examples of associations and composition in much more detail. I highly recommend referencing this material for a more in-depth look into these subjects." You can't reference that because the book is way out of print. Way. Last published in 1998. This statement makes Obj. Oriented Thought Process book feel even older.
There are also some errors:
At one point he is mentioning operator overloading and he says that .NET does not allow it. However, operator overloading is in C# and has been from the beginning -- well at least version 2.0.
The additional reason I only give 3 stars and really want to give about 2.5 is because this is supposed to be the Object Oriented ___Thought PROCESS__. The intro chapters set that up well, but then later he really doesn't deliver on a process to use for doing the object oriented design. He probably should've touched upon domain modeling more or something.
I did not give the book three stars because it was not correct for my experience level, the rating is due to the enormous amount of repetition. A lot of information is available for free on the internet, I purchase books because I like to have access to high quality consistent information. While the quality of some parts of this book are great, it is not consistently high quality. I found myself thinking "Why is this section here? Didn't I just read this?" If you are very new to object-oriented programming and you do not know what encapsulation, inheritance and polymorhpism are you would do just as well reading various internet tutorials as you would reading this book.
If you are just starting out I would not say you are wasting your money buying this book, but if a friend were to ask me if they should purchase it I would say no.
But if you wanna dive deep in OOP concepts, try another book.
By the way, it's a good starting point in OOP concepts, written in a very didactic way
Look for similar items by category
- Books > Computers & Technology > Computer Science
- Books > Computers & Technology > Microsoft > Development > .NET
- Books > Computers & Technology > Programming > Java
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Object-Oriented Design
- Books > Textbooks > Computer Science & Information Systems > Object-Oriented Software Design
- Books > Textbooks > Computer Science & Information Systems > Programming Languages