Completion of the build and execution phases

Question

Is it compulsory to do testing after completion of the build and execution phases?

Answer 1

In established methodologies, testing is always done after the build and execution phases. However that is an incorrect way of thinking, because the cost will be more effective if we catch the defect earlier. For example, resolving a defect in maintenance stage is ten times more costly than resolving it during implementation. In the requirement stage we can confirm whether the requirements are according to customer or not. At the time of design we can verify if the design document are covering all the requirements. In this phase we can also make rough functional data. We can also analyze the design document from the architecture and the accuracy point of view. In the build and execution stage we can perform unit test cases and produce structural and functional data. And lastly the testing stage which performs in the fixed way. i.e., execute the system test cases and observe if the system workings according to the requirements of end user. At the time of installation we require to see whether the system is compatible with the software. At last, during the maintenance stage while any fix are prepared we can review the fixes and pursue the regression testing. So, Testing must take place in combination with each stage of the software development.