{"id":386,"date":"2023-08-13T10:20:28","date_gmt":"2023-08-13T16:20:28","guid":{"rendered":"https:\/\/kop.lat\/blog\/?p=386"},"modified":"2023-08-13T10:20:28","modified_gmt":"2023-08-13T16:20:28","slug":"low-coupling-and-high-cohesion","status":"publish","type":"post","link":"https:\/\/kop.lat\/blog\/low-coupling-and-high-cohesion\/","title":{"rendered":"“low coupling” and “high cohesion”"},"content":{"rendered":"\n

Low Coupling:
<\/strong>
Imagine you have two friends, Alice and Bob. Both<\/strong> love to<\/strong> play<\/strong> video games. Now<\/strong> Alice decides to buy a new game<\/strong> console<\/strong> and Bob wants to play games<\/strong> with<\/strong> her.<\/strong> They connect their consoles with<\/strong> a special cable. But here’s the problem<\/strong> –<\/strong> instead of a regular cable, they use a fancy cable that has all sorts of different connectors and leads.<\/strong> This sophisticated<\/strong> cable can be used to<\/strong> play<\/strong> games,<\/strong> watch<\/strong> movies, connect<\/strong> to the internet<\/strong> and even charge<\/strong> their devices.

In this analogy, fancy cables<\/strong> represent<\/strong> high coupling. High coupling means two parts of a system “like<\/strong> Alice’s console and Bob’s console”;<\/strong> interwoven<\/strong> and interdependent<\/strong> in complex ways. If something goes wrong with one part, it can affect another,<\/strong> and changing one part can<\/strong> drag<\/strong> on<\/strong> another.<\/strong>

Now, imagine Alice and Bob deciding<\/strong> to buy<\/strong> simpler cables designed specifically for gaming. These cables have<\/strong> only the connectors and wires needed<\/strong> to<\/strong> play<\/strong> the<\/strong> game.<\/strong> This is a<\/strong> weak<\/strong> coupling. Loose<\/strong> coupling means that different parts of the<\/strong> system are simply<\/strong> and purposefully<\/strong> connected.<\/strong> If one part changes, it<\/strong> is<\/strong> less likely to interrupt<\/strong> or request<\/strong> changes in the other.<\/strong>

High<\/strong> cohesion:<\/strong>

Stick<\/strong> with our game<\/strong> theme. Imagine you<\/strong> are<\/strong> building a video game<\/strong> and a team of developers are<\/strong> working on it. Each developer has a specific role:
one person designs the characters, another works on the levels<\/strong> and the<\/strong> third does<\/strong> the sound effects.

The<\/strong> high<\/strong> cohesion in this scenario means that each developer is focusing on their own specific task and doing it very<\/strong> well. The character designer does<\/strong> not<\/strong> attempt<\/strong> to create sound effects, and the level designer does<\/strong> not<\/strong> interfere<\/strong> with the<\/strong> character design.<\/strong> People<\/strong> work<\/strong> on what they<\/strong> do<\/strong> best,<\/strong> and their work is clearly<\/strong> organized<\/strong> and divided.<\/strong> On the other hand, imagine if every<\/strong> developer tried<\/strong> to do everything<\/strong> a little<\/strong> bit.<\/strong> The character designer also tries<\/strong> to create the<\/strong> sound effects, the level designer provides<\/strong> input on the<\/strong> character design, and there’s a lot of mixing and matching of quests.<\/strong>

Strong<\/strong> cohesion is like having a team where everyone understands<\/strong> their role and stays focused on their expertise. This<\/strong> means different parts of the<\/strong> system “like<\/strong> the game’s<\/strong> characters, levels<\/strong> and sound effects”;<\/strong> well<\/strong> organized<\/strong> and closely related to their particular<\/strong> purpose.

In a software context, loose<\/strong> coupling and high coherence<\/strong> are design principles that help create systems that are easier to understand, maintain, and update. In C# .NET programming, applying these principles means designing your code so that different components (like classes and modules) are loosely coupled<\/strong> (low coupling) and each component is<\/strong> loosely<\/strong> coupled.<\/strong> section<\/strong> with<\/strong> a clear and specific purpose (high coherence).<\/strong> This makes your code more flexible, easier to debug, and easier<\/strong> to modify<\/strong> in the future.\u00a0<\/p>\n\n\n\n

<\/p>\n\n\n\n

Conceptually<\/strong><\/p>\n\n\n\n


In software design, “low coupling” and “high cohesion” are two principles that aim to create well-structured and maintainable code. These principles are particularly relevant in object-oriented programming languages like C# in the context of designing classes and components. Let’s dive into each concept:<\/p>\n\n\n\n

    \n
  1. Low Coupling: Coupling refers to the degree of interdependence between different modules or components in a software system. Low coupling implies that modules are relatively independent and have minimal knowledge of each other’s internal details. This makes the system more flexible, easier to maintain, and less prone to ripple effects when changes are made to one module.<\/li>\n<\/ol>\n\n\n\n

    In C#\/.NET, low coupling can be achieved by:<\/p>\n\n\n\n

      \n
    • Using well-defined interfaces: Components should interact with each other through well-defined interfaces rather than relying on specific implementation details.<\/li>\n\n\n\n
    • Minimizing direct dependencies: Avoid directly referencing classes or components from other modules. Instead, use abstractions like interfaces or abstract classes to establish communication.<\/li>\n\n\n\n
    • Using dependency injection: Rather than creating dependencies within a class, inject the required dependencies from the outside. This reduces the class’s coupling with its dependencies.<\/li>\n<\/ul>\n\n\n\n
        \n
      1. High Cohesion: Cohesion refers to the degree to which the responsibilities and functionality within a module or class are related and focused. High cohesion indicates that a module or class has a clear and well-defined purpose, and its internal components work together to achieve that purpose. This leads to more readable, maintainable, and reusable code.<\/li>\n<\/ol>\n\n\n\n

        In C#\/.NET, high cohesion can be achieved by:<\/p>\n\n\n\n

          \n
        • Following the Single Responsibility Principle (SRP): Each class or module should have a single, well-defined responsibility. This ensures that the class’s functionality remains focused and easier to understand.<\/li>\n\n\n\n
        • Grouping related methods and data: Place methods and data that are closely related within the same class. This reduces the need to jump between different classes to understand the complete behavior.<\/li>\n\n\n\n
        • Avoiding “God classes”: A “God class” is a class that tries to do too much, leading to low cohesion. Splitting such a class into smaller, more focused classes increases cohesion.<\/li>\n<\/ul>\n\n\n\n

          To sum up, low coupling and high cohesion work together to create maintainable, flexible, and understandable software systems. Low coupling reduces the interdependencies between modules, while high cohesion ensures that each module is focused and well-organized. Following these principles helps developers create more robust and maintainable C#\/.NET applications.<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          <\/p>\n\n\n\n

          <\/p>\n","protected":false},"excerpt":{"rendered":"

          Low Coupling:Imagine you have two friends, Alice and Bob. Both love to play video games. Now Alice decides to buy a new game console and Bob wants to play games with her. They connect their consoles with a special cable. But here’s the problem – instead of a regular cable, they use a fancy cable […]<\/p>\n","protected":false},"author":1,"featured_media":224,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[36,41,1,32,12,7],"tags":[],"_links":{"self":[{"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/posts\/386"}],"collection":[{"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/comments?post=386"}],"version-history":[{"count":1,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/posts\/386\/revisions"}],"predecessor-version":[{"id":387,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/posts\/386\/revisions\/387"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/media\/224"}],"wp:attachment":[{"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/media?parent=386"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/categories?post=386"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kop.lat\/blog\/wp-json\/wp\/v2\/tags?post=386"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}