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.sf.validatedattrib110410.0%20.0%80.0%1
net.sf.validatedattrib.attribute10115100.0%83.0%83.0%1
net.sf.validatedattrib.attribute.primitive110040.0%100.0%0.0%1
net.sf.validatedattrib.constraint10122100.0%50.0%50.0%1
net.sf.validatedattrib.constraint.primitive2111350.0%75.0%25.0%1

Packages

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

net.sf.validatedattrib

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
410.0%20.0%80.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenet.sf.validatedattrib.ValidationException
net.sf.validatedattrib.attribute
net.sf.validatedattrib.attribute.primitive
net.sf.validatedattrib.constraint
net.sf.validatedattrib.constraint.primitive
java.lang

net.sf.validatedattrib.attribute

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
15100.0%83.0%83.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.sf.validatedattrib.attribute.AbstractValidatedAttribute
Nonenet.sf.validatedattrib.attribute.primitive
java.lang
java.util
net.sf.validatedattrib
net.sf.validatedattrib.constraint
org.apache.commons.logging

net.sf.validatedattrib.attribute.primitive

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
040.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenet.sf.validatedattrib.attribute.primitive.ValidatedDouble
Nonejava.lang
net.sf.validatedattrib
net.sf.validatedattrib.attribute
net.sf.validatedattrib.constraint.primitive

net.sf.validatedattrib.constraint

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
22100.0%50.0%50.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.sf.validatedattrib.constraint.Constraint
Nonenet.sf.validatedattrib.attribute
net.sf.validatedattrib.constraint.primitive
java.lang
net.sf.validatedattrib

net.sf.validatedattrib.constraint.primitive

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1350.0%75.0%25.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.sf.validatedattrib.constraint.primitive.DoubleConstraint
net.sf.validatedattrib.constraint.primitive.ValidatedDoubleMinMaxConstraint
net.sf.validatedattrib.attribute.primitive
java.lang
net.sf.validatedattrib
net.sf.validatedattrib.constraint

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.