adplus-dvertising
frame-decoration

Question

What is the main benefit of having simple interfaces with weak coupling between modules and strong cohesion between a module's elements?

a.

Communication between programmers becomes more complex.

b.

Correctness proofs become harder to derive.

c.

It is more likely that changes will propagate to other modules, increasing maintenance costs.

d.

It increases the comprehensibility of modules.

Posted under Software Engineering

Answer: (d).It increases the comprehensibility of modules. Explanation:Simple module interfaces allow for an understanding of a module independent of the context in which it is used, which increases the comprehensibility of modules.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the main benefit of having simple interfaces with weak coupling between modules and strong cohesion between a module's elements?

Similar Questions

Discover Related MCQs

Q. What is the relationship between strong internal cohesion and intermodule coupling?

Q. What is one of the reasons for simple interfaces being important?

Q. What is the principle of information hiding according to David Parnas?

Q. How is information hiding related to cohesion and coupling in design?

Q. How does information hiding affect the maintainability of software according to Boehm (1983)?

Q. What is the relationship between information hiding, abstraction, cohesion, and coupling?

Q. Does the separation of concerns obtained during the design stage depend on the programming language used?

Q. What is the complexity of a problem in a general sense?

Q. What is the complexity of software in the Software development context?

Q. What are the internal attributes of software complexity?

Q. What is the difference between the complexity of a problem and the complexity of the computation performed?

Q. What are the two classes of software attributes considered in measuring software complexity?

Q. What is the purpose of measuring software complexity in quantitative terms?

Q. What is a size-based complexity metric?

Q. What is a structure-based complexity metric?

Q. What is the easiest way to measure software size?

Q. What is the ideal size of a module according to (Weinberg, 1971)?

Q. Why is a module suggested to contain at most 7 elements?

Q. What is the main problem associated with using the number of lines of code as a complexity metric?

Q. What does Halstead's method, also known as 'software science', use to overcome the problems associated with metrics based on a direct count of lines of code?