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
cldcunit.runner6331650.0%86.0%36.0%1
junit.framework14951436.0%80.0%16.0%1

Packages

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

cldcunit.runner

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1650.0%86.0%36.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
cldcunit.runner.BaseTestCaseHelper
cldcunit.runner.TestCaseHelper
cldcunit.runner.TestCaseReflectionData
cldcunit.runner.InstrumentedTestCaseHelper
cldcunit.runner.TestRunner
cldcunit.runner.TestRunner$1
junit.framework
java.io
java.lang
java.util
javax.microedition.lcdui
javax.microedition.midlet
junit.framework

junit.framework

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1436.0%80.0%16.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
junit.framework.Protectable
junit.framework.Test
junit.framework.TestCase
junit.framework.TestListener
junit.framework.TestMethod
junit.framework.Assert
junit.framework.AssertionFailedError
junit.framework.ComparisonFailure
junit.framework.TestFailure
junit.framework.TestResult
junit.framework.TestResult$1
junit.framework.TestSuite
junit.framework.TestSuite$1
junit.framework.TestSuite$2
cldcunit.runner
cldcunit.runner
java.io
java.lang
java.util

Cycles

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

PackagePackage Dependencies
cldcunit.runnerjunit.framework
cldcunit.runner
junit.frameworkcldcunit.runner
junit.framework

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.