Talking about Waterfall Model

The first waterfall model

What is a waterfall model? The waterfall model was proposed by Winston Royce in 1970. It separates the logical implementation from the physical implementation of the software, and separates the implementation of the function from the design. It defines six stages, planning-> requirements analysis-> system design-> coding-> testing-> running and maintenance. The software development process unfolds according to the six stages and progresses layer by layer, just like a waterfall. So it's called the waterfall model.

The waterfall model is actually the architecture of a project development, and the process of software development is carried out in the order defined by these columns. In the early stage of software engineering, the waterfall model makes people begin to look at the software development process from the perspective of engineering and engineering. (software has architecture, so does the process of software development.)

The advantages of the waterfall model: 1, the six stages of the software development process are clearly defined, and the software development team only needs to do the work at that stage step by step according to the defined stage.

2, sequencing, pipelined operations, completed stages, do not need to pay attention to

Disadvantages: 1, only applicable to the Prophase requirements are very clear and clear, and in the development process, the requirements will not change, encountered requirements unknown and frequent changes in the situation, using this model, the risk of project failure is very high.

2. Software products will not be presented to users until all the software has been developed. If the developed products do not meet the needs of users, the risk of failure is also very high.

3, software testing begins after the completion of software development, the cost of repairing defects found at this stage is very high, and software testing does not run through the project cycle.

Conclusion: at the beginning of the idea of software engineering, the waterfall model is undoubtedly a very good model for managing the software development process, but as the software becomes more and more complex, the requirements of users become faster and more demanding, and the time required for delivery becomes shorter, this model is undoubtedly unsatisfiable, and it is cumbersome and slow, so agile development mode is more popular at present. Rather than popular, this model is more in line with the current situation of software development, faster and better to meet the needs of users, but the waterfall model, as a classic development model, is also worth pondering carefully.