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.web.test2924502317.0%100.0%17.0%1

Packages

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

net.smartlab.web.test

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
02317.0%100.0%17.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.smartlab.web.test.ActionTestCase
net.smartlab.web.test.BasicDomainTestCase
net.smartlab.web.test.BusinessObjectFactoryTestCase
net.smartlab.web.test.DomainTestCase
net.smartlab.web.test.ModelTestCase
net.smartlab.web.test.ActionTestCaseTest
net.smartlab.web.test.ActionTestCaseTest$Domain
net.smartlab.web.test.ActionTestCaseTest$Entity
net.smartlab.web.test.ActionTestCaseTest$EntityFactory
net.smartlab.web.test.BusinessObjectFactoryTestCase$1
net.smartlab.web.test.BusinessObjectFactoryTestCaseTest
net.smartlab.web.test.BusinessObjectFactoryTestCaseTest$ExportBusinessObjectFactoryTestCase
net.smartlab.web.test.BusinessObjectFactoryTestCaseTest$NullBusinessObject
net.smartlab.web.test.BusinessObjectFactoryTestCaseTest$NullBusinessObjectFactory
net.smartlab.web.test.BusinessObjectFactoryTestCaseTest$NullBusinessObjectFactoryTestCase
net.smartlab.web.test.BusinessObjectFactoryTestSupport
net.smartlab.web.test.BusinessObjectFactoryTestSupportTest
net.smartlab.web.test.DomainTestCase$BusinessObjectFactoryTestCaseWrapper
net.smartlab.web.test.DomainTestCaseTest
net.smartlab.web.test.DomainTestCaseTest$1
net.smartlab.web.test.DomainTestSupport
net.smartlab.web.test.DomainTestSupportTest
net.smartlab.web.test.EnumerationAssert
net.smartlab.web.test.EnumerationAssertTest
net.smartlab.web.test.EnumerationAssertTest$Mock
net.smartlab.web.test.ModelTestCase$TestConfiguration
net.smartlab.web.test.StringEnumerationAssert
net.smartlab.web.test.StringEnumerationAssertTest
net.smartlab.web.test.StringEnumerationAssertTest$Mock
Nonecom.mchange.v2.c3p0
java.io
java.lang
java.net
java.sql
java.util
javax.naming
javax.sql
junit.framework
net.smartlab.config
net.smartlab.web
net.smartlab.web.config
org.apache.commons.logging
org.dbunit
org.dbunit.database
org.dbunit.dataset
org.dbunit.dataset.xml
org.dbunit.operation
org.hibernate
org.hibernate.cfg
org.hibernate.dialect
org.mockejb.jndi
servletunit.struts

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.