The type of complexity of software complexity

Software complexity refers to the degree of difficulty in understanding and dealing with software, including program complexity and document complexity.

In the reliability design of hardware, there is a basic principle that "simple is reliable". The same principle applies to software, where the addition or enhancement of features is accompanied by constant upgrades and patches. There are several ways to measure software complexity, but MCCABE QA is a great and useful way to calculate multiple software complexities that can be examined, analyzed, and pinpointed for errors that can lead to errors.

In the 70s, software systems had become extremely complex, and both development and maintenance were costly tasks. There is a realization that software must be modularized for easy development, testing, and maintenance. To this end, McCabe & Associates, founded in 1976, has developed the McCabe Cyclomatic Complexity Metric technology for structural testing of software.

Metric is based on the number of software complexity measurements that help engineers identify modules that are difficult to test and maintain, and cyclomatic complexity has become an important criterion for evaluating software quality. One can use cyclomatic complexity to measure the complexity and quality of the software to schedule the project, finding a balance between cost, schedule, and performance.

Describe software complexity in six ways:

the difficulty of understanding the procedure; the difficulty of correcting errors and maintaining procedures; the difficulty of explaining the procedure to others; the difficulty of modifying the program in a specified way; the amount of work required to write a program based on the design documentation; The extent to which resources are required to execute the program.

Basic principles that should be followed in a software complexity measurement model:

1) The relationship between software complexity and program size is not linear; (2) The control structure is complex, and the program is more complex; (3) The program with complex data structure is more complex; (4) the procedure for improper use of steering statements is more complicated; (5) The cyclic structure is more complex than the selection structure, and the selection structure is more complex than the sequential structure. (6) the order of statements, data, subroutines and modules in the program has an impact on the complexity of the software; (7) When there are many variables and non-local variables, the procedure is more complicated; (8) Parameter delivery by address is more complex than value delivery; (9) Functions are more difficult to figure out than explicit parameter transfers; (10) Variables with different roles are difficult to understand when they share the same name; (11) The procedures that are closely related between modules or processes are more complex; (12) The deeper the nesting depth, the more complex the program.

Among the two most typical methods of measuring program complexity, the MCCABE loop complexity measurement is a measurement model formulated for basic principle (2). The Halstead metric is a metric model developed for the frequency of operators and operands in a program.

1What are the types of software complexity? What are the basic principles that should be followed in a software complexity measurement model?

Answer: Describe the complexity of the software in six aspects: the difficulty of understanding the program;

the difficulty of correcting errors and maintaining procedures; the difficulty of explaining the procedure to others; the difficulty of modifying the program in a specified way; the amount of work required to write a program based on the design documentation; The extent to which resources are required to execute the program.

Basic principles that should be followed in a software complexity measurement model:

The relationship between software complexity and program size is not linear; The control structure is complex, and the program is more complex; Programs with complex data structures are more complex; Procedures for improper use of steering statements are more complex;

The cyclic structure is more complex than the selection structure, and the selection structure is more complex than the sequential structure.

The order of statements, data, subroutines, and modules in a program all have an impact on software complexity; When there are many variables and non-local variables, the procedure is more complicated; Passing parameters by address is more complex than passing by value; Functions are more difficult to figure out than explicit parameter passing;

Variables with different roles are more difficult to understand when they share the same name; Procedures that are closely related between modules or processes are more complex; The deeper the nesting depth, the more complex the program becomes.

Complexity: The total length of different DNA sequences in a given sample. Complexity (cpx):

The complexity of a thing can be measured by the length of the computer language required to describe it.