Q. Which is the best way to solve defects - requirements, plan, design, code / testing phase?
Ans. In any phase, the sooner we see a defect, the less is the cost spent on rectifying the defect. It becomes a costlier affair in later stages. The best phase is Requirements phase. When the defect is found in later phases, it costs more for its correction.
Q. Cost of solving a bug from requirements phase to testing phase - increases slowly, decreases, increases steeply or remains constant?
Ans. 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.
No comments:
Post a Comment