4: IMPACT ANALYSIS
In any project if there is a change request by the client, if we want to modify the code to meet the requirement of the client then modifying the code will affect other progs relating to that prog. What are the progs being impact by that code is analysed and a document is prepared for that. This is Impact Analysis.
This is ans to my knowledge. Any one can help it out.
1) Review : Review is nothing but a walk thru to the code or script you are going on. Reviewer has to check about the standards followed & all the things which are very much specific to the entity He is working with, ofcourse apart from the functionality of the script.
2) UTP : Ofcourse its a UNIT TEST PLAN, which you conduct on each & every functionality of your script to check its working. You can prepare your UTP for a particular module with several kind of INPUTs & then you'll have to check for EXPACTED OUTPUT & ACTUAL OUTPUT. If both are same for every INPUT. Its going Fine.
4) Impact Analysis : As ssowjanya pointed out, Impact Analysis is to check for post-affects of the changes Or enhancments you are making.
5) Check List : I can't say there can be a standard definition, but the checklist is simply a document prepared specifically for each & every module to get you reminded of imp things when ever you are going to make any changes or enhancement.