What are the guidelines for the division of modules in software design?

The criteria for module division in software design are: high cohesion and low coupling.

Cohesion is a measure of the connections within a module from a functional point of view, and a good cohesive module should do exactly one thing. It describes the functional connections within the module; Coupling is a measure of the interconnection between modules in a software structure, and the strength of coupling depends on the complexity of the interfaces between modules, the points at which a module is entered or accessed, and the data that passes through the interface.

The division of modules should follow certain requirements to ensure that the division of modules is reasonable, and to further ensure that the software system developed on this basis is reliable, easy to understand and maintain. The coupling between the modules should be as low as possible, and the cohesion of the modules should be as high as possible.

The criteria that should be followed in the division of modules in software design are high cohesion and low coupling, appropriate module size and scale, appropriate dependency of modules, etc., and the division of modules should follow certain requirements to ensure that the module division is reasonable, and further ensure the reliability of the software system developed on this basis. Easy to understand and maintain.

Advanced applications of computer level 2 MS

In the software design, the module division should follow the high cohesion and low coupling module size specification is appropriate, and the module specification division is appropriate. The module division should follow certain requirements to ensure that the module division is reasonable, and further ensure that the software system developed on this basis is reliable, easy to understand and maintain, the coupling between the modules should be as low as possible, and the cohesion of the modules should be as high as possible.

Hope it was helpful to you, thank you!

1. The criterion that should be followed in the division of modules in software design is high cohesion and low coupling.

Software design is based on the specification of software requirements, according to the function determined in the demand analysis stage to design the overall structure of the software system, divide the functional modules, determine the implementation algorithm of each module and write specific equipment, and form a specific design scheme of the software.

2. The criterion that should be followed in the division of modules in software design is high cohesion and low coupling.

The guidelines that should be followed for the division of modules include coupling and cohesion between modules. In general, the coupling between modules is required to be as low as possible, i.e., the modules are as independent as possible; The degree of cohesion of the modules is as high as possible, i.e., the principle of high cohesion and low coupling.

Software design is based on the specification of software requirements, according to the function determined in the demand analysis stage to design the overall structure of the software system, divide the functional modules, determine the implementation algorithm of each module and write specific equipment, and form a specific design scheme of the software.

The criteria for module division in software design are: high cohesion and low coupling.

Software design is based on the specification of software requirements, according to the functional design determined in the demand analysis stage, the overall structure of the software system, the division of functional modules, the determination of the implementation algorithm of each module and the preparation of specific **, the formation of the specific design scheme of the software.

Software design is the abstraction of many things and problems, and abstracting their different levels and perspectives. Decomposing and modularizing a problem or thing makes it easy to solve the problem, and the finer the decomposition, the more modules there are, which makes the designer consider more coupling between modules.

Software design is the process of forming a specific design scheme of software from the specification of software requirements, that is to say, on the basis of clarifying what the software is "doing quickly" in the requirements analysis stage, the problem of "how to do" the software is solved. The structural designer will divide the software design into two stages: outline design and detailed design.

The main task of the outline design is to decompose the functions of the software by analyzing the requirements specification and determine the overall structure of the software. In the detailed design stage, the algorithms and data structures required for each module's function are determined, and the logical structure of each module is designed.

The result of the work at the end of the software design phase is the software design specification, which describes the components of the software system, the invocation relationships between modules, and the inputs, outputs, and detailed process descriptions of each module.

Answer]: In structured program design, the division of modules should follow the principles of high cohesion, cultivation and low coupling. Among them, cohesion is a measure of the tightness of the various elements in a module, and coupling is a measure of the closeness of the interconnection between modules.

Answer]: cc [Analysis] According to the principle of software design, the following optimization criteria are proposed: When dividing the module, try to achieve high cohesion and low coupling, maintain the relative independence of the module, and optimize the initial software structure based on this principle.

A module's area of effect should be within its control, and the module it is located in should be as close as possible to the module being affected by its influence. The depth, width, fan-in, and fan-out of the software structure should be appropriate. The size of the module should be moderate.

c correct.

Answer]: According to the principle of software design, the following optimization criterion code skin is proposed: When dividing the module, try to achieve high cohesion and low coupling, maintain the relative independence of the module, and optimize the initial software structure based on this principle.

The scope of action of a module should be within its control, and the module in which it is judged to be located should be as close as possible to the module affected by the mold bench. The depth, width, fan-in, and fan-out of the software knot travel structure should be appropriate. The size of the module should be moderate.

c correct.