OOD background knowledge
Computer hardware technology is developing rapidly. From a mysterious homonym, a mobile chip carrying it will be carried by now with a mobile chip that is running in each second to 10 billion computments per second. When software developers are still looking for "silver bombs" [Brooks, 95] that enhance software development and productivity, hardware development has already increased hundreds of times. Hardware engineers can be so efficient because they are very lazy. They always abide by the ancient training of "Don't go back to the wheel", "Class Category", now we usually call them "Component". Class belongings are composed of entities called class (Class), and the classes are combined between the class and classes. A class can hide a lot of details, only a simple interface, which is in line with people like abstract psychology. So, this is a great concept because it gives us the foundation for packaging and reuse, allowing us to see questions from the perspective of the problem, not from the perspective of the machine. The software is initially started from the function library and class library. These two multiplexed forms are actually white boxes. By the 1990s, some people began to develop and sold the real black box software module: Framework and Control. Framers and controls are often limited by platforms and languages. Now the new trend of software technology is a Web Service using SOAP as a transmission medium, which allows the software module to detach from the binding of the platform and language to achieve higher degrees. But thinking about it, in fact, Web Service is also object-oriented, but it is intended to describe the association between classes and classes [li, 02]. In the past decade, object-oriented technology has played greatly in the software industry. In the future, it will still be the main technology of software design - at least I can't see what technology can replace it. What is OOD? Object-oriented Design, OOD is a software design method and is an engineering specification. OOD is "The process of correlation between classes, classes, and classes of classes, based on demand." The goal of OOD is to manage interdependence of each part of the program. In order to achieve this goal, the OOD requires the program into a block, and the size of each block should be small to the level of management, and then hide each block behind the interface, allowing them to communicate with each other through the interface. OOD is a design paradigm (Paradigm), an abstract paradigm. Using OOD This design paradigm, we can use the object (Object) to express the entity of the problem, each object has the corresponding status and behavior. We just said: OOD is an abstract paradigm. Abstractions can be divided into many levels, from very summary to very special, and objects may be at any abstraction level. In addition, the objects that are different but interposed therefrom can be shared together: as long as there is similarity between these objects, they can be processed as the objects of the same class.
Comprehensive understanding of COM (Pick) Transaction allows components to form a set of independent operations a whole operation, and the transaction is either successful or fail. The object pool refers to the instance of the object in memory so that these objects can be used immediately when the customer requests to create an object. Like IMDB, the object pool is entirely due to the reason for the efficiency, used to establish a large application system.
