The most widely used software engineering methodologies are traditional methodologies and object-oriented methodologies. The traditional methodology is not only traditional but also not suitable for the contemporary place, then whether it has the application value in the present age?
Traditional methodologies are also known as life-cycle methodologies or structured generics. It uses structured technology (structured analysis, structured design, and structured implementation) to accomplish the tasks of software development and to support the use of structured technology using the appropriate software tools or the engineering environment. This method divides the whole process of the software life cycle into several stages, and then completes the tasks of each stage in sequence. Usually the completion of the previous phase of the task is a prerequisite and basis for the beginning of the latter phase of the work. The traditional methodology emphasizes the completion of the various stages of software development from top-down order.
Traditional methodology, though traditional, has its own advantages. It divides the software life cycle into several stages, each phase of the task is relatively independent, and relatively simple, convenient for different people to work together, thereby reducing the overall software development engineering difficulties; This top-down approach also ensures the quality of the software, especially the maintainability of the software. Greatly improve the success rate of software development, software development productivity can also be significantly improved.
So the traditional software engineering methodology still has its practicability, and it is still a very extensive software engineering methodology used by people in the development of softwares. I think a long time later will also apply, will not be eliminated.
Whether the traditional software engineering methodology still has use value in the present age