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 Total

Classes
Abstract

Classes
Concrete

Classes
Afferent

Couplings
Efferent

Couplings
Abstractness Instability Distance
attrib4j 13 6 7 6 9 0.46 60% 6%
attrib4j.ant 6 0 6 0 8 0 100% 0%
attrib4j.attributes 1 0 1 1 2 0 67% 33%
attrib4j.bcel 5 1 4 1 9 0.2 90% 10%
attrib4j.cfparse 4 0 4 0 9 0 100% 0%
attrib4j.examples 6 2 4 0 5 0.33 100% 33%
attrib4j.examples.attributes 5 0 5 2 2 0 50% 50%
attrib4j.tests 4 0 4 0 9 0 100% 0%
attrib4j.utensil 2 0 2 1 3 0 75% 25%

Packages

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

attrib4j.attributes

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 0% 67% 33%
Abstract Classes Concrete Classes Used by Packages Uses Packages
JavadocAttribute

attrib4j

attrib4j

java.lang

attrib4j.bcel

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 9 20% 90% 10%
Abstract Classes Concrete Classes Used by Packages Uses Packages
AbstractBCELClassAnnotator

BCELAttributeExtractor

BCELClassAnnotator

BCELFactory

DescriptorUtil

attrib4j.tests

attrib4j

com.sun.javadoc

java.io

java.lang

java.lang.reflect

java.net

java.util

org.apache.bcel.classfile

org.apache.bcel.generic

attrib4j.cfparse

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
CFCustomAttrInfo

CFParseAttributeExtractor

CFParseClassAnnotator

CFParseFactory

attrib4j

com.ibm.toad.cfparse

com.ibm.toad.cfparse.attributes

com.ibm.toad.cfparse.utils

com.sun.javadoc

java.io

java.lang

java.net

java.util

attrib4j.examples

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 5 33% 100% 33%
Abstract Classes Concrete Classes Used by Packages Uses Packages
AbstractDeposit

DepositTransaction

ExampleClass

InheritanceTxExample

ParamParseExample

TransactionExample

attrib4j

attrib4j.examples.attributes

java.io

java.lang

java.util

attrib4j.examples.attributes

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 2 0% 50% 50%
Abstract Classes Concrete Classes Used by Packages Uses Packages
DebugAttribute

PersistentAttribute

PointCutAttribute

TraceAttribute

TransactionAttribute

attrib4j.examples

attrib4j.tests

attrib4j

java.lang

attrib4j.tests

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
AllTests

AttributeTest

DescriptorTest

ParamParseTest

attrib4j

attrib4j.bcel

attrib4j.examples.attributes

java.io

java.lang

java.lang.reflect

java.util

junit.framework

junit.textui

attrib4j.utensil

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 3 0% 75% 25%
Abstract Classes Concrete Classes Used by Packages Uses Packages
PathTokenizer

PathUtil

attrib4j

java.io

java.lang

java.util

Cycles

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

Package Cyclic Dependencies
attrib4j attrib4j.attributes

attrib4j

attrib4j.attributes attrib4j

attrib4j.attributes

attrib4j.bcel attrib4j

attrib4j.attributes

attrib4j

attrib4j.cfparse attrib4j

attrib4j.attributes

attrib4j

attrib4j.examples attrib4j.examples.attributes

attrib4j

attrib4j.attributes

attrib4j

attrib4j.examples.attributes attrib4j

attrib4j.attributes

attrib4j

attrib4j.tests attrib4j.examples.attributes

attrib4j

attrib4j.attributes

attrib4j

Explanations

[ 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.