Question 3The goal in low coupling is to ensure that changes don't cross the boundaries of modules.1 pointFalseTrue

The statement about low coupling emphasizes the importance of module boundaries in software design. Low coupling refers to a design principle in which individual modules or components in a system are independent of one another. This allows for changes in one module to have minimal or no impact on other modules.

1. Explanation of Low Coupling: When modules are loosely coupled, they can be modified or replaced with little to no influence on other modules. This is beneficial for maintainability, scalability, and reusability.

2. Impact of Changes: Low coupling ensures that changes within one module do not 'cross over' to other modules, thus reducing the risk of unintended side effects and enhancing the overall coherence of the system.

Given the options, the correct answer to whether the goal in low coupling is to ensure that changes don't cross the boundaries of modules is:

Final Answer

True