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
ori 651350,8362%46%
ori.data 55051117%17%
ori.impl 60628080%20%
ori.impl.encoder 2020100100%0%
ori.impl.provider.xml 202090100%0%
ori.impl.utils 101010100%0%
ori.impl.utils.proxy 303030100%0%
ori.jaas 10192110,185%5%

Packages

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

ori

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3583%62%46%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

ori.data

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

ori.impl

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
280%80%20%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

ori.impl.encoder

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

ori.impl.provider.xml

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

ori.impl.utils

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

ori.impl.utils.proxy

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

ori.jaas

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21110%85%5%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

Cycles

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

PackageCyclic Dependencies
ori
  • ori.impl
  • ori.jaas
  • ori
ori.impl
  • ori.jaas
  • ori
  • ori.impl
ori.impl.encoder
  • ori
  • ori.impl
  • ori.jaas
  • ori
ori.impl.provider.xml
  • ori
  • ori.impl
  • ori.jaas
  • ori
ori.jaas
  • ori
  • ori.impl
  • ori.jaas

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.