Summary of VB. NET data room charging system Personal Edition

In the C/S stage, we learned software engineering, UML, and VB. net, the design model, three-tier architecture, and a simple understanding of the C # language basics. With the accumulation of these theories, we began to use the data room charging system for practice, only by practicing this knowledge can you become a real person, because you can understand it deeply only when you are a real person.

The individual version of the data center charging system has been written twice in total, and only three layers are used once. I call it a simple three-tier Data Center charging system, with the aim of further understanding the three layers, and VB.. NET language. Because it was the first time, coupled with the start of school, it took a lot of time. It took a month and ten days, and it was a waste of time.
The second time, I call it the plus-design mode data center charging system. I added the design mode, sqlhelper, which once gave me a headache, and various database operations, such as views and stored procedures, the trigger is also attempted. Of course, retional is not used this time.
Instead, you can use EA and EA to map the code, documents, and UML diagrams.
This is intended to learn these things. Of course, I feel more deeply that I have a deeper understanding of object-oriented programming languages by comparing the two. It took about two months to start and end.

Let's talk about it first. Because there is no design mode, it is still quite easy to draw a picture. With the help of the login example, it is probably quite smooth. This time, we actually implemented a system in a three-tier architecture with object-oriented features. Only by truly experiencing the advantages of modeling first and then realizing the differences between the project manager and the code engineer. Although it was implemented by line and line by line this time, but with the figure, I feel that the implementation code is much simpler. At least I don't have to worry about it all the time, the logic is very clear. During this period, I asked Hui Ge some questions. Some of his general guidance is still very useful. At the very least, I have a bottom in my mind, in this way, I have finished writing this article, because I have done it again later, and many things are nonstandard. Hui Ge asked me to continue.

In the design mode of the second repeat, we first started with the login example and implemented a login example to clarify his sequence diagram and package diagram, in this way, the data center charging system is simple. Although it seems redundant to add some design models to the data center charging system, we are trying to learn how to learn the design model and experience its benefits. When the login example with the design mode is very clear, we started to use the new tool EA to model the overall system. With the foundation of the first modeling, the figure drawn in this modeling process is more comprehensive. Although the design mode is added, I feel that I only called it several times back and forth. I still feel very deep with EA, and it feels better than retional for our real software.
Rose is more powerful, or it can be said that it is more convenient for us. This implementation code is basically implemented by layer. It is quite comfortable to write code by layer and write code by layer according to the diagram. The most profound experience is the interface between each layer, the importance of the method name specification, so that there can be a good connection between each layer. Through two comparisons, we can better understand how to do object-oriented design.

In my self-built IDC room charging system, what impressed me the most was the document specification. During the Acceptance Period, Bao Qiang Shige said, "the first time the IDC room charging system was mainly used for acceptance of your functions, the second step is the standardization of object-oriented modeling documents and graphs!" Indeed, during the Acceptance Period, Master Hui Ge raised many non-standard questions to me. However, after three days of modification, it was basically completed, and it was definitely not perfect. However, it gave us a profound lesson for the next system. This is also our step towards project manager, the beginning of leadership. There is only one standard for writing documents. It is perfect to show others the documents you have written to make a system. This requires us to grasp this degree through continuous experience accumulation. This suddenly reminds me of the most important experience in the IT industry.

I have gained a lot from the individual version of the data center charging system. This has brought me a step forward from the previous object-oriented process, which is more practical today. Like the conversion from c/s to B/S, we are making a subtle change ......