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.sourceforge.rules.compiler.drools220090.0%100.0%0.0%1
net.sourceforge.rules.compiler.drools.main9901110.0%92.0%8.0%1
net.sourceforge.rules.compiler.drools.util9811411.0%80.0%9.0%1

Packages

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

net.sourceforge.rules.compiler.drools

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
090.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenet.sourceforge.rules.compiler.drools.DroolsRulesCompiler
net.sourceforge.rules.compiler.drools.Main
Nonejava.io
java.lang
java.lang.reflect
java.util
net.sourceforge.rules.compiler
net.sourceforge.rules.compiler.drools.main
org.codehaus.plexus.logging
org.codehaus.plexus.util
org.codehaus.plexus.util.cli

net.sourceforge.rules.compiler.drools.main

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1110.0%92.0%8.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenet.sourceforge.rules.compiler.drools.main.CommandLine
net.sourceforge.rules.compiler.drools.main.Main
net.sourceforge.rules.compiler.drools.main.Main$1
net.sourceforge.rules.compiler.drools.main.Main$2
net.sourceforge.rules.compiler.drools.main.Main$3
net.sourceforge.rules.compiler.drools.main.Main$4
net.sourceforge.rules.compiler.drools.main.Main$HiddenOption
net.sourceforge.rules.compiler.drools.main.Main$Option
net.sourceforge.rules.compiler.drools.main.RulesCompiler
net.sourceforge.rules.compiler.drools
java.io
java.lang
java.text
java.util
net.sourceforge.rules.compiler.drools.util
org.drools.builder
org.drools.definition
org.drools.definitions.impl
org.drools.io
org.drools.rule
org.drools.util

net.sourceforge.rules.compiler.drools.util

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1411.0%80.0%9.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.sourceforge.rules.compiler.drools.util.Context$Factory
net.sourceforge.rules.compiler.drools.util.Context
net.sourceforge.rules.compiler.drools.util.Context$Key
net.sourceforge.rules.compiler.drools.util.Diagnostic
net.sourceforge.rules.compiler.drools.util.FatalError
net.sourceforge.rules.compiler.drools.util.FileUtil
net.sourceforge.rules.compiler.drools.util.IOUtil
net.sourceforge.rules.compiler.drools.util.Log
net.sourceforge.rules.compiler.drools.util.Options
net.sourceforge.rules.compiler.drools.main
java.io
java.lang
java.text
java.util

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.