What is structured design for module partitioning from a technical point of view?

Structured design methodology is a methodology connected with structured analysis, which is used to derive the system module structure diagram from the system analysis data flow diagram, and to divide the modules with low coupling and high cohesion. The principles that should be followed for module division are:

(1) Top-down, layer-by-layer decomposition. The modules at the top level represent functions with higher levels of abstraction, and the modules at the bottom level have specific, single functions. The module structure design diagram can be derived from the data flow diagram according to certain rules.

(2) The singularity and independence of the module. When the module division of the accounting information system, each module must have an independent and single function. Since the modules are relatively independent of each other, each module can be understood, programmed, tested, debugged and modified separately.

For a module to solve a problem, it is not necessary to consider the problems of other modules outside the module. This reduces the chance of error and also facilitates the distribution of tasks during project development.

A complex problem must be composed of a number of slightly simpler problems. Modularization is the process of breaking down the overall goal of the program to be solved into sub-goals and further. Break it down into specific sub-goals, calling each sub-goal a module.

Limiting the use of the goto statement, the origins of the structured programming approach come from the recognition and debate over the GOTO statement. The affirmative conclusion was that GOTO statements were often needed at unusual exits from blocks and processes, and that using GOTO statements would make program execution more efficient.