Removing software defects and errors – we’re closer to the Holy Grail!
Tags: QA Vs. QC, software bugs, software defects, software quality, software testing
Defect free or bug free software is in the wish list of many software vendors for ages and it hasn’t materialized and people are still looking for the Holy Grail. No piece of software can be bug free, however we can ensure that it works well in a controlled environment.
Defects are introduced in the software at all phases starting from requirements to analysis to design to development to verification to implementation to maintenance. In addition, 50% of the bugs are introduced when programmers try to fix a known bug. Essentially, any activity that is performed by a programmer or a member of the project team has potential for introducing a bug, which will in turn result in a defect and not allow the software from serving its intended purpose.
QA and testing will have to be done throughout the development life cycle. QA will certainly prevent defects from entering the software. However, QA can only do as much, and it cannot remove defects that are already there in the software, which is caused by the unknown factors during design and development. Testing can certainly remove defects and improve delivery confidence towards releasing the software to the market. Both QA and Testing (QC) will have to go together towards ensuring software quality.
Test early and test often should be the ‘Mantra’ and repeated cycles of testing and resolution can allow software vendors to identify the risks – allowing them to make informed decisions and ultimately reducing bugs and uncertainty.