Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

Requirements Based Testing Process Overview

[document] Submitted on 14 August, 2019 - 11:57
Keywords Requirements Based Testing Process Overview The requirements-based testing
Standards groups

Relative Cost to Fix an Error:
The reason for integrating testing earlier into the life cycle is simple economics. Studies have shown two things. First, that the majority of defects have their root cause in poorly defined requirements (see Figure 1). And second that the cost of fixing an error is cheaper the earlier it is found. The issue is scrap and rework. If a defect was introduced while coding, you just fix the code and re-compile. However, if a defect has its roots in poor requirements and is not discovered until integration testing then you must re-do the requirements, re-do the design, re-do the code, re-do the tests, re-do the user documentation, and re-do the training materials. It is all this “re-do” work that sends projects over budget and over schedule. Let’s say that a defect introduced during the
requirements phase is found during the requirements phase. Define the cost of finding that defect as 1X. If that same defect is not found until integration testing or production it will cost hundreds or even thousands of times more (see Figure 2).

Metadata
Date published
2009
Document type
technical white paper
Pages
18
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
Paper Bender-Requirements Based Testing Process Overview.pdf application/pdf   112.62 KB English DOWNLOAD!
File attachments
Defines standard
Visit also