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.cache 26 14 12 2 4 46.0% 67.0% 13.0% 1
org.apache.commons.cache.adt 5 4 1 1 1 20.0% 50.0% 30.000002% 1
org.apache.commons.cache.remote 19 17 2 0 3 11.0% 100.0% 11.0% 1
org.apache.commons.cache.tagext 2 2 0 0 6 0.0% 100.0% 0.0% 1

Packages

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

org.apache.commons.cache

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 4 46.0% 67.0% 13.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.commons.cache.BaseCache
org.apache.commons.cache.BaseStash
org.apache.commons.cache.BaseStashPolicy
org.apache.commons.cache.Cache
org.apache.commons.cache.CachedObjectInfo
org.apache.commons.cache.CachedObjectIterator
org.apache.commons.cache.EvictionPolicy
org.apache.commons.cache.GroupMap
org.apache.commons.cache.RetrievalListener
org.apache.commons.cache.Stash
org.apache.commons.cache.StashPolicy
org.apache.commons.cache.StorageListener
org.apache.commons.cache.BaseRetrievalListener
org.apache.commons.cache.BaseStorageListener
org.apache.commons.cache.CacheSingleton
org.apache.commons.cache.CacheStat
org.apache.commons.cache.CachedObjectInfoImpl
org.apache.commons.cache.FileStash
org.apache.commons.cache.GroupMapImpl
org.apache.commons.cache.LRUEvictionPolicy
org.apache.commons.cache.MemoryStash
org.apache.commons.cache.NoOpCache
org.apache.commons.cache.RecursiveFileDeleter
org.apache.commons.cache.ShareableFileStash
org.apache.commons.cache.SimpleCache
org.apache.commons.cache.StaleObjectEvictor
org.apache.commons.cache.remote
org.apache.commons.cache.tagext
java.io
java.lang
java.util
org.apache.commons.cache.adt

org.apache.commons.cache.adt

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 1 20.0% 50.0% 30.000002%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.commons.cache.adt.Listable
org.apache.commons.cache.adt.ListableBase
org.apache.commons.cache.adt.ListableObject
org.apache.commons.cache.adt.WListableBase
org.apache.commons.cache.adt.WListableObject
org.apache.commons.cache
java.lang

org.apache.commons.cache.remote

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 3 11.0% 100.0% 11.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.commons.cache.remote.CacheRequest
org.apache.commons.cache.remote.CacheResponse
org.apache.commons.cache.remote.Ack
org.apache.commons.cache.remote.BooleanResponse
org.apache.commons.cache.remote.CacheStatResponse
org.apache.commons.cache.remote.ClearAllRequest
org.apache.commons.cache.remote.ClearGroupRequest
org.apache.commons.cache.remote.ClearRequest
org.apache.commons.cache.remote.ClosingConnection
org.apache.commons.cache.remote.ContainsRequest
org.apache.commons.cache.remote.GetCacheStatRequest
org.apache.commons.cache.remote.GetKeysForGroupRequest
org.apache.commons.cache.remote.ObjectArrayResponse
org.apache.commons.cache.remote.ObjectResponse
org.apache.commons.cache.remote.OkResponse
org.apache.commons.cache.remote.ProtocolErrorResponse
org.apache.commons.cache.remote.RetrieveRequest
org.apache.commons.cache.remote.StoreRequest
org.apache.commons.cache.remote.ThrowableResponse
None java.io
java.lang
org.apache.commons.cache

org.apache.commons.cache.tagext

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.commons.cache.tagext.CacheTag
org.apache.commons.cache.tagext.ClearCacheTag
None java.io
java.lang
javax.servlet.jsp
javax.servlet.jsp.tagext
org.apache.commons.cache
org.apache.commons.jocl

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.