Metric Results

[ summary] [ packages] [ cycles] [ explanations]

The following document contains the results of a JDependmetric analysis. The various metrics are defined at the bottom of this document.

Summary

[ summary] [ packages] [ cycles] [ explanations]

Package TC AC CC AC EC A I D
hoplugins 10123060%40%
hoplugins.commons.ui 9090110100%0%
hoplugins.commons.ui.info.clearthought.layout 413050.25100%25%
hoplugins.commons.ui.renderer 202040100%0%
hoplugins.commons.ui.sorter 918170.1188%1%
hoplugins.commons.utils 90916086%14%
hoplugins.commons.vo 101010100%0%

Packages

[ summary] [ packages] [ cycles] [ explanations]

hoplugins

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
230%60%40%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

hoplugins.commons.ui.info.clearthought.layout

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0525%100%25%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

hoplugins.commons.ui.renderer

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
040%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

hoplugins.commons.ui.sorter

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1711%88%1%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

hoplugins.commons.utils

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
160%86%14%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

hoplugins.commons.vo

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
010%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

Cycles

[ summary] [ packages] [ cycles] [ explanations]

There are no cyclic dependencies.

Explanations

[ summary] [ packages] [ cycles] [ explanations]

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

TermDescription
Number of ClassesThe number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent CouplingsThe number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent CouplingsThe number of other packages that the classes in the package depend upon is an indicator of the package's independence.
AbstractnessThe ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package. The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package.
InstabilityThe ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change. The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package.
DistanceThe perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability. A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0). The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible.
CyclesPackages participating in a package dependency cycle are in a deadly embrace with respect to reusability and their release cycle. Package dependency cycles can be easily identified by reviewing the textual reports of dependency cycles. Once these dependency cycles have been identified with JDepend, they can be broken by employing various object-oriented techniques.