Mena1710

 Profile Answers by Mena1710 Questions by Mena1710

• Jan 21st, 2008

 

Hi

I assume that you are talking about Root cause Analysis.  We can take an example of the defects logged with respect to any software.  We will be logging this defect with respect to module.  Just one step further we need to find out from the defect, from where it has arisen, is it from the basic design, or logic, or due to system testing etc

This Analysis we do to avoid these type of defects in our future products and improve on ours selves

Hope this is clear

Thanks
Anna

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 17th, 2009

 

Root Cause Analysis is a class of problem solving methods aimed at identifying the root causes of problems or events. The practice of RCA is predicated on the belief that problems are best solved by attempting to correct or eliminate root causes, as opposed to merely addressing the immediately obvious symptoms.  When test discovers a defect, it is always good to question whether the defect identifies a symptom or root cause.  If it is a symptom of an underlying cause, then the tester should investigate further to isolate the deeper cause.  For example, a tester may author a defect which describes poor performance on several different pages in a website.  Upon further investigation, it may be discovered that a common image was used on these pages that was much too large (not within spec) which caused the loading times to drastically increase.  Though the lengthy time to render was the symptom, it was the image size that ultimately caused the problem.