It is said [Software Defect ReductionTop 10 List] that, ‘about 40 to 50 percent of user programs contain nontrivial defects’.
What are some nontrivial defects and how to overcome them?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It is said [Software Defect ReductionTop 10 List] that, ‘about 40 to 50 percent of user programs contain nontrivial defects’.
What are some nontrivial defects and how to overcome them?
I would interpret “non-trivial” as “has a real impact on the user”.
For instance, if a menu item has a typo in it, that would be a trivial defect. If your spreadsheet application crashed when it tried to save any sheet with the number “999” in, that would be non-trivial.
I’d be hugely surprised if the number was really as low as 40-50%. In my experience pretty much every signficant application has non-trivial defects, even if they’re rarely encountered. (If I’m the only user in the world who uses the number 999 in a spreadsheet, the bug is still hugely important to me so I don’t think it can be classed as trivial.)
As for “overcoming” defects – the normal barrage of unit tests, continuous build, automated integration tests, manual testing, making sure you have a really good user feedback system, and management who are willing to put resources into fixing bugs as well as creating new features.