// Write in front TimeStamp: 2005-3-27
Seeing Matt Weisfeld about oo 's post on developer.com, I feel that it mentioned:
This is the fifth installment in a series of articles about fundamental object-oriented (OO) concepts. The material presented in these articles is partially excerpted from the second edition of my book, The Object-Oriented Thought Process, 2nd edition. The Object- ORIENTED THOUGHT Process Is Intended for Anyone WHO NEEDS To Undeded The Basic Object-Oriented Concepts Before Jumping Into The Code. Shuiyou Find the book found that China also translated this book, but seeing the cover and the translator, I don't dare to hope. I still look at the original version, I have a more authentic, I will exercise English, I will put some wonderful paragraphs in the form of Chinese and English comparison.
// Write in front TimeStamp: 2005-3-28
Table of contents
Copyright
Developer's Library
About the Author
Acknowledgments
WE Want to Hear from you!
Introduction
This book's scope
What's new in the second edition
INTENDED AUDIENCE
This book's scope
This book's convention
Source Code Used in this book
This is the beginning of the book, to understand the author of the author and the author writes this book.
I will give a more important original text, then give an outline and some of my ideas.
About the Author
Matt Weisfeld is an assistant professor at Cuyahoga Community College (Tri-C) in Cleveland, Ohio. Matt is a member of the information technology faculty, teaching programming languages such as C , Java, and C # .NET. Prior to joining Tri-C , Matt spent 20 years in the information technology industry gaining experience in software development, project management, business development, corporate training, and part-time teaching. Matt holds an MS in computer science and an MBA in project management. Besides the first edition of The Object-Oriented Thought Process, Matt has published two other computer books, and more than a dozen articles in magazines and journals such as Dr. Dobb's Journal, The C / C Users Journal, Software Development Magazine, Java Report, and the international journal Project Management. Matt Has Presented At Conferences Throughout The United States and Canada. About the author
It can be seen that the boss Matt Weisfeld is still very strong, with rich theoretical practical experience, and is also very experienced in education. On Dr. Dobb's Journal, THE C / C Uses Journal, Software Development Magazine, Java Report, The International Journal Project Management published more Than a dozen, and attended the US and Canada seminar.
This book's scope
As the title suggests, 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 one level or. another of object orientation. Several popular books deal with topics including OO analysis, OO design, OO programming, design patterns, OO databases, the Unified Modeling Language (UML), various OO programming languages, and many other topics related to OO programming.
However, while poring over all of these books, many people forget that each one of these topics are built on a single foundation:. How you think in OO ways It is unfortunate, but often software professionals dive into these books without taking the appropriate time And Effort to really understand the concepts in them.
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 concepts via OO one of these methods or tools Many C programmers were first introduced to object orientation by migrating directly to C -.. Before they were even remotely exposed to OO concepts. Some software professionals were first introduced to object orientation by presentations that included object models using UML-again, before they were even exposed directly to OO concepts.
It is important to understand the significant difference between learning OO concepts and using the methods and tools that support the paradigm. In his article "What the UML Is-and Is not," Craig Larman 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. Many times developers who claim to be C programmers are simply C programmers using C compilers .
This problem is even more of an issue now that object-oriented languages like Java, C # .NET, Visual Basic .NET, and so on have become so popular. There are many Visual Basic programmers who now must make the leap to Visual Basic. Net. Likewise, Many C Programmers, Who Might Not Be Conforming to Strict Oo Practices, Are Being asked To Migrate To Java Or C #, WHERE The Have No Choice But to Think In Oo Ways.
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 C , C # or Java) or a modeling language (such as UML), and take the time to learn the object-oriented thought process.
This book is a concepts book intended to introduce programmers to object-oriented technologies. One of these audiences is, of course, structured programmers making the leap to OO. Thus, I have included some material that is, in fact, a bridge between structured . and object-oriented technologies Chapter 6 is a good example of this approach - I have included techniques that will be familiar to structured programmers It is important to understand that Object-oriented and structured practices are not mutually exclusive Structured techniques are used throughout.. Oo Designs (Just Consider a for loop or if statement).
. 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 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. book range
// This paragraph is quite important, so I put all the original text, the author explains the original and motivation of him to write this book.
In summarization, it is to say that we have to learn OOA / OOD / OOP / UML / DesignPattern is based on [how to use OO method]. But unfortunately, the book did not say clearly, many people didn't understand, the fact is true. We always think that use UML drawing, use classes, inherit, and interfaces are in object-oriented.
It is said that UML is similar to a circuit diagram. You should always know some electrical knowledge before watching the circuit diagram.
Direct programming language (C / Java) or auxiliary language is not correct on the way to OO development. Before this, you must follow your heart to spend some time to think about the object.
Add some of my thoughts:
In fact, the boss said and what I thought is still consistent. I wrote C for 3 years. I believe that many people will think that C / Java will have taken the top of the Kangzhuang Avenue of the object. They are all classes, inherited, interface, which is not all advocated to objects, and sometimes in time, painting UML map, set up a set of sets, good! We are already OO. Do you still need theory? That is the stuff in the Tooth Tower, how can I have time to learn, the project is too late. I have seen some people put global functions and global variables in a class, change the global function to this class, and write a global variable to members even if it is written. UUPS, how do you do it, or follow the old university's thinking method. Let's go!
