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
com.panogenesis 10121033%67%
com.panogenesis.dao 1414044150%50%
com.panogenesis.dao.hibernate 14014090100%0%
com.panogenesis.model 17116850.0638%56%
com.panogenesis.service 161424100.8871%59%
com.panogenesis.service.impl 140140100100%0%
com.panogenesis.util 606312080%20%
com.panogenesis.webapp.action 290290260100%0%
com.panogenesis.webapp.filter 5050140100%0%
com.panogenesis.webapp.listener 20219090%10%
com.panogenesis.webapp.taglib 6060220100%0%
com.panogenesis.webapp.util 303211085%15%

Packages

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

com.panogenesis

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

com.panogenesis.webapp.listener

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

Cycles

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

PackageCyclic Dependencies
com.panogenesis.dao
  • com.panogenesis.model
  • com.panogenesis.dao
com.panogenesis.dao.hibernate
  • com.panogenesis.dao
  • com.panogenesis.model
  • com.panogenesis.dao
com.panogenesis.model
  • com.panogenesis.dao
  • com.panogenesis.model
com.panogenesis.service
  • com.panogenesis.dao
  • com.panogenesis.model
  • com.panogenesis.dao
com.panogenesis.service.impl
  • com.panogenesis.util
  • com.panogenesis.model
  • com.panogenesis.dao
  • com.panogenesis.model
com.panogenesis.util
  • com.panogenesis.model
  • com.panogenesis.dao
  • com.panogenesis.model
com.panogenesis.webapp.action
  • com.panogenesis.util
  • com.panogenesis.model
  • com.panogenesis.dao
  • com.panogenesis.model
com.panogenesis.webapp.filter
  • com.panogenesis.service
  • com.panogenesis.dao
  • com.panogenesis.model
  • com.panogenesis.dao
com.panogenesis.webapp.listener
  • com.panogenesis.service
  • com.panogenesis.dao
  • com.panogenesis.model
  • com.panogenesis.dao
com.panogenesis.webapp.taglib
  • com.panogenesis.model
  • com.panogenesis.dao
  • com.panogenesis.model

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.