Cost of solving a bug from requirements phase to testing phase - increases slowly, decreases, increases steeply or remains constant?

  • Interview Candidate
  • 56
  • 4180

Showing Answers 1 - 56 of 56 Answers

SatishTKakade@yahoo.com

  • Aug 2nd, 2005
 

Cost of solving a bug from requirements phase to testing phase - increases slowly 
 
 

  Was this answer useful?  Yes

raj

  • Oct 5th, 2005
 

increases steeply requirement --------- x (say for fixation cost per bug)planning ----------------5xdesign -----------25 xcoding ---------------------70 xtesting --------------------- 100 x

rajaniqa

  • Apr 23rd, 2007
 

In any Methodology, the defects found in the earlier stages would reduce the cost of fixing the same drsatically when compared to identifying and fixing them at later stages.

Be it be Waterfall or Agile Extreme programming, the cost of solving a bug increases from the requirements to the later stages.

Please correct me if my understanding is wrong!!

Thanks in advance.

saransh

  • Jun 21st, 2007
 

Cost of solving a bug from requirements phase to testing phase increases slowly till design phase and after this it increases speedly.

  Was this answer useful?  Yes

siteuse

  • Jun 28th, 2007
 

yes i agree with Rajaniqa.
But i also want to know why others are saying that Cost of solving a bug from requirements phase to testing phase increases .Can anybody explain this clearly!

Thanks

  Was this answer useful?  Yes

maddy14

  • Jul 3rd, 2007
 

cost of solving a bug from requirement phase to testing phace gradually increases and testing stage is the bottle neck stage i.e at this stage all the defects in the software shd be detected and solved.

  Was this answer useful?  Yes

upendrah

  • Jul 19th, 2007
 

Yes it increases as  we need to revamp from the beginning. ie., If we detect that error in the initial phase itself then we can make the change there on and it will not cascade to the next stage. But as we proceed to further stages, then the cost increases as we need to make changes from the initial stage to the bug identified stage. This involves not only cost but also time.

  Was this answer useful?  Yes

Kumud Bajaj

  • Jul 31st, 2007
 

The cost of fixing the bug increases tenfolds from requirement Phase .

  Was this answer useful?  Yes

Sujatars

  • Aug 15th, 2007
 

Cost of solving bug from requirement to testing increases steeply,the overall cost of fixing bugs in early requirement phase is always lower than the cost of solving bugs in testing phase.

  Was this answer useful?  Yes

Porush Parasher

  • Oct 12th, 2007
 

Thats because the more later you find the bug the more resources are used to find and fix it, over all after a completed cycle for one phase ones need to re check the whole cycle, and that will drastically increase the time and cost from phase to phase.

  Was this answer useful?  Yes

preeti.indoori

  • Dec 3rd, 2008
 

When the bug is identified in the initial requirement phase then it would be easy to fix as it would not go for the coding by the developers and then later passed on as a build to the testing team where tester has to test it find the bug and then send back to the developers then it goes back to the business analyst to verify it and again fix the requirement. Basically lot of time and money is wasted, as faulty requirement goes through the entire cycle of development and testing. 
 I hope  this was useful

  Was this answer useful?  Yes

vk1978

  • Feb 20th, 2009
 

In any Life Cycle, defects in the later stages increases Cost because the
amount of work needed to do, the resources needed to complete the additional
task, the time spent on it, meetings and of course amount. let me tell you an
example, assume if 3 different critical issues with respect to
Design/functionality of the application are found in these 3 different stages
lets say 1st critical defect found in design, 2nd and 3rd critical defects found
Coding Phase and Testing phase.


So to fix the 1 defect, in design phase it is obvious that by this time not
all the documents are finalized or else i can say coding stage is just started,
so BA or High level management can fix it with some effort by doing changes
according to the need, as they have lots of time for the release of first build,
but for the issues found in coding and testing phase, changes has to be done in
Requirement documents, Design documents, specifications, Application Design,
Code written to develop application etc., by the respective members and also all
the related and effected documents with respect to Testing like Test plan, Test
objectives, traceability matrix, test cases, raising or closing the bugs that
are linked with the defect etc., needed to be change by test team, and more over
assume the situation if such kind of defects were found when major release is
nearby (in a week's) when build release dates gap is decreasing drastically
build after build due to the issues.

mithr17

  • Nov 1st, 2011
 

If you are asking this question, it means you have not understood SDLC nor any of the QA concepts for that matter.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions