Locating and eliminating dependencies

Sonar provides a widget to report on package and class dependencies. The following screenshot shows what Sonar reports on the commons-lang project. This is the entry point when you want to review highly coupled classes and locate dependencies that deteriorate the modularization of your packages.

Click on any number to navigate to Sonar's design matrix view. Alternatively, you can click on the Design link from the left menu.

Sonar reports 5 dependencies between packages and 10 between files. The design matrix lists all project packages on the left,. The right-hand side section is separated into two triangular regions. You will notice that all dependencies to be cut are located within the upper-right triangle. The circled area encloses all 5 package dependencies and the sum of the numbers equals to 10, which is the dependency between files. In Java, this means that there are ten imports spread in classes within five packages that should be cut in order...