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

Background:

Today, when I was reading the preface to "Code cleanliness" by Robert C.Martin (Uncle BOb), I accidentally saw "high cohesion, low coupling". After a tumult, I found that I was not very clear about what I had learned in my freshman year.

Content:

After consulting the information on the Internet, I finally understand its meaning:

High cohesion means that within a function or module, the closer the relationship between the components (methods or classes), the better, that is, all the components are directed towards the same goal.

Low coupling refers to the connection between the impassable functional modules, the less dependent the better, independent of each other.

In the words of Mr. Zhang, who was object-oriented at that time, it is: who does what he does.

Quoting netizens' explanation, I think it's right:

High cohesion and low coupling is a concept in software engineering and a standard to judge whether the design is good or not. It is mainly object-oriented design, which mainly depends on whether the cohesion of the class is high and whether the degree of coupling is low. Cohesion is the degree to which the elements in a module are combined with each other, and high cohesion is the high degree to which the elements in a module are combined with each other. The so-called high cohesion means that a software module is composed of highly related code and is responsible for only one task, which is often called the principle of single responsibility.

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.