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.joyaop 761420.8633%19%
net.sf.joyaop.config 3121110.3392%25%
net.sf.joyaop.framework 99034157%57%
net.sf.joyaop.impl 408322140.288%8%
net.sf.joyaop.impl.aspect 163132120.1986%4%
net.sf.joyaop.util 11035162%62%

Packages

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

net.sf.joyaop

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
4286%33%19%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

net.sf.joyaop.config

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
11133%92%25%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

net.sf.joyaop.framework

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
34100%57%57%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

net.sf.joyaop.impl

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21420%88%8%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

net.sf.joyaop.impl.aspect

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21219%86%4%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

net.sf.joyaop.util

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
35100%62%62%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

Cycles

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

PackageCyclic Dependencies
net.sf.joyaop.config
  • net.sf.joyaop.impl
  • net.sf.joyaop.impl.aspect
  • net.sf.joyaop.impl
net.sf.joyaop.impl
  • net.sf.joyaop.impl.aspect
  • net.sf.joyaop.impl
net.sf.joyaop.impl.aspect
  • net.sf.joyaop.impl
  • net.sf.joyaop.impl.aspect

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.