PyQdeck LogoPyQdeckSubjectsSyllabusBlog
Back to the 2023 paper

Module 3: Software Design & Metrics

20232m

To 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 coupling

Search GoogleAsk AI
Worked SolutionAI Assisted

Solution

Correct Answer: (c) Strong cohesion and low coupling

Explanation

Good modular design principle: High cohesion, Low coupling.

  • Strong (high) cohesion - elements inside module belong together → maintainable
  • Low coupling - modules independent → change in one doesn't affect others

Weak cohesion or high coupling are bad (hard to test, ripple errors).

Answer: (c) Strong cohesion and low coupling

Similar questions

Software 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 EngineeringWhich 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 cohesion20262mSoftware EngineeringDefine coupling and cohesion in module design. Why is low coupling and high cohesion preferred?20257mSoftware EngineeringWhich of the following is *not* a characteristic of good software design? (i) Low coupling (ii) High cohesion (iii) High complexity (iv) Modularity20252m
NextWhich is NOT a non-functional requirement? a) Efficiency b) Reliability c) Product features d) Stability
AI LearningWeb Platform

Coursify — Personal AI Course Generator

Struggling with a difficult subject or concept? Turn any engineering topic into a structured course with interactive lessons, quizzes, and research-backed explanations.

Try Coursify Free