In bad software design, which term describes a system where every change affects many other parts?

In bad software design, which term describes a system where every change affects many other parts?

• A. Changes are isolated and do not affect other parts
• B. The system becomes easier to modify over time
• C. Every change affects many other parts of the system
• D. Code is always perfectly modular

Answer: (C)

High coupling is being tested here. When parts of a system are tightly connected, a change in one area often forces edits in many other areas, creating a ripple effect that makes the code fragile and hard to maintain. The idea is to keep modules loosely related so a modification stays localized, which is the goal of good design. Hence, describing a system where every change affects many other parts accurately captures the problem of high coupling and poor modularity. The other statements describe ideal, well-modulated design where changes remain isolated, the system is easier to modify, and code is modular.

High coupling is being tested here. When parts of a system are tightly connected, a change in one area often forces edits in many other areas, creating a ripple effect that makes the code fragile and hard to maintain. The idea is to keep modules loosely related so a modification stays localized, which is the goal of good design. Hence, describing a system where every change affects many other parts accurately captures the problem of high coupling and poor modularity. The other statements describe ideal, well-modulated design where changes remain isolated, the system is easier to modify, and code is modular.