Actually Its quite project specific we cannot talk about the life hazards when we are testing a stapler.. can we? That would be quite generic..
Let be particular to Software testing which mostly doesnt have any life hazards.. we have to put it in such a way the person understands the importance of testing from generic facts.. rather than examples.. 'If u talk about an example like NASA project obviously the clients reaction wud be 'I dont run a NASA out here I dont want to spend more'.. Isnt that true?
1. Software testing can compensate for the fact that the software development process does not identify the true needs of the user and thus test to determine whether or not the user’s needs have been met regardless of the specifications.
2. Finding defects early in the software development process when they can be corrected at significantly less cost than detected later in the software development process.
3. Removing defects of all types prior to software going into a production state when it is significantly cheaper than during operation.
4. Identifying weaknesses in the software development process so that those processes
can be improved and thus mature the software development process. Mature processes produce software more effectively and efficiently.