Describe the criticism of traditional waterfall SDLC process

What will be an ideal response?

There are several criticisms of the traditional life-cycle approach to systems development. One relates to the way the life cycle is organized. Note how the flow of the project begins in the planning phase and from there runs "downhill" to each subsequent phase, just like a stream that runs off a cliff. It became too tempting to ignore the need for feedback and to treat each phase as complete unto itself, never to be revisited once finished. Another criticism of the traditional waterfall SDLC is that the role of system users or customers was narrowly defined. User roles were often relegated to the requirements determination or analysis phases of the project, where it was assumed that all of the requirements could be specified in advance. Such an assumption, coupled with limited user involvement, reinforced the tendency of the waterfall model to lock in requirements too early, even after business conditions had changed.