UGC NET CSE | December 2004 | Part 2 | Question: 41

Question

The main objective of designing various modules of a software system is :

• A. To decrease the cohesion and to increase the coupling

• B. To increase the cohesion and to decrease the coupling

• C. To increase the coupling only

• D. To increase the cohesion only

Answer 1

(B) is correct.

Coupling is quantitative measure of to what extent, the modules are dependent on each other

Cohesion is quantitative measure of to what extent the modules are independent of each other

An efficient  modular project has low coupling and high cohesion.​​​

Answer 2

In software engineering, coupling is the degree of interdependence between software modules; a measure of how closely connected two routines or modules are; the strength of the relationships between modules

Coupling is usually contrasted with cohesion. low coupling often correlates with high cohesion, and vice versa. Low coupling is often a sign of a well-structured computer system  and a good design, and when combined with high cohesion, supports the general goals of high readability and maintainability

• Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.So in the context of modular software design there should be high cohesion and low coupling.

https://en.wikipedia.org/wiki/Coupling_(computer_programming)#:~:text=In%20software%20engineering%2C%20coupling%20is,high%20cohesion%2C%20and%20vice%20versa.

Answer 3

B. To increase the cohesion and to decrease the coupling ...

 

Cohesion refers to the degree to which the elements inside a module belong together…

In one sense, it is a measure of the strength of relationship between the methods and data of a class and some unifying purpose or concept served by that class...

 

1. https://en.wikipedia.org/wiki/Cohesion_(computer_science)

 

Answer 4

The correct answer is:

To increase the cohesion and to decrease the coupling

Explanation:

• Cohesion refers to how closely related the responsibilities of a module are. High cohesion means that a module performs a single task or a group of related tasks.
• Coupling refers to how much one module depends on another. Low coupling means that modules are more independent and changes in one module are less likely to affect other modules.

The goal of good software design is to have high cohesion (modules should focus on a single responsibility) and low coupling (modules should minimize dependencies on each other), leading to a more maintainable, flexible, and scalable system.