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.dbforms.config 2612511200,0465%32%
org.dbforms.conprovider 1019180,189%1%
org.dbforms.devgui 272250140,07100%7%
org.dbforms.dom 3122140,3388%21%
org.dbforms.event 197125120,3771%7%
org.dbforms.event.classic 8080100100%0%
org.dbforms.event.datalist 9090110100%0%
org.dbforms.event.datalist.dao 6152130,1787%3%
org.dbforms.event.eventtype 725130,2975%4%
org.dbforms.interfaces 12102880,8350%33%
org.dbforms.servlets 6060210100%0%
org.dbforms.servlets.base 11027178%78%
org.dbforms.servlets.reports 7341170,4394%37%
org.dbforms.taglib 755702200,0791%2%
org.dbforms.taglib.cewolf 110110210100%0%
org.dbforms.util 210211422061%39%
org.dbforms.util.external 50546060%40%
org.dbforms.validation 40417088%12%
org.dbforms.xmldb 20214080%20%

Packages

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

org.dbforms.event.classic

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

org.dbforms.event.datalist

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

org.dbforms.event.eventtype

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1329%75%4%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.dbforms.servlets.base

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
27100%78%78%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.dbforms.taglib

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2207%91%2%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.dbforms.util.external

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

org.dbforms.validation

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

org.dbforms.xmldb

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

Cycles

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

PackageCyclic Dependencies
org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.conprovider
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.devgui
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.dom
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.event
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.event.classic
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.event.datalist
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.event.datalist.dao
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
org.dbforms.servlets
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.servlets.base
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.servlets.reports
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.taglib
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.taglib.cewolf
  • org.dbforms.taglib
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config
  • org.dbforms.util
org.dbforms.validation
  • org.dbforms.config
  • org.dbforms.util
  • org.dbforms.interfaces
  • org.dbforms.config

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.