Cohesive vs. Coupling

Attribute	Cohesive	Coupling
Definition	Refers to how closely related and focused the responsibilities of a module or component are	Refers to how dependent or interconnected modules or components are
Goal	To have high cohesion, meaning each module or component performs a single, well-defined task	To have low coupling, meaning modules or components are independent and changes in one do not heavily impact others
Impact of Changes	Changes are localized and do not affect other parts of the system	Changes can have ripple effects on other modules or components
Flexibility	High cohesion allows for easier maintenance and modifications	Low coupling allows for easier integration of new modules or components

Cohesive

Cohesion refers to the degree to which the elements inside a module belong together. In other words, cohesive modules have a strong relationship between the elements they contain. This means that the elements work together towards a common goal or purpose. Cohesion is essential for creating maintainable and understandable code. When modules are cohesive, it is easier to make changes to the code without affecting other parts of the system.

There are different types of cohesion, ranging from low to high. Low cohesion occurs when the elements inside a module are unrelated and do not work towards a common goal. This can lead to code that is difficult to understand and maintain. On the other hand, high cohesion means that the elements are closely related and work together towards a common goal. Modules with high cohesion are easier to understand and maintain.

• Strengthens the relationship between elements
• Improves maintainability and understandability
• Helps in making changes without affecting other parts of the system

Coupling

Coupling, on the other hand, refers to the degree of interdependence between modules. In other words, coupling measures how much one module relies on another module. Modules with high coupling are tightly interconnected, making it difficult to make changes to one module without affecting others. On the other hand, modules with low coupling are more independent and can be changed without impacting other parts of the system.

There are different types of coupling, ranging from low to high. Low coupling occurs when modules are independent and do not rely heavily on each other. This allows for greater flexibility and easier maintenance. On the other hand, high coupling means that modules are tightly interconnected and changes to one module can have a ripple effect on others. High coupling can lead to code that is difficult to maintain and understand.

• Measures interdependence between modules
• High coupling can lead to code that is difficult to maintain
• Low coupling allows for greater flexibility and easier maintenance

Comparison

When comparing cohesion and coupling, it is important to understand that they are related concepts but focus on different aspects of software design. Cohesion deals with how well the elements inside a module work together, while coupling deals with how modules interact with each other. Both cohesion and coupling play a crucial role in determining the quality of software.

High cohesion and low coupling are desirable attributes in software design. Modules with high cohesion are easier to understand and maintain, while modules with low coupling are more flexible and easier to change. When modules are both cohesive and loosely coupled, it is easier to make changes to the code without causing unintended side effects.

• Both cohesion and coupling are important in software design
• High cohesion and low coupling are desirable attributes
• Cohesion deals with how elements inside a module work together
• Coupling deals with how modules interact with each other

Conclusion

In conclusion, cohesion and coupling are essential concepts in software design. Cohesion measures how well the elements inside a module work together, while coupling measures how modules interact with each other. High cohesion and low coupling are desirable attributes that lead to maintainable and flexible code. By understanding and applying these concepts, software developers can create systems that are easier to understand, maintain, and change.