Method Waterfall

The traditional Waterfall software design and development method is based on the gradual and very detailed processing of all software components, each of which must be fully completed before the next can begin. Although the stages may overlap, the name Waterfall is based precisely on the principle of gradual implementation according to a precisely defined description in advance. Detailed analysis and precise processing of the system design is one of the main features of this methodology.

Design and development method

Extensive system project
Before the actual development, an extensive system project is created, often down to the prototype level, on which we verify that the designed system meets all functional and non-functional requirements.
User testing
The prototype, if implemented, will be tested on selected users (user testing) and any observations will be incorporated before the actual programming of the application logic.
The emergence of the system
The system is created exactly according to the project, the customer does not have to participate directly during development.
Handover
The finished system is usually delivered in stages or as a whole. There is always an acceptance process to ensure that the project specifications are met.

When to use the Waterfall model?

All system requirements are known in advance and there is no expectation of major changes during development or immediately after deployment. The customer prefers certainty of price and system launch date over the possibility of continuous feedback on the developed software.

Advantages and disadvantages waterfall methods

Advantages

The price and delivery date of the developed software are known in advance.
A detailed project is prepared in advance with a list of the functionality and features of the system.