PyQdeck LogoPyQdeckSubjectsSyllabusBlog
Back to the 2026 paper

Module 3: Software Design & Metrics

20262m

Which combination generally represents desirable modular design?

(i) High coupling and low cohesion
(ii) Low coupling and high cohesion
(iii) High coupling and high cohesion
(iv) Low coupling and low cohesion

Search GoogleAsk AI
Worked SolutionAI Assisted

Solution

Correct Answer: (ii) Low coupling and high cohesion

Explanation

  • Cohesion = how strongly the elements inside one module are related. High is good.
  • Coupling = how dependent modules are on each other. Low is good.

A good modular design has high cohesion within modules and low coupling between modules, which makes software easier to understand, test, maintain and reuse.

Why other options are incorrect:

  • (i) High coupling, low cohesion - the worst combination.
  • (iii) High coupling, high cohesion - modules are focused but too dependent on each other.
  • (iv) Low coupling, low cohesion - independent modules, but each does unrelated things.

Answer: (ii) Low coupling and high cohesion

Similar questions

Software EngineeringWhich of the following is *not* a characteristic of good software design? (i) Low coupling (ii) High cohesion (iii) High complexity (iv) Modularity20252mSoftware EngineeringTo achieve a good design, modules should have (i) Weak cohesion Low coupling (ii) Weak cohesion High coupling (iii) Strong cohesion Low coupling (iv) Strong cohesion High coupling20242mSoftware EngineeringTo achieve a good design, modules should have a) Weak cohesion and low coupling b) Weak cohesion and high coupling c) Strong cohesion and low coupling d) Strong cohesion and high coupling20232mSoftware Engineering______ is a measure of the degree of interdependence between modules. (i) Cohesion (ii) Coupling (iii) None of the mentioned (iv) All of the mentioned20212m
PreviousWhich characteristic of an SRS indicates that every requirement has only one clear interpretation? (i) Complete (ii) Unambiguous (iii) Consistent (iv) ModifiableNextA DFD primarily represents (i) Program execution time (ii) Source-code complexity (iii) Class inheritance (iv) Flow and transformation of data
Budget AppAndroid App

Pocketly on Android

Log daily food, travel, and hostel expenses instantly. Set monthly spending limits and see where your money goes without complex spreadsheets.

Install Pocketly