Match List I with List II Software Design Principle. Definition (A) Cohesion…
2024
Match List I with List II
Software Design Principle. Definition
(A) Cohesion (I) Degree to which one module relies on another module.
(B) Coupling (II) Dividing a software system into distinct modules.
(C) Abstraction (III) Degree to which elements of a module belong together.
(D) Modularity (IV) Simplifying complex reality by modeling classes appropriate to the problem.
Choose the correct answer from the options given below:
- A.
(A)-(I), (B)-(II), (С)-(III), (D)-(IV)
- B.
(A)-(II), (B)-(III), (C)-(IV), (D)-(I)
- C.
(А)-(III), (B)-(I), (C)-(IV), (D)-(II)
- D.
(А)-(ІІІ), (B)-(IV), (C)-(II), (D)-(I)
Attempted by 200 students.
Show answer & explanation
Correct answer: C
Correct matching and brief explanations:
Cohesion → Degree to which elements of a module belong together. A highly cohesive module has closely related responsibilities.
Coupling → Degree to which one module relies on another. Lower coupling is desirable to reduce dependencies.
Abstraction → Simplifying complex reality by modeling classes appropriate to the problem; exposing only relevant details.
Modularity → Dividing a software system into distinct modules to manage complexity and enable reuse.
Therefore the correct mapping is: Cohesion → definition (degree elements belong together); Coupling → definition (degree of reliance); Abstraction → definition (simplifying/modeling); Modularity → definition (dividing into modules).
A video solution is available for this question — log in and enroll to watch it.