This guy knew what he was talking about.

Why the hell do something about dependency mgmt?

• be able to replace components with minimal effort
• better quality (dependencies result in bugs)
• enable faster change  of the product

Tools can help:

• textual/graphical analysis tools don't really help (not usable)
• what does work: DSM (Dependency structure matrix).
• The DSM tool in IntelliJ IDEA looked impressive : scales well, looks good

How to organize DM:

-> Define the rules and make sure everybody sticks with them !

What can you do about them once you know you have them:

• move code
• extract interfaces/superclasses
• copy (may be ugly)
• pull members up
• introduce parameters
• replace constructors with factory methods
• Service locator design pattern
• Use inversion of control
• Dependency injection

I have my concerns about these last 2: you still have the dependencies, but instead of having them at compile time (in code) you have them at runtime (eg in xml when using Spring)