What is a central problem associated with the waterfall software development model?

What is a central problem associated with the waterfall software development model?

• A. It does not allow iterative design with user feedback
• B. It does not allow for changes in requirements that occur during development
• C. It does not consider software designers' work practices
• D. It does not allow for iterative design with user feedback and cannot accommodate changing requirements

Answer: (C)

The central idea here is that the waterfall model is highly rigid because it follows a strict, linear sequence of phases: requirements, design, implementation, testing, and maintenance. Once a phase is completed, there’s little opportunity to revisit earlier work. This means user or stakeholder feedback isn’t incorporated iteratively, and changes to requirements discovered after the project has started are hard to accommodate without upending completed work. The model assumes requirements are known up front and remain stable, which is rarely the case in real projects. Because of this, the most complete description of the main problem is that it does not allow iterative design with user feedback and cannot accommodate changing requirements. One option mentions only the lack of iterative feedback, another mentions only changing requirements, but neither fully captures both limitations. The choice focusing on designers’ work practices misses the core issue of how the process handles requirements and feedback rather than how designers work.

The central idea here is that the waterfall model is highly rigid because it follows a strict, linear sequence of phases: requirements, design, implementation, testing, and maintenance. Once a phase is completed, there’s little opportunity to revisit earlier work. This means user or stakeholder feedback isn’t incorporated iteratively, and changes to requirements discovered after the project has started are hard to accommodate without upending completed work. The model assumes requirements are known up front and remain stable, which is rarely the case in real projects.

Because of this, the most complete description of the main problem is that it does not allow iterative design with user feedback and cannot accommodate changing requirements. One option mentions only the lack of iterative feedback, another mentions only changing requirements, but neither fully captures both limitations. The choice focusing on designers’ work practices misses the core issue of how the process handles requirements and feedback rather than how designers work.