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

What is your understanding regarding a test plan?

0 Answers  


what is meant by positive testing ?

4 Answers  


If Technical manager is not addressing to bugs while releasing the project , then how u can treat that bugs? a.open b.closed c.pending 4.deffered

11 Answers   Logica CMG,


What is the audit process? How do you perform the audit?

1 Answers   Cap Gemini, Sparsh,


HOW DO YOU REPORT AND TRACK A BUG

3 Answers   HCL,


Difference between ISO and CMM (No Abbrevations, Only concepts)

1 Answers  


hey, i recently attended 2 interviews and they asked whether I used qamonitor of softsmith. any help on what it does?

2 Answers  


iq test

0 Answers   Equinox,


what is build and release and what is the difference b/w them?

1 Answers  


what is Quality product?

5 Answers   Accenture,


What is Impact analysis.how to do impact analysis in yr project..

12 Answers   MBT,


What is conversion testing?

1 Answers  


Categories