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
nextgrid.api.builder 3 2 1 0 10 33.0% 100.0% 33.0% 1
nextgrid.api.env 9 4 5 3 7 56.0% 70.0% 26.0% 1
nextgrid.api.pem 7 2 5 2 5 71.0% 71.0% 43.0% 1
nextgrid.api.pom 26 7 19 4 14 73.0% 78.0% 51.0% 1
nextgrid.api.ram 3 1 2 0 6 67.0% 100.0% 67.0% 1

Packages

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

nextgrid.api.builder

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 10 33.0% 100.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
nextgrid.api.builder.POMBuilder
nextgrid.api.builder.BuildException
nextgrid.api.builder.POMBuilderFinder
None java.io
java.lang
java.net
java.util
java.util.concurrent
nextgrid.api.pom
org.apache.commons.discovery
org.apache.commons.discovery.resource
org.apache.commons.discovery.resource.names
org.apache.commons.logging

nextgrid.api.env

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 7 56.0% 70.0% 26.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
nextgrid.api.env.Prioritiser
nextgrid.api.env.ProcessDiscoverer
nextgrid.api.env.ProcessEnvironment
nextgrid.api.env.ProcessSelector
nextgrid.api.env.STSModule
nextgrid.api.env.DiscoveryException
nextgrid.api.env.PriorityException
nextgrid.api.env.STSFailureException
nextgrid.api.env.SelectionException
nextgrid.api.pem
nextgrid.api.pom
nextgrid.api.ram
java.io
java.lang
java.net
java.util
nextgrid.api.pem
nextgrid.api.pom
org.w3c.dom

nextgrid.api.pem

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 5 71.0% 71.0% 43.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
nextgrid.api.pem.ControlListener
nextgrid.api.pem.DiscoveryListener
nextgrid.api.pem.POMEvent
nextgrid.api.pem.POMListener
nextgrid.api.pem.ProcessListener
nextgrid.api.pem.DiscoveryEvent
nextgrid.api.pem.ProcessEvent
nextgrid.api.env
nextgrid.api.pom
java.io
java.lang
java.util
nextgrid.api.env
nextgrid.api.pom

nextgrid.api.pom

Afferent Couplings Efferent Couplings Abstractness Instability Distance
4 14 73.0% 78.0% 51.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
nextgrid.api.pom.AbstractProcess
nextgrid.api.pom.AsyncProcess
nextgrid.api.pom.ControlProcess
nextgrid.api.pom.DoWhileProcess
nextgrid.api.pom.Expression
nextgrid.api.pom.Grounding
nextgrid.api.pom.GroundingFactory
nextgrid.api.pom.IfThenElseProcess
nextgrid.api.pom.LoopProcess
nextgrid.api.pom.Process
nextgrid.api.pom.ProcessController
nextgrid.api.pom.ProcessFactory
nextgrid.api.pom.Reference
nextgrid.api.pom.RepeatUntilProcess
nextgrid.api.pom.SequenceProcess
nextgrid.api.pom.Service
nextgrid.api.pom.SplitJoinProcess
nextgrid.api.pom.UnorderedListProcess
nextgrid.api.pom.WhileDoProcess
nextgrid.api.pom.ExpressionException
nextgrid.api.pom.GroundingFactoryFinder
nextgrid.api.pom.ProcessController$State
nextgrid.api.pom.ProcessException
nextgrid.api.pom.ProcessFactoryFinder
nextgrid.api.pom.Query
nextgrid.api.pom.QueryProfile
nextgrid.api.builder
nextgrid.api.env
nextgrid.api.pem
nextgrid.api.ram
java.io
java.lang
java.net
java.util
java.util.concurrent
java.util.concurrent.locks
javax.xml.namespace
nextgrid.api.env
nextgrid.api.pem
org.apache.commons.discovery
org.apache.commons.discovery.resource
org.apache.commons.discovery.resource.names
org.apache.commons.discovery.tools
org.apache.commons.logging

nextgrid.api.ram

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 67.0% 100.0% 67.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
nextgrid.api.ram.Discoverer
nextgrid.api.ram.Registry
nextgrid.api.ram.RegistryException
None java.io
java.lang
java.net
java.util
nextgrid.api.env
nextgrid.api.pom

Cycles

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

Package Package Dependencies
nextgrid.api.builder nextgrid.api.pom
nextgrid.api.env
nextgrid.api.pom
nextgrid.api.env nextgrid.api.pom
nextgrid.api.env
nextgrid.api.pem nextgrid.api.pom
nextgrid.api.env
nextgrid.api.pom
nextgrid.api.pom nextgrid.api.env
nextgrid.api.pom
nextgrid.api.ram nextgrid.api.env
nextgrid.api.pom
nextgrid.api.env

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.