Metric Results

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

The following document contains the results of a JDepend metric analysis. The various metrics are defined at the bottom of this document.

Summary

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

PackageTCCCACCaCeAIDV
net.smartlab.config3027302110.0%100.0%10.0%1

Packages

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

net.smartlab.config

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
02110.0%100.0%10.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.smartlab.config.Configuration
net.smartlab.config.Element
net.smartlab.config.Listener
net.smartlab.config.AbstractConfigurationTest
net.smartlab.config.AbstractConfigurationTest$1
net.smartlab.config.AbstractConfigurationTest$2
net.smartlab.config.Configuration$Monitor
net.smartlab.config.ConfigurationException
net.smartlab.config.ConfigurationExceptionTest
net.smartlab.config.ConfigurationTest
net.smartlab.config.ConfigurationTest$1
net.smartlab.config.ConfigurationTest$2
net.smartlab.config.ConfigurationTest$3
net.smartlab.config.ConfigurationTest$4
net.smartlab.config.ConfigurationTest$5
net.smartlab.config.ConfigurationTest$6
net.smartlab.config.ElementTest
net.smartlab.config.ListenerTest
net.smartlab.config.ListenerTest$1
net.smartlab.config.Node
net.smartlab.config.NodeTest
net.smartlab.config.Reference
net.smartlab.config.ReferenceTest
net.smartlab.config.SQLConfiguration
net.smartlab.config.SQLConfiguration$SimpleDataSource
net.smartlab.config.SQLConfiguration$SimpleDataSource$ConnectionWrapper
net.smartlab.config.SQLConfigurationTest
net.smartlab.config.XMLConfiguration
net.smartlab.config.XMLConfiguration$XMLHandler
net.smartlab.config.XMLConfigurationTest
Nonejava.io
java.lang
java.net
java.security
java.sql
java.util
javax.crypto
javax.crypto.spec
javax.sql
javax.xml.parsers
junit.framework
junitx.framework
org.apache.commons.dbcp
org.dbunit
org.dbunit.database
org.dbunit.dataset
org.dbunit.dataset.xml
org.dbunit.operation
org.jmock
org.xml.sax
org.xml.sax.helpers

Cycles

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

There are no cyclic dependencies.

Explanation

[ 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.