Fault distribution is very uneven for the majority of software, not depending on their size, functionality, implementation language and other features.

Risk Identification Methods In Software Testing

Much empirical evidence has accumulated over the years to support the so-called 80:20 principle. It states that 20% of the software elements are answerable for 80% of the troubles.

Such problematic elements may commonly be described by specific estimation properties about their design, size, complexity, change history.

Because of the uneven fault distribution among software elements, there is a huge need for risk identification methods to analyze these estimation data so that inspection,software testing and other quality assurance activities can be concentrated on such potentially high-defect elements.

There are several risk detecting methods:

  • tree-based modeling
  • traditional statistical analysis methods
  • neural networks
  • learning algorithms
  • pattern matching methods
  • principal component and discriminant analysis

These methods can be described by such features as:

  • exactness
  • presence of tool support
  • ease of result interpretation
  • simplicity
  • stability
  • creative info
  • early presence
  • manual for quality betterment

Correct risk detecting methods may be picked to fit specific application environments with the goal to detect high-risk software elements for focused inspection and software testing.


http://qatestlab.com/

Share
Related Documents
  1. Definitions and Meaning: Error, Fault, Failure and Defect (4793)
  2. Software Test Efficacy. Meaning and Calculation (3859)
  3. Safety Assurance And Failure Scope (3737)
  4. Software Bug Handling Process And Tools (4638)
  5. Software Fault Tolerance Methods (4556)
  6. Main Software Testing Techniques (3788)
  7. Software Projects Analysis And Design (3574)
  8. Test Documents In The Software Development Lifecycle (3612)
  9. What Is Defect Removal Efficiency In Software Testing? (4366)
  10. What Is Documentation Testing? (2953)
  11. Classification: Quality Assurance As Operating With Software Bugs (3961)
  12. Quality Assurance In Software Development Stage (3960)
  13. How Can We Reach Quantifiable Quality Improvement? (4179)
  14. Operating with Pre-/Post-Release Software Bugs (4084)
  15. Requirements-Based Testing (6586)
  16. Waterfall Process In the Quality Assurance Activities (4373)
  17. Quality Estimation And Improvement (4373)
  18. Quality Engineering and Quality Improvement Paradigm (3832)
  19. Significance of Education and Training During Software Development (3833)
  20. Software Bug Handling In Various Quality Assurance Activities (3888)