Question

what is a downside of using the traditional waterfall approach ​

Answer 1

Answer:

The disadvantage of waterfall development is that it does not allow much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-documented or thought upon in the concept stage.

Answer 2

Answer:

There is not a lot of time for contemplation or modification in the waterfall method. There is little room for reflection or correction because the client cannot perceive progress until a step is finished. This can be a problem if you're seeking for something specific and there's no room for modifications.

Explanation :

• A traditional model used in the system development life cycle to design a system with a linear and sequential approach is the waterfall model.
• Also we can say that because the model progresses methodically from one phase to the next in a downward direction, it is known as a waterfall model.
• The output of one phase is utilised as the input for the following phase in this model, which is broken up into several phases.
• There is no overlap between phases; each must be finished before the next one begins.
• The successive phases that propel the team forward are what drive the Waterfall model.
• The old method nearly never allows for adjustments once each phase is finished.
• Only during the stage's processing are changes feasible.
• Since project testing takes a long time to complete, major adjustments may result in significant delays.
• There is very little emphasis placed on the end client's engagement in the process.
• This strategy carries a significant degree of risk and unpredictability.
• It is inappropriate for complicated projects.
• It does not correct the error; it merely notices it.
• Its lack of thorough documentation causes misconceptions and problems among the team members.
• If updates are added to the development process beyond the planning stage, it may result in higher prices and longer lead times.
• Due to the ambiguity and uncertainty of many project aspects, they provide more flexibility but also yield less predictable results.
• In general, waterfall projects are more expensive and take longer to complete.
• They are less adaptable as well. It doesn't perform well in an environment where you might need to make a lot of assumptions in an effort to address the uncertainty; frequently, those assumptions will be incorrect and necessitate more re-planning and possible rework.
• It is highly unclear and risky. Not suggested for difficult, object-oriented designs.
• No phase can be modified to fit shifting requirements. because testing is done later.
• Therefore, it's possible that dangers and obstacles from previous phases would go unnoticed.

#SPJ2