When many other components depend on a given component, what design quality does that imply?

When many other components depend on a given component, what design quality does that imply?

• A. It is highly volatile
• B. It is widely reused and stable
• C. It has high external dependencies
• D. It cannot be easily tested

Answer: (B)

When many other components rely on a given component, it signals that the component is designed to be widely reusable and stable. A stable interface is essential because changes to a frequently depended-upon component would ripple through all dependents, causing widespread breakage. So such a component is typically a foundational utility or service with a clear contract, well-documented behavior, and minimal tendency to change. This explains why it’s not described as highly volatile—that would imply frequent interface changes that would disrupt many others. It’s not about having many external dependencies on its own; rather, it’s about the component being dependable for others to build on. And while testing is important for any component, the key idea here is the emphasis on broad reuse and stability.

When many other components rely on a given component, it signals that the component is designed to be widely reusable and stable. A stable interface is essential because changes to a frequently depended-upon component would ripple through all dependents, causing widespread breakage. So such a component is typically a foundational utility or service with a clear contract, well-documented behavior, and minimal tendency to change.

This explains why it’s not described as highly volatile—that would imply frequent interface changes that would disrupt many others. It’s not about having many external dependencies on its own; rather, it’s about the component being dependable for others to build on. And while testing is important for any component, the key idea here is the emphasis on broad reuse and stability.