This is the first project made after graduating from our university and the first window. There is a lot of progress in yourself. From a language from 3 months, it is now basically possible to implement the design of the database. I have to say that I am a miracle for me, maybe I have learned Java before. So many things are easy to understand when using C #.
This system mode is initially defined as C / S, but it seems that the technology is not reached, so it still has a single machine version. The entire project is available from the purchase, storage, inventory, outbound, and is scheduled to do. It can be said that it runs through the entire core process, thanks to the trust of the boss, a new college students who have just graduated.
Success started from failure first. Mainly want to record the failure lesson. After reference, reference.
Program design.
The first is that the name is not unified, and the whole team uses its own naming way. It was originally considering a new language. Everyone was not familiar, so it did not emphasize, but it turned out that this is the most basic mistake. If it is not your own module, someone else cannot understand the code. Second, the merge module has not found a good method. At present, I don't know how to merge it. I just know that I have developed my code too difficult when I was joint.
2. Database design
Basically satisfy 3 NF, but the expansion performance is not good, the database changes too much as the demand of users. Difficulties in modification, so that even 1NF is not satisfied when the user needs to change.
3. Software design
It feels that it is to drag the Control, plus events and processing methods to the .NET designer. It is not used to object-oriented design thinking. I also blame me, in order to achieve the effect of the boss, only the interface, did not see the design (but the boss did not give me so much time to do or study these things, the boss is the effect of making it, he doesn't care what you don't design. I don't know if other software designers or programmers have this contradiction). After I recently read the object-oriented object-oriented object of C #, I said to myself: Next time I will not use this design method. Of course, there is a big problem with demand, people arrangement, etc., first of all, users in Beijing, we are in Guizhou, the boss is just verbally telling me, and even almost no. After waiting in a few days, I found that there is a problem when I have problems. I will call Beijing, and then the user tells me that I have a big difference in understanding, the halo results, the database is also changed, and the object-oriented, result Change from the head to the end.
The problem should be paid to the next design:
1. Standardize naming rules
2. Do you have to spend more time to do demand, the demand is incorrect, and the half-way discovery is changed, and finally I have never never, and the user is not satisfied.
3. Be sure to use the object-oriented design, it is best to draw the UML map, here to determine the object, and the database also uses object-oriented design (reference "database system concept (the fourth edition of the original book)")
4. Do the module or program in the team inside the team.
