Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


What is defect management in QA?

Answers were Sorted based on User's Feedback



What is defect management in QA?..

Answer / rao

Defect management is nothing but daily actitivites you
performed on logged defects against functionality. Every
day you have to find any status changes in ur logged
defects and you need to be idetify the how many active
defects are there and need to find that any defect leakage
and the trend of the defectsw.

Is This Answer Correct ?    1 Yes 1 No

What is defect management in QA?..

Answer / vr

In Simple, Taking care of the defects sill its Closure.

Is This Answer Correct ?    0 Yes 1 No

What is defect management in QA?..

Answer / lakshmanaraj bg

Defect management in QA:

A process for analyzing and classifying defects and problem reports is an important part of defect tracking against quality targets.

The defect management process is based on the following general principles:

The primary goal is to prevent defects. Where this is not possible or practical, the goals are to both find the defect as quickly as possible and minimize the impact of the defect.

The defect management process should be risk driven -- i.e., strategies, priorities, and resources should be based on the extent to which risk can be reduced.

Defect measurement should be integrated into the software development process and be used by the project team to improve the process.

In other words, the project staff, by doing their job, should capture information on defects at the source.

It should not be done after-the-fact by people unrelated to the project or system

As much as possible, the capture and analysis of the information should be automated.

Defect information should be used to improve the process. This, in fact, is the primary reason for gathering defect information.

Most defects are caused by imperfect or flawed processes.

Thus to prevent defects, the process must be altered.

Is This Answer Correct ?    0 Yes 1 No

Post New Answer

More QA Concepts Interview Questions

How many levels of ISTQB Certifications r there? What r they? When they will be commenced?

2 Answers  


how can u find system IP address

5 Answers  


How does the Internal QA Audit relates with the ISO Standards level ?

0 Answers   QA,


What are the challenges faced with the 1+ years experience team.

0 Answers   Bharat Petroleum,


What is the cost of quality?

5 Answers   Covansys,


Hi I m working as a sqa engineer and after 1 yr i want to switch to system analyst side kindly tell me how both fields relate each other and is this easy to switch job from qa to system analyst and what's the difference b/w both fields.

0 Answers  


Have you used any automation tools?

0 Answers  


what is the entry & exit criteria of testing process?

6 Answers   APC, MBT, Microsoft, Nortel, TCL,


Explain what is bug triage?

0 Answers  


If we don't caught any bug in all build, then what we can say - 1. Bad Coverage 2. Excellent Coding 3. Bad Testing

5 Answers  


what is query to see the "user" in SQL Server 2000

2 Answers   Satyam,


What is the rule of a "test driven development"?

0 Answers  


Categories