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 ]

Package TC CC AC Ca Ce A I D V
net.sourceforge.jwebunit.tests 29 28 1 1 19 3.0% 95.0% 2.0% 1
net.sourceforge.jwebunit.tests.util 7 6 1 1 16 14.0% 94.0% 8.0% 1
net.sourceforge.jwebunit.tests.util.reflect 2 2 0 1 2 0.0% 67.0% 33.0% 1

Packages

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

net.sourceforge.jwebunit.tests

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 19 3.0% 95.0% 2.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
net.sourceforge.jwebunit.tests.JWebUnitAPITestCase
net.sourceforge.jwebunit.tests.ButtonAssertionsTest
net.sourceforge.jwebunit.tests.CharsetTest
net.sourceforge.jwebunit.tests.ConcurrentJWebUnitTest
net.sourceforge.jwebunit.tests.CustomTesterTest
net.sourceforge.jwebunit.tests.CustomTesterTest$MyWebTester
net.sourceforge.jwebunit.tests.ExpectedTableAssertionsHtmlTest
net.sourceforge.jwebunit.tests.ExpectedTableAssertionsXHtmlTest
net.sourceforge.jwebunit.tests.FormAssertionsTest
net.sourceforge.jwebunit.tests.FormAssertionsWithLabelTest
net.sourceforge.jwebunit.tests.FormSubmissionTest
net.sourceforge.jwebunit.tests.FramesAndWindowsTest
net.sourceforge.jwebunit.tests.HelloWorldTest
net.sourceforge.jwebunit.tests.HtmlParsingTest
net.sourceforge.jwebunit.tests.IElementTest
net.sourceforge.jwebunit.tests.ImageTest
net.sourceforge.jwebunit.tests.JavaScriptEventsTest
net.sourceforge.jwebunit.tests.JavaScriptTest
net.sourceforge.jwebunit.tests.NavigationTest
net.sourceforge.jwebunit.tests.NonHtmlContentTest
net.sourceforge.jwebunit.tests.RedirectionTest
net.sourceforge.jwebunit.tests.ResourceBundleAssertionsTest
net.sourceforge.jwebunit.tests.ResponseServletTest
net.sourceforge.jwebunit.tests.SelectOptionsTest
net.sourceforge.jwebunit.tests.TableAssertionsTest
net.sourceforge.jwebunit.tests.TestContextTest
net.sourceforge.jwebunit.tests.WebAssertionsTest
net.sourceforge.jwebunit.tests.WebCookieTest
net.sourceforge.jwebunit.tests.XPathTest
net.sourceforge.jwebunit.tests.util
com.google.code.tempusfugit.concurrency
java.io
java.lang
java.lang.reflect
java.net
java.text
java.util
javax.imageio
javax.servlet.http
net.sourceforge.jwebunit.api
net.sourceforge.jwebunit.exception
net.sourceforge.jwebunit.html
net.sourceforge.jwebunit.junit
net.sourceforge.jwebunit.tests.util
net.sourceforge.jwebunit.tests.util.reflect
net.sourceforge.jwebunit.util
org.hamcrest
org.junit
org.junit.rules

net.sourceforge.jwebunit.tests.util

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 16 14.0% 94.0% 8.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
net.sourceforge.jwebunit.tests.util.HtmlHelper
net.sourceforge.jwebunit.tests.util.CookiesServlet
net.sourceforge.jwebunit.tests.util.HeadersServlet
net.sourceforge.jwebunit.tests.util.JettySetup
net.sourceforge.jwebunit.tests.util.ParamsServlet
net.sourceforge.jwebunit.tests.util.RedirectServlet
net.sourceforge.jwebunit.tests.util.ResponseServlet
net.sourceforge.jwebunit.tests
java.io
java.lang
java.net
java.util
javax.servlet
javax.servlet.http
net.sourceforge.jwebunit.tests
org.apache.commons.fileupload
org.apache.commons.fileupload.disk
org.apache.commons.fileupload.servlet
org.eclipse.jetty.http
org.eclipse.jetty.security
org.eclipse.jetty.server
org.eclipse.jetty.server.handler
org.eclipse.jetty.webapp
org.junit

net.sourceforge.jwebunit.tests.util.reflect

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 0.0% 67.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None net.sourceforge.jwebunit.tests.util.reflect.MethodInvoker
net.sourceforge.jwebunit.tests.util.reflect.StaticMethodInvoker
net.sourceforge.jwebunit.tests
java.lang
java.lang.reflect

Cycles

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

Package Package Dependencies
net.sourceforge.jwebunit.tests net.sourceforge.jwebunit.tests.util
net.sourceforge.jwebunit.tests
net.sourceforge.jwebunit.tests.util net.sourceforge.jwebunit.tests
net.sourceforge.jwebunit.tests.util

Explanation

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

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

Term Description
Number of Classes The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent Couplings The number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent Couplings The number of other packages that the classes in the package depend upon is an indicator of the package's independence.
Abstractness The 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.
Instability The 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.
Distance The 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.
Cycles Packages 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.