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
org.apache.commons.pool 27 17 10 1 2 37.0% 67.0% 4.0% 1
org.apache.commons.pool.impl 28 28 0 0 7 0.0% 100.0% 0.0% 1

Packages

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

org.apache.commons.pool

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 37.0% 67.0% 4.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.commons.pool.BaseKeyedObjectPool
org.apache.commons.pool.BaseKeyedPoolableObjectFactory
org.apache.commons.pool.BaseObjectPool
org.apache.commons.pool.BasePoolableObjectFactory
org.apache.commons.pool.KeyedObjectPool
org.apache.commons.pool.KeyedObjectPoolFactory
org.apache.commons.pool.KeyedPoolableObjectFactory
org.apache.commons.pool.ObjectPool
org.apache.commons.pool.ObjectPoolFactory
org.apache.commons.pool.PoolableObjectFactory
org.apache.commons.pool.PoolUtils
org.apache.commons.pool.PoolUtils$CheckedKeyedObjectPool
org.apache.commons.pool.PoolUtils$CheckedObjectPool
org.apache.commons.pool.PoolUtils$ErodingFactor
org.apache.commons.pool.PoolUtils$ErodingKeyedObjectPool
org.apache.commons.pool.PoolUtils$ErodingObjectPool
org.apache.commons.pool.PoolUtils$ErodingPerKeyKeyedObjectPool
org.apache.commons.pool.PoolUtils$KeyedObjectPoolAdaptor
org.apache.commons.pool.PoolUtils$KeyedObjectPoolMinIdleTimerTask
org.apache.commons.pool.PoolUtils$KeyedPoolableObjectFactoryAdaptor
org.apache.commons.pool.PoolUtils$ObjectPoolAdaptor
org.apache.commons.pool.PoolUtils$ObjectPoolMinIdleTimerTask
org.apache.commons.pool.PoolUtils$PoolableObjectFactoryAdaptor
org.apache.commons.pool.PoolUtils$SynchronizedKeyedObjectPool
org.apache.commons.pool.PoolUtils$SynchronizedKeyedPoolableObjectFactory
org.apache.commons.pool.PoolUtils$SynchronizedObjectPool
org.apache.commons.pool.PoolUtils$SynchronizedPoolableObjectFactory
org.apache.commons.pool.impl
java.lang
java.util

org.apache.commons.pool.impl

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 7 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.commons.pool.impl.CursorableLinkedList
org.apache.commons.pool.impl.CursorableLinkedList$Cursor
org.apache.commons.pool.impl.CursorableLinkedList$ListIter
org.apache.commons.pool.impl.CursorableLinkedList$Listable
org.apache.commons.pool.impl.CursorableSubList
org.apache.commons.pool.impl.EvictionTimer
org.apache.commons.pool.impl.EvictionTimer$1
org.apache.commons.pool.impl.EvictionTimer$PrivilegedGetTccl
org.apache.commons.pool.impl.EvictionTimer$PrivilegedSetTccl
org.apache.commons.pool.impl.GenericKeyedObjectPool
org.apache.commons.pool.impl.GenericKeyedObjectPool$1
org.apache.commons.pool.impl.GenericKeyedObjectPool$Config
org.apache.commons.pool.impl.GenericKeyedObjectPool$Evictor
org.apache.commons.pool.impl.GenericKeyedObjectPool$Latch
org.apache.commons.pool.impl.GenericKeyedObjectPool$ObjectQueue
org.apache.commons.pool.impl.GenericKeyedObjectPool$ObjectTimestampPair
org.apache.commons.pool.impl.GenericKeyedObjectPoolFactory
org.apache.commons.pool.impl.GenericObjectPool
org.apache.commons.pool.impl.GenericObjectPool$1
org.apache.commons.pool.impl.GenericObjectPool$Config
org.apache.commons.pool.impl.GenericObjectPool$Evictor
org.apache.commons.pool.impl.GenericObjectPool$Latch
org.apache.commons.pool.impl.GenericObjectPoolFactory
org.apache.commons.pool.impl.SoftReferenceObjectPool
org.apache.commons.pool.impl.StackKeyedObjectPool
org.apache.commons.pool.impl.StackKeyedObjectPoolFactory
org.apache.commons.pool.impl.StackObjectPool
org.apache.commons.pool.impl.StackObjectPoolFactory
None java.io
java.lang
java.lang.ref
java.lang.reflect
java.security
java.util
org.apache.commons.pool

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.

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.