Today, I will be summarizing an interesting article I found on www.softwaretestinghelp.com about software quality assurance and how to prevent defects in a timely fashion. The article, entitled “Defect Prevention Methods and Techniques”, was last updated in October 2017, but the author is not credited. I selected this article as a topic for a blog post because I found it interesting how it provided a definition to “quality assurance” as well as methods and techniques on how to prevent software defects during development.
The article begins by differentiating between quality assurance and quality control; quality assurance activities are targeted toward preventing and identifying defects while quality control activities are targeted toward finding defects after they’ve already happened. The reason that the emphasis of this article is on quality assurance and defect prevention is because, according to the article, defects found during the testing phase or after release are costlier to find and fix. Preventing defects motivates the staff and makes them more aware, improves customer satisfaction, increases reliability/manageability, and enhances continuous process improvement. Taking measures to prevent defects, early on,not only improves the quality of the finished product but also helps companies achieve the highest Capability Maturity Model Integration Level (CMMI).
The process of preventing defects begins after implementation is complete and is comprised of four main stages:
Review and Inspection – Review of all work products
Walkthrough – Comare the system to its prototype
Defect Logging and Documentation – Key information; arguments/parameters that can be used to support the analysis of defects
Root Cause Analysis – Identifying the root cause of problems and prioritizing problem resolution for maximum impact
This process often requires the involvement of three critical groups within an organization, each with their own sets of roles and responsibilities;
Managers are responsible for:
- Support in the form of resources, training, and tools
- Definitions of appropriate policy and procedure
- Promotion of discussion, distribution, and changes
Testers are responsible for:
- Maintenance of the defect database
- Planning implementation of changes
Clients are responsible for:
- Providing feedback
The article concludes by emphasizing the importance of defect prevention and its effect on the final product. I believe that actively participating in a process of avoiding defects before the final stages and release of a product is good practice and should be followed just like any other beneficial development strategy. The article certainly contributed to my repertoire of development techniques and I think I will refer to these concepts in the future.
From the blog CS@Worcester – by Ryan Marcelonis and used with permission of the author. All other rights reserved by the author.
