??? 07/07/05 18:52 Read: times |
#96792 - another article of interest Responding to: ???'s previous message |
http://ganssle.com/articles/crashburn.htm I have to do my code walk throughs with my boss, who knows nothing about software, but we have a software design specification and a software verification test plan. We go through the code line by line and I have to explain to him what the software is doing. It is at this time that software bugs are caught. Theoretically, testing should catch all of the bugs, but in practice, the testing either would take too long or the resources just are not available to do a thorough test of the code. By thorough, I mean that you are testing every possible input and recording the result and doing this for every function that exists in the software. Even then, you couldn't be sure that some external hardware condition wouldn't trigger some unknown sequence of events causing your software to crash. Jacob |