Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What are the criteria for module division in software design?

2025-04-04 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/02 Report--

This article is to share with you what the guidelines for module division should follow in software design. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

The criterion of module division in software design is high cohesion and low coupling. Starting from the software requirement specification, the software design is to design the overall structure of the software system, divide the functional modules, determine the implementation algorithm of each module and write specific code according to the functional design determined in the requirement analysis stage. form the specific design scheme of the software.

This article operating environment: windows10 system, thinkpad T480 computer.

The criterion of module division in software design is high cohesion and low coupling.

The criteria for module division include coupling and cohesion between modules. Generally speaking, the coupling between modules is required to be as low as possible, that is, modules are as independent as possible; the degree of cohesion of modules is as high as possible, that is, the principle of high cohesion and low coupling.

Starting from the software requirement specification, the software design is to design the overall structure of the software system, divide the functional modules, determine the implementation algorithm of each module and write specific code according to the functional design determined in the requirement analysis stage. form the specific design scheme of the software.

Software design is to abstract many things and problems, and abstract their different levels and angles. Decomposing and modularizing a problem or thing makes it easier to solve the problem, and the more modules are decomposed, the more modules are decomposed. Its side effect is that it makes designers consider more coupling between modules.

Thank you for reading! This is the end of this article on "what are the guidelines for module division in software design?". I hope the above content can be of some help to you, so that you can learn more knowledge. If you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report