The early detection of error causes the impact of it very negligible. So after each and every phase of the software there needs to be a FTR.
Let us find out the objective of the FTR:
- To uncover errors in function, logic or implementation for any representation of software.
- To verify that the software under review meets its requirements.
- To ensure that the software has been represented according to predefined standards.
- To achieve software that is developed in a uniform manner.
- To make projects more manageable.
It does includes walkthroughs, inspections, round-robin reviews and other small technical assessments of software. The key point to make a review meeting successful is that it should be properly planned, controlled and attended.
Next section will introduce you the guidelines of the FTR which needs to be followed.
