OO's translation called "object-oriented", I think this translation is particularly prone to misunderstanding. The first feel of the object is specific, visible entity. If you think in this angle, the software design will inevitably fail. I think OO understands "determining the goal", and is more close to the philosophy. The key difference is Object corresponding to an abstract in Object, not an entity. (Of course, understanding the entity can also solve some problems. If you can solve the problem in accordance with the entity concept, the process-oriented method must be more suitable for this problem domain.) Behind the process design method corresponds to the specific implementation process. With the accumulation of the process, the discovery process can be multiplexed. Then, a higher level of abstraction is generated, and the description of the abstract "natural" of such a high layer is the "OO" method. The software starts at the main solution "calculation problem", so the process method dominates. As the PC is more powerful, the software is directly involved in solving complex problems. Software design must begin learning "people" way to solve problems. And people's solution to complex issues or unknown issues is that they are divided into them. Behind this method is the abstraction of the problem. "Division" has produced different goals for solving problems, while OO methods work with "people" to solve the problem, that is, "Nature" mentioned in some articles. The mode is the basic element in the OO method, in fact, each mode is an abstract object. The most important thing in the process of using the mode is to understand the application area of the mode, each mode, corresponding to the abstraction of the special problem. ... The understanding of OO should be established in 1> Method 2> OO language implementation features: memory model and non-OO language memory model. 3> Understanding of the basic mode 4> Solve the problem with synthesis mode. ...
