For all but truly trivial problems, it is impossible to test every possible situation that the program might encounter. Users can imagine far worse "data-driven scenarios" than any test engineer or programmer can think of. In a very important way, this is all about achieving software correctness.
For this module, let's talk about how we design to be "fail-safe." Also, look at how we lay out a verification and validation strategy that can affordably gain us enough reassurance to release a software system to its end users. That V&V (verification and validation) strategy includes a mix of the main techniques of software quality assurance: inspection, analysis, test, and simulation.
Since you cannot test everything, or test it exhaustively, how do you go about choosing what mix of V&V strategies to use, or how much of them to use to be able to feel ready to hand the software over to the end users with a clean conscience?
You should also answer the following:
If you'd like to use additional resources (such as from the Internet) to help in developing your discussion post, thats great-just be sure to provide proper citation to your source, and use your source, dont just quote from it! Generally speaking, your responses should be two to three paragraphs (about 300 to 400 words).