Computer room Reconfiguration---what have we "reconstructed"?

The computer room reconfiguration is about to end, at the end of this "third" system, it is necessary to think about the purpose of our reconstruction.

Perhaps some people say, there is no purpose, is not the programming language changed to. Net, make, adjust the bug, can run to get Bai. What a strength to be in such a pompous day.

For those who have this idea, I must say: you (white) hard.

No matter what you do, there is no way to make a summary of your thinking.

I have some of the following reconstruction of the discussion or review of the summary also has a lot of deficiencies, I hope you can correct this, thank you first.

This paper will discuss the reconstruction system from five aspects, namely system architecture, UML diagram guidance, design pattern application, data processing and object-oriented.

First, the system architecture aspect .

In this refactoring, we have used three-tier architecture to reduce coupling, improve the reusability and maintainability of the system and other purposes. In the design, and the first room of the basic process-oriented programming, we do have a profound understanding of the architecture is convenient and easy to maintain.

By adding basic auxiliary modules or tools, such as appearance, SqlHelper, configuration files, and so on, we once again realized the great convenience of the independent encapsulation, from decoupling to encapsulation, we saw the object-oriented.

Second,UML diagrams and Documentation guide . The focus is on UML diagrams, where use case diagrams, package diagrams, class diagrams, and sequence diagrams are key.

Package and "Three-layer", class diagram and three-layer D and B-layer design (different classification criteria, such as database table or function for B-layer design), sequence diagram of the function implementation process guidance, etc. are inseparable, we need to be carefully analyzed in advance. These are, of course, based on requirements analysis and use-case design.

Again, design pattern aspect .

So far, the difficulty in applying design patterns is how to map a function or series of systems to design patterns. In the course of learning, it is important to understand and visualize each instance, so that we can better correspond to the later system case analysis.

In the computer room reconfiguration, at present I understand or use the design pattern application has:

Policy patterns-Implementing different billing methods for different types of users

Abstract Factory + Reflection-simplifies switching of different tables

Appearance-the appearance layer between the U-layer and B is further decoupled to make the U-layer more independent

Templates-Similar forms do not need to repeat the code over and over

Adapters-External reports and vb.net fusion

Single example-Ensure that a form is not created by various new

Responsibility chain-from the general user to the operator to the administrator, there is always a problem to be solved

Talk about data processing again.

Data processing is an issue that needs to be addressed at all times, especially in the modern era of large data, where efficiency and security seem to be more important. In this computer room reconfiguration, some of the database functions have a more in-depth understanding.

It says two points here. First, the database was built and improved on the basis of the jerky of the database and the lack of the necessary three-paradigm analysis. Even in the system programming process, sometimes still can not avoid to move the database, change the field, to make up for our analysis of the deficiencies and temporary inspiration.

Second, when we repeatedly pass the marked "transactions, stored procedures, triggers, views," and so on the key words of the road signs, it is necessary to stop to explore some. Stored procedures and trigger execution convenient cut more in line with the packaging features, transactions on the system some "interaction" of the strict control features such as we have to explore their advantages, and then apply. The application of stored procedures such as the upper and lower machine, combined query, etc. transactions can be considered for recharge, checkout aspects.

Finally, talk about the system and object-oriented .

In this reconstruction, we realized the idea of object-oriented everywhere.

For example, inheritance: The administrator of the operator's inheritance, the operator of the general user's inheritance, not only clear their relationship, but also simplifies the structure. In addition the application of the interface is also inheritance.

Encapsulation is more, data encapsulation, functional encapsulation everywhere. A good system design requires a very deep understanding of object-oriented, interface-oriented, in addition, practice in the actual operation is to enhance our understanding of the best means.

Summary : For this room reconfiguration, there are many practical application of the deficiencies, how to put these thoughts through this refactoring, or even the next cooperation version of the implementation of the experience is the best supplement. So in response to the following learning, you can take the study itself as a system for perfect analysis and best practice.