单选题
Ravi, like many project {{U}} {{U}} 71
{{/U}} {{/U}}, had studied the waterfall model of software development as the
primary software life-cycle {{U}} {{U}} 72 {{/U}} {{/U}}. 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 {{U}} {{U}} 73 {{/U}} {{/U}}and not as
{{U}} {{U}} 74 {{/U}} {{/U}}. 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
{{U}} {{U}} 75 {{/U}} {{/U}}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.