Talking about software design from a trap for loop [original]

Software design from a trap for Loop Xie gang, Department of Information Management, Huazhong Normal University, Wuhan Abstract: Let's talk about some of the details that should be paid attention to in the software design process based on one of our actual experiences. Keywords: software design requirement analysis Some time ago, I designed a MIS System (pb8.0 + MSSQL) with an external company ),It is about secure production. In order to reflect the high-quality services of our designers, I have designed a feature for them in addition to the requirements description, that is, every time this function window is opened, go to the database to automatically check whether there are conflicting data; that is to say, whether two identical devices are installed on two different machines. I believe many of my friends will write this function, that is, two loops and one trap will be completed. Yes, I did use two for traps. Good. The design and thinking are both good. In addition to the Demand description, I started to get a little nod from the company ". What happened later made me smile: Yesterday, when the actual data of their company was imported to our ms SQL Server, (a total of 9983 records, each record is 20 fields ); I found that my function window could not be opened. It's hard to get in! Helpless on the spot. This afternoon, after the "black box" and "white box" tests, countless tests found that the 10000*10000 automatic detection was faulty. That is to say, during the execution of this 10000*10000 cycle, the general machine cannot be opened. In this case, a lot of comparison work and verification are also done in the database. Therefore, even amd1500 Dual CPU and MB of memory are a little tired. Summary: 1. As long as it is a feature that is not written in the Demand description, do not be smart, because in this way, you will only get a little nod from the company, and there is no practical benefit. On the contrary, a time bomb will be laid for you at all times. 2. DesignProgramYou must considerAlgorithmThe so-called program = Data Structure + algorithm, indeed 3. Pay attentionCodeWhile taking program execution efficiency into account 4. Write detailed comments and instructions (this habit is very important ). 5. Each modification is recorded, and the test results and test data types and methods are recorded in each test. 6. Be careful with the knowledge of software engineering. These are some of my thoughts. I am very happy today. We still hope that our brothers and sisters can make an axe. Xiegang was written in person on the afternoon of 2004.06.04.Article, But please note the source of the post. Thank you for your cooperation