The Charging System of the IDC has been completed for several days, but the summary has not been written until now. During the acceptance, the master asked me a lot of questions. There were two acceptance questions, and I felt very rewarding. Now we will summarize the problems and gains of acceptance. I. First acceptance of collection problems: 1. When the card number problem is registered in the form of registration card number, there is no limit on the length of the card number at that time, and unlimited input can be made.
The Charging System of the IDC has been completed for several days, but the summary has not been written until now. During the acceptance, the master asked me a lot of questions. There were two acceptance questions, and I felt very rewarding. Now we will summarize the problems and gains of acceptance. I. First acceptance of collection problems: 1. When the card number problem is registered in the form of registration card number, there is no limit on the length of the card number at that time, and unlimited input can be made.
The Charging System of the IDC has been completed for several days, but the summary has not been written until now. During the acceptance, the master asked me a lot of questions. There were two acceptance questions, and I felt very rewarding. Now we will summarize the problems and gains of acceptance.
I. collection problems
Acceptance for the first time: 1. When the card number is registered in the "register" form, there is no limit on the length of the card number at that time, and unlimited input is allowed. Similarly, each field in other forms must have a limited character length. 2. After the disk is saved successfully, the database data needs to be updated. At that time, my database was not updated. Similarly, the corresponding fields in the Database need to be updated for recharge, refund, and other forms. 3. After the problem is returned, you should not be able to recharge your account or go to the computer ." The two amounts in the registration form should show the same quantity. 4. Combined Query problem composite query should clear the table of the record as the record is cleared.
The second acceptance: 1. Amount problems when registering a user, the amount displayed on the registration form should be consistent with the "minimum amount" displayed on the "Basic Data Settings" form. 2. After selecting the user level in the "add and delete users" form for user level issues, after clicking the Add button, the user level in the "Add User" form should be automatically selected and cannot be modified. It is consistent with the user level selected in "add and delete users. 3. After the database is cleared, the data in the database should be cleared. 4. drop-down reminder: when the machine is about to be down, you can remind the user of how long it will take to get down, so that the user is ready to get down. 5. Out-of-the-box problem master: remind the user to go to the machine first to prevent the user from going off the machine. Me: I don't think I need to remind you that the user will return the card only after the host is down. It's impossible for him to return the card if he doesn't get down! Should this be the case according to the normal logic? So I don't think I need to go out and get off the server. 6. the checkout Logic first refers to the Administrator's settlement of the operator's account, and then all the operations in the checkout form (Card Purchase, recharge, card return, temporary user, summary) all operations are performed only on the selected operator. In addition, I have a specific understanding of each operation. Card Purchase: This operator sells cards for all registered cards, but here only the cards operated by this operator are closed. The information should include (card number, student number, date, time, amount), which is the user's money to the operator. Recharge: the operator can recharge all card buyers, but here only the account of the card sold by the operator that he has used to recharge the card. The user pays the operator.
Temporary User: similar to card purchase, only the operator has registered the card number. The user pays the operator. Return card: the user applies for a return card from this operator, and the operator gives the user money. Summary: The Administrator summarizes all the operations of the operator, and the operator pays the administrator. Exit: the Administrator performs the checkout operation. 7. In addition, the acceptance process does not have the function of running successfully: select the student offline and refresh the exercise in the daily report. Ii. Problem Analysis
These problems have exposed my biggest problem: I didn't thoroughly analyze the system from the very beginning, when I got the system from the very beginning, I was a little anxious to start from scratch. As a result, many logic problems may be messy at the end. This is one of the most important reasons. In addition, there are many reasons for the above problems: the form name definition problem, the database connection problem (mainly for the problem of "object variables or with block variables not set ), many of these problems are caused by Incorrect code writing and rough code writing. Iii. Analysis and Summary after the acceptance of the data center charging system, I learned that no matter what the program is, the first thing is to clearly analyze the user's needs. According to the user's needs, the logic of the train of thought is repeatedly clear, and the right remedy is given according to the clear logic. A little bit of system program, a little bit of completion of the system modules. Finally, implement the functions of each module to complete the entire project.
