December 27, 2017
Posted by: Peter Marcum
Software defect reduction is essential for eliminating future time-consuming work on fixing the defect as opposed to creating new development or new product. The upfront cost of eliminating the chance of defects is significant, but the cost of fixing defects is enormous. Therefore, software developers now have the capabilities of avoiding predictable pitfalls to help reduce errors in code.
It is 100 times more expensive discovering and fixing a software problem after delivery instead of finding and repairing during the requirements and design phase. Good design architectural practices can also decrease the cost-escalation factor. Another way to reduce software defect is to reduce avoidable rework by abandoning the traditional reductionist processes and instead embrace the emergent processes. These types of processes emerge through prototyping. Additionally, peer reviews are a critical component of reducing software defect. In fact, 60 percent of defects are caught through peer reviews. Overall, reducing software defect is a continuous process throughout development and can be accomplished in many ways.