Vb. NET computer room Charge System Summary

always feel this computer room charge system is very heavy, has not been a summary, from 2014-7-27 to 2014-9-29, There are too many stories and growth in the middle. First of all, the difference between the two-time computer room charge system, it is we from the process to the object-oriented transformation, in the . NET Platform under the development of three layers of thought, and add some design patterns, and then say my changes, No matter from the thought or technology is absolutely a wealth, after the computer room charge system, I more firmly believe that two words: "Come out to mix sooner or later" "Everything Will pass."

        This personal refactoring:7.27-8.11(drawing phase, which includes data design2days);8.12-9.14(Code implementation, in the middle of a week to prepare tomato template courseware);9.15-9.20(document, modify diagram);9.21Brother Siang Acceptance;9.23-9.28(Modify the problem, in fact9the month does very little work). Because this is ourC/Sa relatively complete project, should follow the development process, to the present summary of a feeling, personal reconstruction is the wholeC/SStudy of the synthesis or leakage of the vacancy, the front software engineering,UML,. NET, three-storey and design-mode things all blend together.

         first in the paint phase, this is necessary, there is the end of this part of the work, That's because we did it once, the basic ability to understand the same, this drawing understand the ea 4 . Span lang= "ZH-CN" style= "Font-family:simsun", Package diagram: The division of the entire system module, each package in the face of the class, use case diagram, and then the corresponding sequence diagram under each use case, where I according to the class diagram is the most difficult, The pass of the method does not know what the parameter and return value are, and if the class diagram is well-drawn, the sequence diagram can be dragged directly there. In this lack of object-oriented abstraction is not good, many classes of methods can be abstracted (for example, many functions are used to determine whether the card number exists, you can create a separate method, not in each class to establish the method), there is the package diagram in the interface, factory and d

Database design taking into account the three paradigm principle, the biggest change is to realize the separation of card and student information (http://blog.csdn.net/u010097777/article/details/38796793) , there is the table in the fields are designed to consider when to use (such as recharge and return card status field), in the first room in the use of someone else's database, some fields do not know what to do with, and the deepest feeling is the conversion of data type, This is also a very silent thing behind, especially the time-type conversion, as well as char(fixed length) and varchar(variable length) in judging user rights can let me spend a lot of time debugging it.

        Code implementation: Building a seven-tier environment is important, I did not add abstract factory when I was learning three layers+Reflection+configuration file, this time can let me laborious, read a lot of blog, a week to take off, are the first contact, understanding is too good, began not to know from that layer began to knock, ask after know the first interface layer, the factory layer, then isDlayer,Blayers andUlayer, you really have to knock a line and see how the code walk will understand a lot. This refactoring uses the view http://blog.csdn.net/u010097777/article/details/39268659, stored procedures+Business http://blog.csdn.net/u010097777/article/details/39432449 , and so on, the most want to say is to encounter problems to think about how to use a more simple way to solve, These tools are also adapted to our needs, but also out of the mix sooner or later to pay back, before learning the database when things are compensated. The addition of design patterns is a challenge, but at this stage we are imitating, adding the appearance, template http://blog.csdn.net/u010097777/article/details/39638017 and the singleton http:/ /blog.csdn.net/u010097777/article/details/39718549, feel is to be bold to try, have the idea is good, really is this, this time the machine code is oneself writes, although the abstraction is also not good, but the function still realizes. There are a lot of problems in the middle: assemblies are not loadedDAL,The object reference was not added to the instance, the table could not be found, and many issues were resolved:Checkout control lookup, global variable usage, etc., in short, I will be the first initiative to find solutions to solve, really can not solve will also discuss with them, such as the child parent form this feeling of a clear than my method is better http://blog.csdn.net/u010097777/article/details/ 39719921.

       Brother Siang Acceptance, they stand relatively high, in addition to some judgments, norms and the like,UIdesign also uncomfortable let people, modify student information, forcing all the function of the next machine, the biggest problem is that I object-oriented abstract bad,Blayer code is rare, andUthe layer has a large number of judgments and directlyDlayer information back to the interface, where is this decoupling? Later, the on-machine method was written to the appearance in the modification, so that all return values were not returnedUlayer, but the machine I was not able to abstract out, because the machine calculates time and money when I was directly usedUlayer interface data, but the appearance cannot be referencedUWhat about the floor? So there are problems in forcing the machine. In the process of modifying the diagram, it is important to realize the original specification diagram, the parameters, the return value, the comments should be accurate, and so on when we cooperate in the development of the layer.

Legacy: No packaging release, the next machine can not use the strategy mode, forcing all the problem of the next machine, personal reconstruction temporarily, feel oneself from a rookie in the growth, but also let me realize that their road is still very long.

Vb. NET computer room Charge System Summary