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
net.sf.cantina 7707010%0%
net.sf.cantina.application 303040100%0%
net.sf.cantina.datasource 927130.2275%3%
net.sf.cantina.decorator 20212067%33%
net.sf.cantina.search 30312067%33%
net.sf.cantina.system 817030.12100%12%
net.sf.cantina.tags 413030.25100%25%
net.sf.cantina.util 651500.830%17%
net.sf.cantina.webgui 22021133%33%

Packages

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

net.sf.cantina

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

net.sf.cantina.application

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

net.sf.cantina.datasource

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1322%75%3%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

net.sf.cantina.decorator

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
120%67%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

net.sf.cantina.search

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
120%67%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

net.sf.cantina.system

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0312%100%12%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

net.sf.cantina.tags

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

net.sf.cantina.util

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
5083%0%17%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

net.sf.cantina.webgui

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21100%33%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
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.