"The completion of the computer room cooperation, we even a qualified it people," said Miss Rice.
participated in the 11 phase of the machine room cooperation acceptance, brother Siang sister from the function, UML diagram, documentation, code walk Four stages to make a review, the following talk about the process I summed up the idea.
First, Harvest:
(a) from the perspective of "user" to think about functional design
1. Login interface input Error What exactly does this hint say?
Before I do, my first feeling "if prompted ' your username or password error ' is a bit too unprofessional" like today's sister-in-the-line, the specific prompt to the user name or password, so that more convenient for users to modify, then Kun said, "Your user name or password error" is more consistent with security, I think the benevolent see, is really mountains outside the mountain, the function of the design process of thinking is once again opened, as if to breathe fresh air.
2. What is the order between the registration card and the student information?
Shaoxing Group and I before the reconstruction of the design is the same, the card and student information are registered separately, but in the registration card needs to check student information, if there is no student information, card can not register success, for designers, the registration card will naturally go to register the student information, Then the registration card to check the student information, but the user will do it? When registering a card, you will feel why the student information is not added? Is there a problem with the system?
This requires me to design the procedure in the future, do not completely from the developer's point of view to design the program, thinking to open.
3. is it true that at least the amount on the computer should be reflected on the machine?
For example, at least on the machine to set the amount of 3 yuan, the registration card when the registered capital of 1 yuan, even if the card registration is successful, but still can not machine, imagine, the purpose of the registration card is not to machine it? Why not put at least the limit on the amount of the machine to mention the registration card? So the card just registered can be on the machine? At that time the design was still "at least" in the amount of "on the machine" two words to limit ...
4. Combo Query whether the symbol drop-down list is " = "," < "," > "Change the settings?"
Teachers have been stressing that "serving the world wholeheartedly", why is it so difficult to embody the specific function? Do you choose "<" and ">" When choosing a person's name? Listened to this acceptance only to discover how superficial.
Recently also in and nine and 10 period brother Siang to do the evaluation system needs, found that want to design a good function, do demand more complicated than knocking code, this Part I feel in addition to experience, more important like today's harvest this point, thinking is very important, thinking when the position is equally important.
(ii) specification
Although I am not the team leader, but I think for "UI specification, SVN specification, code specification, database specification" and so I still need to pay attention to, not to say next time a project I will be the group leader.
For this machine room co-acceptance, I separately for today's system summarized as follows:
1. UI Specification
A. Cue box position to be placed in the same coordinate
B. In addition to the top right corner of the subform windows comes with the Close button, the system will add a close button for each page
C. The text box or drop-down list has default data and is real data.
D. The icon of the prompt box first or the same, exclamation point, greetings, information symbols used in the use of the scene, but also can not be used, today a group has two interface, while the Submit button, click to display the picture is an exclamation point, one is the information hint symbol "I", very obvious error.
2. Code Specification
Use of the Try catch statement:
There is a set of code used in the try Catch statement, but as long as the system has a problem error prompt out, the prompt interface is the same, not good, as above standing in the "user" angle to think about functional design, consider the user to see this interface feeling it? After the catch just need to write throw to OK, expression do not upload, we in the design process in order to facilitate the error can have, but released on the line, forget it, or specific problems specific hints, do not all use try catch, whole use try Catch is not a good choice either.
3. Document Specification
Soft work, the entire software life cycle if clear, I would like to write and use the document should be very much received, Mu Xiashi said, "demand, development, testing, maintenance" four blocks can be summed up this cycle, simple and clear, before their own memory this process has been chaotic ...
A. Write a document with a document cover, name, time, version and details.
B. Use case diagram notes, instructions to be detailed.
C. The use of design patterns in the class diagram (you can modify the class diagram slightly in later versions).
(iii) New discoveries
Today Mu Xiashi elder sister acceptance process of the computer system time to change, fast into one hours, the results of the money when the direct consumption of one hours of the amount, this is a big BUG, if so, the guest in the Internet bar in the administrator not secretly changed the control end of the system time, Is it equivalent to ask everyone to go online? Imagine that he does not change the specific time, but change the date, the day ahead, the Internet bar on the loss of a day's money, once such a thing, the boss lost.
So, real-time to calculate money, real-time update card balance, it is necessary!!!
Through today's acceptance, some fragmentary points on the summary, as mentioned above, the most important, let me broaden my horizons, very good.
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Computer room Cooperation--11 phase acceptance