Machine Room Reconstruction (a)--UML diagram

Finally began to refactor, the machine room reconstruction can be said to be a very important at this stage of our small project, because it relates to our time to learn all kinds of knowledge; First we use the knowledge of the soft workers, to do the work of writing documents before development, followed by the UML diagram, and then the main development environment of our refactoring is VS, It involves the video of C # and. NET in our watch, and finally the comprehensive utilization of design patterns and three-tier knowledge. Therefore, the reconstruction is our study at this stage a trial stone, is our weaving knowledge network an important node.

The main document is to refine and supplement the previous, especially the description of some flowchart and sequence diagram. Took a few days to finally the reconstruction of several pictures, according to the needs of my main painting is package diagrams, Class diagram, as for the sequence diagram I think over a period of time to draw, this is mainly because the idea of reconstruction is not too accurate, first will be the most basic things done (of course, the sequence diagram is the basis), After a certain understanding of its development process and then draw, help oneself to the whole process of control.

Package diagrams

Package diagram is mainly to learn from the experience of Brother Siang, from a simple three-storey development to seven layers; UI, BLL, DaL, entity classes have been introduced before, here is no longer introduced. Now, let's look at some of the other things:

Facade: Exterior layer, this is a knowledge of our learning design patterns, mainly for decoupling, it can be very good to remove the coupling between the U-layer and B-layer, but also to enhance the reusability of code.

Factory: Abstract Factory mode, this is a very important mode, for example, if our current database problems or because of a need to replace the database, the application of abstract Factory mode can be easily replaced.

Idal: Interface, is also to reduce the B-layer and D-layer coupling between, to avoid the B-layer operation of the direct operation of the database caused confusion.

Class Diagram:

Summary:

Start to do refactoring when really do not know what to do first, what to do after. Through this drawing and perfect the document, feel oneself slightly into a little door, like learning three layers of time, perhaps do not know oneself how to study, how to achieve a demo; however, whatever you do, just grab a line and go down the line. Now is only the introduction, has realized the "line" concept and importance, this time the system will bring us a huge harvest ah.

Machine Room Reconstruction (a)--UML diagram