How would a person "test" and "accept" software for automated aircraft landing ?
The software might work for a suite of "static" test cases but be unsuitable for "real-world" input data. (The real-world data might fluctuate around average values).
How would you educate your CEOs etc on the necessity to "ruggedize" the software so as to make it work for real-life data ?
Mandate that CEOs take an airplane ride once a week.






November 30th, 2009 at 5:20 pm
All depends on the matching of the static test data to the real-world data.
However, such tests would never complete, i.e. it cannot cover every situation. It is similar to doing penetration test in information systems, which is a never ending story.
Most software are tested according to certain standards, e.g. those in IEEE. Those are aiming on the perfection of the software itself, i.e. minimum glitch and vulnerability to zero deficit (zero means tolerable)
References :