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
org.dom4j 261881390,6941%10%
org.dom4j.bean 505080100%0%
org.dom4j.datatype 7070110100%0%
org.dom4j.dom 1501516086%14%
org.dom4j.dtd 40411050%50%
org.dom4j.io 331325210,0381%16%
org.dom4j.io.aelfred 404070100%0%
org.dom4j.io.aelfred2 40417088%12%
org.dom4j.jaxb 10370120,3100%30%
org.dom4j.persistence 743140,5780%37%
org.dom4j.persistence.nativ 110021100%100%
org.dom4j.rule 927560,2255%23%
org.dom4j.rule.pattern 20213075%25%
org.dom4j.swing 808070100%0%
org.dom4j.tree 491336880,2750%23%
org.dom4j.util 11110170,0988%3%
org.dom4j.xpath 40419090%10%
org.dom4j.xpp 10115083%17%
org.xml.sax 171161130,6521%14%
org.xml.sax.ext 853340,6257%20%
org.xml.sax.helpers 1401445056%44%

Packages

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

org.dom4j.bean

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

org.dom4j.datatype

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

org.dom4j.dtd

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
110%50%50%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.dom4j.io.aelfred

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

org.dom4j.io.aelfred2

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
170%88%12%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.dom4j.persistence

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1457%80%37%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.dom4j.persistence.nativ

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

org.dom4j.rule

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
5622%55%23%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.dom4j.rule.pattern

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
130%75%25%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.dom4j.swing

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

org.dom4j.xpath

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
190%90%10%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.dom4j.xpp

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

org.xml.sax.ext

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3462%57%20%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

Cycles

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

PackageCyclic Dependencies
org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.bean
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.datatype
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.dom
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.io
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.jaxb
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.persistence
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.persistence.nativ
  • org.dom4j.io
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.rule
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.rule.pattern
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.swing
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.tree
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.util
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j
org.dom4j.xpath
  • org.dom4j
  • org.dom4j.xpath
org.dom4j.xpp
  • org.dom4j
  • org.dom4j.xpath
  • org.dom4j

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.