The degree of interconnectedness between modules is described by _.

The Design phase in the Software Development Life Cycle plays a pivotal role in creating a solution for the problems outlined in the Software Requirement Specification (SRS) document. Its primary output is the Software Design Document (SDD). To measure the quality of a software system’s design, two key concepts, coupling and cohesion, are essential. In this comprehensive guide, we will delve into the degree of interconnectedness between modules, as described by coupling and cohesion.

Coupling: Interdependence Between Modules

Coupling refers to the degree of interdependence between software modules. High coupling signifies that modules are closely connected, and changes in one module may have a significant impact on other modules. In contrast, low coupling means that modules are independent, and changes in one module have minimal influence on other modules.

Types of Coupling:

Data Coupling: Modules communicate by passing data. Changes in one module don’t affect the others. An example is a customer billing system.
Stamp Coupling: The complete data structure is passed from one module to another. This may involve tramp data and is chosen for efficiency.
Control Coupling: Modules communicate by passing control information, which can be either good or bad based on the context.
External Coupling: Modules depend on other modules external to the software, like protocols or device formats.
Common Coupling: Modules share global data structures, making changes in global data impact multiple modules.
Content Coupling: One module can modify the data of another module or pass control flow, which is undesirable.
Temporal Coupling: Modules depend on the timing or order of events, which can result in design issues.
Sequential Coupling: The output of one module serves as the input for another, creating a chain of dependencies, which can be challenging to maintain.
Communicational Coupling: Modules share a common communication mechanism, which can lead to performance issues.
Functional Coupling: Modules depend on each other’s functionality, resulting in tightly-coupled code.
Data-Structured Coupling: Modules share a common data structure, which can lead to data integrity issues.
Interaction Coupling: Methods of a class invoke methods of other classes, with the worst form being direct access to internal parts.
Component Coupling: Classes have variables or methods with parameters of another class, creating interaction coupling.

Cohesion: Functional Relatedness Within a Module

Cohesion measures the degree to which elements within a module are functionally related. High cohesion means that all elements within a module work together to fulfill a single, well-defined purpose.

Types of Cohesion:

Functional Cohesion: Every essential element for a single computation is contained in the component.
Sequential Cohesion: Elements exchange data, naturally occurring in functional programming languages.
Communicational Cohesion: Elements operate on the same input or contribute to the same output data.
Procedural Cohesion: Elements ensure the order of execution but may not be reusable.
Temporal Cohesion: Elements are related by timing involved, with all tasks executed in the same time span.
Logical Cohhesion: Elements are logically related but not functional.
Coincidental Cohesion: Elements are unrelated, the worst form of cohesion.
Procedural Cohesion (again): Elements or tasks are grouped based on their sequence of execution, common in structured programming languages.
Communicational Cohesion (again): Elements or tasks are grouped based on their interactions with each other, found in object-oriented programming.
Temporal Cohesion (again): Elements or tasks are grouped based on their timing, common in real-time and embedded systems.
Informational Cohesion: Elements or tasks are grouped based on their relationship to specific data structures or objects, common in object-oriented programming.
Functional Cohesion (again): All elements contribute to a single well-defined function or purpose.
Layer Cohesion: Elements are grouped based on their level of abstraction or responsibility.

Advantages of Low Coupling:

Improved maintainability.
Enhanced modularity.
Better scalability.

Advantages of High Cohesion:

Improved readability and understandability.
Better error isolation.
Improved reliability.

Disadvantages of High Coupling:

Increased complexity.
Reduced flexibility.
Decreased modularity.

Disadvantages of Low Cohesion:

Increased code duplication.
Reduced functionality.
Difficulty in understanding the module.

Conclusion

In the world of software design, understanding the concepts of coupling and cohesion is crucial. High coupling and low cohesion can lead to challenging software systems, making them difficult to change and test. Conversely, low coupling and high cohesion make a system more maintainable and scalable. Recognizing the different types of coupling and cohesion and their advantages and disadvantages is vital for creating well-designed, efficient software systems.

Whether you’re a budding software engineer or a seasoned developer, the significance of coupling and cohesion cannot be overstated. These concepts are fundamental in ensuring the quality and robustness of your software. So, embrace them, apply them, and elevate your software design skills to new heights.