Ravi, like many project （1） , had studied the waterfall model of software development as the primary software life-cycle （2）. He was all set to use it for an upcoming project, his first assignment. However, Ravi found that the waterfall model could not be used because the customer wanted the software delivered in stages, something that implied that the system had to be delivered and built in （3） and not as （4）.
The situation in many other projects is not very different. The real world rarely presents a problem in which a standard process, or the process used in a previous project, is the best choice. To be the most suitable, an existing process must be （5） to the new problem.
A development process, even after tailoring, generally cannot handle change requests. To accommodate change requests without losing control of the project, you must supplement the development process with a requirement change management process.
（1） A. customers
B. managers 
C. users  
D. administrators
（2）A. activity   
B. procedure 
C. process   
D. progress
（3） A. parts 
B. modules  
C. software  
D. a whole
（4） A. parts
B. modules  
C. software  
D. a whole
（5） A. modified 
B. used 
C. suited
D. tailored