From a circle for FOR cycle to talk about Wuhan Huazhong Normal University Triegue Xie Gang Summary: Talk to some of the details of the software design process should be paid attention to in the software design: Software design demand analysis, with the outside company Design a MIS system (using tools is PB8.0 MSSQL) is a safe production. In order to reflect the high quality service of our designer, I will help them in "demand instructions", which is: When the function window is opened each time, go to the database to automatically detect to see if there is any conflict data; That is, two exactly the same equipment is installed on two different machines. This feature, I believe that many friends will write, that is, the two loops are over. Yes, I was indeed written in two FOR traps. Nice, the design is very good. And it is a "demand description", and starts a little "nod". The last thing happened, I was told me that I was smirked: Yesterday, when the actual data of their company is guided into our MS SQL-Server, (a total of 9983 records, each record is 20 fields); discovery My function window can't be opened. Dirty life is not going! I helpless on the spot. After the "Black Box" and "White Box" test this afternoon, it was found that this 10000 * 10000 automatically detected the problem. That is, when executing this 10000 * 10000 cycle, the general machine has been a little bit no, in which case is also a large number of comparative work and verification in the database. Therefore, even if the AMD1500's dual CPU and 1024m memory are also a bit tired. Summary: 1, as long as it is "demand description", the function you have not written will not be smart, because you will only get a little "nod" in the company, there is no practical benefit. On the contrary, always buried a certain time bomb 2, when designing the program, must consider the algorithm, the so-called: program = data structure algorithm, this is true, pay attention to code efficiency, consider program execution efficiency 4, write detail Note and instructions (this habit is very important). 5, each modification is modified, and each test will record the test results and test data types and methods. 6. Seriously understand the "software engineering" knowledge, do not think it is useless. The above is a little idea, I am very happy today, I am here. Looking forward to the brothers and sisters. Xiegang Pen and 2004.06.04 afternoon; although not an excellent article, please invite you when you repost. Thank you for your cooperation
