Hi........

Change Request is a attribute or part of Defect Life Cycle.

Now wen u as a tester find a defect n report to ur DL...he 
in turn informs the Dvpt Team.
The DT says its not a defect its an extra implemnetation or 
says not part of req'ment.
its new.cust has to pay.

Here the status in ur defect report would be Change Request

I think change request controlled by change request control 
board (CCB). If any changes required by client after we 
start the project , it has to come thru that CCB and they 
have to approve it. CCB got full rights to accept or reject 
based on the project schedule and cost.

Hi Sriharsa And Mavan,

Ur ans for CR is bit related to it but not exact.
CR means wen a tester log a bug, the dev team has to fix 
it. It they can't fix it at the moment, it'l go to monitor 
state which is a state in Bug Life Cycle. Finally dev team 
try to fix it. If can't they'l raise CR.

CR is to change the functionality. Frequently v can't raise 
this. MR(modification Request) only possible to use in very 
first time. It means, here they'l change the codes of the 
suffered functionality.

Change Requests are used to document and track defects, 
enhancement requests and any other type of request for a 
change to the product. The benefit of CRs is that they 
provide a record of decisions and, due to their assessment 
process, ensure that change impacts are understood across 
the project.