Briefly describe the characteristics of traditional and object-oriented methods

The characteristics of traditional and object-oriented approaches are as follows:

I. Characteristics of Traditional Approach:

The traditional approach is also known as life-cycle approach or structured paradigm. It uses structured techniques to accomplish various tasks of software development. This methodology divides the entire process of the software life cycle into a number of phases in sequence, and then sequentially and progressively completes the tasks of each phase.

There are strict criteria for the beginning and end of each phase, and for any two neighboring phases, the end criteria of the previous phase is the beginning criteria of the next phase.

The main disadvantage of the traditional approach is that it is not flexible enough to adapt to changes in requirements; in addition, the structured approach is either behavioral or data oriented, and lacks a mechanism to organically combine the two.

Second, the characteristics of the object-oriented approach:

Object-oriented approach to the data and behavior as equally important, the data and the operation of the data is closely integrated approach, which is the object-oriented approach and the traditional approach to the important difference.

The starting point and basic principle of the object-oriented approach is to try to simulate the habitual way of thinking of human beings, so that the method and process of developing software is as close as possible to the human understanding of the problem and problem-solving methods and processes, so as to make the problem space describing the problem as much as possible consistent with its solution space in the structure. For large, complex and interactive systems, the use of object-oriented approach is more advantageous.

Object-Oriented Programming Deficiencies:

1. Lower operational efficiency.

Large loading of classes sacrifices system performance and reduces operational speed. Although the CPU speed is improving, memory capacity is increasing, but this problem will still gradually show up as the system becomes larger and more serious.

2. Huge class libraries.

Since the class libraries are too large, programmers need a period of time to master them, from the point of view of popularization and promotion, the class libraries should be based on ensuring that their functionality is complete on the basis of the corresponding reduction.

3, class library reliability.

The more massive the system will be the existence of unpredictable problems, programmers can not guarantee that each class in the library in a variety of environments 100% correct, when the use of the class problem will affect the follow-up work, the programmer may also be overthrown all the original work.