Final answer:
We avoid acyclic dependencies to prevent circular dependencies, which can complicate code readability and maintainability. Acyclic dependencies impact the structure and the inter-module interactions, aiming to improve the ease of understanding and extending the software.
Step-by-step explanation:
We want to avoid acyclic dependencies in software development to minimize the risk of circular dependencies. Circular dependencies occur when two or more modules rely on each other directly or indirectly, resulting in a closed loop. This situation can lead to various problems, including difficulties in code readability and maintainability, increased complexity in error detection, and potentially creating problems in build processes such as compilation or automated testing.
While Option 1 and Option 3 present issues that could arise in software systems, they are not directly related to acyclic dependencies. Acyclic dependencies are fundamentally about the structure of the codebase and how different parts of the system interact with one another. Avoiding circular dependencies, which are a consequence of improper handling of acyclic dependencies, is crucial in ensuring that software can be easily understood, maintained, and extended by developers.