In the case when software bug is found at the initial phase then it should be removed during that phase itself rather than at any later phase. 

 

It is a well-known fact that if a software bug is detained for later stages it is much more expensive.

 

On this picture you can see how an error is costly as the stages move forward:

 

 

If an error if found and eliminated during the requirement and design stage it is the most cost efficient. At the same time if an error eliminated during maintenance it is 20 times more expensive than during the requirement and design stages.

 

For example, if a software bug is found during requirement and design you just need to modify the documentation, but if it is found during the maintenance stage you need not only to fix an error, but change your test plans, conductregression testing, and modify all documentation.

 

This is the reason why a software bug should be eliminated in earlier stages andsoftware testing team should be involved right from the requirement stage, but not after the execution phase.


http://qatestlab.com/

Share
Related Documents
  1. In What Stage Are There More Software Bugs? (2410)
  2. Basics of Software Testing Policy (2792)
  3. What Does Testing Company Need From User To Start Proper Testing? (2351)
  4. Principal Types of Verification (2486)
  5. Latent and Masked Software Bugs. What Is The Difference? (2770)
  6. Main Types of Defects in Software Testing (3498)
  7. Successful Bug Reporting (2468)
  8. Software Testing Documentation (2580)
  9. White Box Test Techniques. Linear Code Sequence and Jump Testing (3281)
  10. Control, Monitoring and Estimation in Software Testing (2654)
  11. The Main Goal of Acceptance Testing (2987)
  12. Undesirable Bug Reporting (2271)
  13. Configuration Management in Software Testing (2649)
  14. Workbench Concept in Software Testing (2576)
  15. What Is Software Bug Seeding? (1328)
  16. What Is Data-Driven Testing? (2582)
  17. What Is The Difference Between White Box, Black Box And Gray Box Testing? (1396)
  18. Validation and Failures In Software Testing (3029)
  19. What to Test and What Type of Faults Are Found? (1969)
  20. Verification and Conformance In Software Testing (2987)