DRE approaches for quality approach - Software Process Improvement

Discussion

• Nirja Shah   -Posted on 26 Oct 15
  Defect Removal Efficiency
  
  - A quality metric that provides benefit at both the project and process level is defect removal efficiency (DRE).
  
  - It is a measure of the filtering ability of quality assurance and control activities as they are applied throughout all process framework activities. To compute DRE:
  DRE = E / (E + D)
  
  - Where E= no. of error before release and D = defect found after release of software to end users
  
  - 1 is the ideal value for DRE.
  
  - That is, no defects are found in the software.
  
  - Realistically, 0 will be greater than D, but the value of DRE can still approach 1.
  
  - As E increases (for a given value of D), the overall value of DRE begins to approach 1.
  
  - In fact, the final value of D will decrease as E increases (errors are filtered out before they become defects).
  
  - DRE encourages a software project team to institute techniques for finding as many errors as possible before delivery.
  
  - It can also be used within the project to assess a team’s ability to find errors before they are passed to the next framework activity or software engineering task.
  
  - For example, the requirements analysis task produces an analysis model that can be reviewed to find and correct errors.
  
  - Those errors that are not found during the review of the analysis model are passed on to the design task.
  When used in this context, we redefine DRE as
  DREi = Ei/(Ei + Ei+1)
  
  - Ei is the number of errors found during software engineering activity i.
  
  - Ei+1 number of errors found during software engineering activity i+1
  
  - A quality objective for a software team is to achieve DREi that approaches 1.
  
  - That is, errors should be filtered out before they are passed on to the next activity.
  

➨ Post your comment / Share knowledge