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
com.github.davidmoten.grumpy.wms 32 28 4 2 25 12.0% 93.0% 5.0% 1
com.github.davidmoten.grumpy.wms.reduction 6 4 2 0 7 33.0% 100.0% 33.0% 1
com.github.davidmoten.util.servlet 1 1 0 1 4 0.0% 80.0% 20.0% 1

Packages

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

com.github.davidmoten.grumpy.wms

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 25 12.0% 93.0% 5.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
com.github.davidmoten.grumpy.wms.CapabilitiesProvider
com.github.davidmoten.grumpy.wms.ImageWriter
com.github.davidmoten.grumpy.wms.Layer
com.github.davidmoten.grumpy.wms.Layers
com.github.davidmoten.grumpy.wms.Capabilities
com.github.davidmoten.grumpy.wms.Capabilities$1
com.github.davidmoten.grumpy.wms.Capabilities$Builder
com.github.davidmoten.grumpy.wms.CapabilitiesLayer
com.github.davidmoten.grumpy.wms.CapabilitiesLayer$1
com.github.davidmoten.grumpy.wms.CapabilitiesLayer$Builder
com.github.davidmoten.grumpy.wms.CapabilitiesProviderEmpty
com.github.davidmoten.grumpy.wms.CapabilitiesProviderFromCapabilities
com.github.davidmoten.grumpy.wms.CapabilitiesProviderFromClasspath
com.github.davidmoten.grumpy.wms.ImageCache
com.github.davidmoten.grumpy.wms.ImageWriterDefault
com.github.davidmoten.grumpy.wms.LayerFeatures
com.github.davidmoten.grumpy.wms.LayerFeatures$1
com.github.davidmoten.grumpy.wms.LayerFeatures$Builder
com.github.davidmoten.grumpy.wms.LayerManager
com.github.davidmoten.grumpy.wms.LayerManager$1
com.github.davidmoten.grumpy.wms.LayerManager$2
com.github.davidmoten.grumpy.wms.LayerManager$MyGraphics
com.github.davidmoten.grumpy.wms.LayersBuilder
com.github.davidmoten.grumpy.wms.LayersBuilder$1
com.github.davidmoten.grumpy.wms.MissingMandatoryParameterException
com.github.davidmoten.grumpy.wms.RendererUtil
com.github.davidmoten.grumpy.wms.UnknownParameterException
com.github.davidmoten.grumpy.wms.WmsRequest
com.github.davidmoten.grumpy.wms.WmsServletRequestProcessor
com.github.davidmoten.grumpy.wms.WmsServletRequestProcessor$1
com.github.davidmoten.grumpy.wms.WmsServletRequestProcessor$Builder
com.github.davidmoten.grumpy.wms.WmsUtil
com.github.davidmoten.grumpy.wms.reduction
com.github.davidmoten.util.servlet
com.github.davidmoten.grumpy.core
com.github.davidmoten.grumpy.projection
com.github.davidmoten.util.servlet
com.jamesmurty.utils
com.vividsolutions.jts.geom
java.awt
java.awt.geom
java.awt.image
java.io
java.lang
java.lang.reflect
java.net
java.text
java.util
java.util.concurrent
javax.imageio
javax.servlet
javax.servlet.http
javax.xml.parsers
javax.xml.transform
org.apache.commons.io
org.apache.commons.lang3
org.geotools.geometry.jts
org.geotools.renderer.lite
org.slf4j

com.github.davidmoten.grumpy.wms.reduction

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 7 33.0% 100.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
com.github.davidmoten.grumpy.wms.reduction.RectangleSampler
com.github.davidmoten.grumpy.wms.reduction.ValueRenderer
com.github.davidmoten.grumpy.wms.reduction.RectangleSamplerCorners
com.github.davidmoten.grumpy.wms.reduction.RectangleSamplerGrid
com.github.davidmoten.grumpy.wms.reduction.RectangleUtil
com.github.davidmoten.grumpy.wms.reduction.Reducer
None com.github.davidmoten.grumpy.core
com.github.davidmoten.grumpy.projection
com.github.davidmoten.grumpy.wms
com.google.common.base
java.awt
java.lang
java.util

com.github.davidmoten.util.servlet

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 4 0.0% 80.0% 20.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None com.github.davidmoten.util.servlet.RequestUtil
com.github.davidmoten.grumpy.wms
com.github.davidmoten.grumpy.wms
java.lang
java.util
javax.servlet.http

Cycles

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

Package Package Dependencies
com.github.davidmoten.grumpy.wms com.github.davidmoten.util.servlet
com.github.davidmoten.grumpy.wms
com.github.davidmoten.grumpy.wms.reduction com.github.davidmoten.grumpy.wms
com.github.davidmoten.util.servlet
com.github.davidmoten.grumpy.wms
com.github.davidmoten.util.servlet com.github.davidmoten.grumpy.wms
com.github.davidmoten.util.servlet

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.