Data Center reconstruction (1) -- UML diagram, Data Center reconstruction -- uml diagram

Data Center reconstruction (1) -- UML diagram, Data Center reconstruction -- uml diagram

Finally, we started restructuring. Data Center reconstruction is a very important small project at this stage, because it involves all kinds of knowledge we learned during this time. First, we used the knowledge of softwares, write the document before development, and then use the UML diagram. The main development environment we reconstructed this time is VS, which involves the videos C # And. net knowledge. Finally, it is the comprehensive use of design patterns and layer-3 knowledge. Therefore, reconstruction is a trial stone we have learned at this stage and an important node for us to build a knowledge network.

The document mainly refines and supplements the previous steps, especially the descriptions of some flowcharts and sequence diagrams. After a few days, I finally finished the reconstruction of several pictures. Based on this requirement, I mainly drew package and class diagrams. As for the sequence diagram, I want to draw it later, this is mainly because the ideas for restructuring are not very accurate. First, do the most basic things (of course, the sequence diagram is also basic ), after you have a certain understanding of its development process, you can draw a picture to help you control the entire process.

Package diagram:

The package diagram mainly draws on the experience of the teachers and sisters and develops from a simple three-tier architecture to a seven-tier architecture. The UI, BLL, DaL, and Entity classes have been introduced before, so we will not introduce them here. Now let's take a look at several other types:

Facade, it also enhances code reusability.

Factory: Abstract Factory mode. This is a very important mode. For example, if a problem occurs in our current database or the database needs to be changed due to a certain requirement, the abstract factory mode can be easily replaced.

IDAL: interfaces are used to reduce Coupling Between Layer B and layer D and avoid confusion caused by direct operations on the database by layer B.

Class diagram:

Summary:

When you start refactoring, you have no idea what to do first and what to do later. Through this drawing and the improved documentation, I feel like I am learning three layers, maybe I don't know how to learn and how to implement a demo. However, in any case, you just need to grab a line and proceed. Now we are just getting started. We have already realized the concept and importance of "line". This system will bring us great gains.