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

can u explan me clearly wt is web based app: and client server app:

2 Answers   HCL,


what is the difference between defect age and build intervel period?

1 Answers   Semantic Space,


whatis the diff. between Tracebility matrix and Bidirectional Tracebility matrix?

2 Answers   AZTEC,


Why do you consider testing to be necessary?

3 Answers  


what are the feature of our test group?

0 Answers  


How to download QTP 9.5 Trail version? please explain the complete process?

2 Answers  


What are the benefits of automated testing?

0 Answers  


How many defects is acceptable for a project. Is there any goal for no. of defects.

3 Answers   FIC, MinMax Software,


Whose level is higher in between QA, QC and tester and their role and resposibilities and job profile.

1 Answers  


what is confirmation testing??

2 Answers  


List out the roles of software quality assurance engineer?

0 Answers  


What is Database Testing? How will you do it?

10 Answers  


Categories