Analysis of object-oriented analysis and design using VC for a period of time, in this time, the most in touch is the lack of object-oriented analysis methods for macro. Object-oriented analysis is one of the popular systematic analysis methods today. Here is some of my little experience in the process of doing projects.
Programmers can make a smooth solution solution in the face of simple systems, and in general, it is feasible. This is because the problem domain is simple, the internal structure involved is readily interpreted. For current increasingly complex systems, the problem is also increasingly complex, and the internal relationship is not easy to explain, and some large systems often exceed the ability to solve problems. In this case, the conventional faculty solution has not met the needs of increasing complex system analysis, in which case object-oriented analytical methods are particularly general.
In the object-oriented design area, the problem domain is divided into several different, low coupling, high-polygon problem domains in the horizontal direction, while continuing to decompose different small problems in the vertical direction, and finally decomposing the leaf node problem. Domain, thereby solving problems. In the face of object analysis methods, messaging between several objects is used to complete the entire problem.
Let's take a look at the five attributes of complex systems:
1. The heterogeneity is often manifested in the form of a hierarchy, and the complex system is composed of interrelated subsystems, and these subsystems are composed of their respective subsystems, and thereby push to the bottom of the base.
2. The choice of the most basic components in the system is arbitrary, and to a large extent on the determination force of the system observer.
3. In general, the connections within each component are always stronger than the connection between the members. This property is quite useful when separating high-frequency dynamics from the low frequency dynamics of the component. This is because high frequency dynamics involve the internal structure of each component, and low frequency dynamics involve interactions between components.
4. The hierarchical system is usually composed of only a few different subsystems through different arrangement combinations.
5. We found that the running complex system is always evolved by the previously running simple system ... Any complex system that is designed to make it is impossible to operate normally, and it is impossible to be repaired. We must start with a simple system in the run.
For the first point, as I said above, the system is hierarchical. It is possible to ensure the correct hierarchy of the system to ensure proper estimation of the system, including feasibility, maintainability, scalability ... and more. And for the maintenance of the system, the mainvation is well supported for the future.
For the second point, it emphasizes the observer's judgment. In fact, I also believe that it also includes the identity angle of the observer. For a system, the observer is not an engineer that is analyzed, and the programmer of the coding phase should include all of these people related to the system. As a different personnel, there is a different observation point, observe the angle, identity of special factors. Therefore, the system characteristics observed in different identities (referring to participants) even in the human eye of the same identity are different. Everyone in the university has been exposed to transparent concepts, which is an intuitive response to different observer observes. For users, basic underlying operations, algorithms, communications are transparent for them, they don't have to pay attention to it (in fact, I don't know) what I have used inside. For a programmer responsible for a module, it will not consider the implementation of other modules. For them, other modules are transparent, they only need to manage the function-provided module interface is OK.
For the third point, it is to face the direction of object analysis design. When the object analysis design system is facing the object analysis, the various modules being decomposed must be high, low and low coupling. There is a good high polymerization, and low-coupling systems are often easy to maintain, and a local change usually does not need to be involved in large changes, maintaining power. Moreover, for the more required efficiency of the VC program, high-polymer, low coupling can also improve the operational period efficiency of the program, should be less than the call within the module in general. Implementation time, this will improve the execution efficiency of the program running period to a certain extent within an object within an object. The fourth point illustrates the advantages of object-oriented programming to reuse the program design. In this "hierarchy system consists of only a few different subsystems", "there are so many subsystems that can be reused in different complex systems. For example, building a building and building bridge, although both are complex systems, but there will be many similar or even the same, there is no need to build a building bridge to redes every time. Fast brick tile.
The fifth point reminds us that when designing, try to use the previous subsystem that can run normally to rewind the new system. This point not only shows the reuse of the fourth point, but also shows a mistake we often have to make. It will not be brought to the large system by strict testing subsystems, which is not conducive to the grassroots level of the system, often introducing other errors, making the system frequently collapse, and the most serious will lead to systematic researchers.
This is my personal understanding of object-oriented, although we have different problems in the usual work, the development tools are different, but object-oriented is a way of thinking, conducive to analysis, solving problems One way does not hook any language (of course, the language is different for object-oriented characteristics). Therefore, I hope that all colleagues can use scientific methods to analyze the problem to form a design model for everyone to communicate with each other.
Software design is an art and an engineering.
