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.semispace 20 17 3 2 13 15.000001% 87.0% 2.0% 1
org.semispace.actor 6 4 2 0 10 33.0% 100.0% 33.0% 1
org.semispace.admin 12 10 2 1 8 17.0% 89.0% 6.0% 1
org.semispace.event 5 4 1 3 1 20.0% 25.0% 55.0% 1
org.semispace.exception 5 5 0 2 1 0.0% 33.0% 67.0% 1

Packages

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

org.semispace

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 13 15.000001% 87.0% 2.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.semispace.SemiEventListener
org.semispace.SemiLease
org.semispace.SemiSpaceInterface
org.semispace.DistributedEvent
org.semispace.ElementLease
org.semispace.EventDistributor
org.semispace.Holder
org.semispace.HolderContainer
org.semispace.HolderElement
org.semispace.ListenerHolder
org.semispace.ListenerLease
org.semispace.NameValueQuery
org.semispace.SemiBlockingListener
org.semispace.SemiEventRegistration
org.semispace.SemiSpace
org.semispace.SemiSpace$1
org.semispace.SemiSpace$PreprocessedTemplate
org.semispace.SemiSpace$ShortestTtlComparator
org.semispace.SemiSpace$WrappedInternalWriter
org.semispace.SemiSpaceStatistics
org.semispace.actor
org.semispace.admin
com.thoughtworks.xstream
com.thoughtworks.xstream.io.xml
java.io
java.lang
java.lang.reflect
java.util
java.util.concurrent
java.util.concurrent.atomic
java.util.concurrent.locks
org.semispace.admin
org.semispace.event
org.semispace.exception
org.slf4j

org.semispace.actor

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 10 33.0% 100.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.semispace.actor.Actor
org.semispace.actor.SwingActor
org.semispace.actor.ActorManifest
org.semispace.actor.ActorMessage
org.semispace.actor.ActorNotification
org.semispace.actor.ActorNotification$ActorMessageTaker
None com.thoughtworks.xstream
java.lang
java.lang.annotation
java.util
java.util.concurrent
javax.swing
org.semispace
org.semispace.event
org.semispace.exception
org.slf4j

org.semispace.admin

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 8 17.0% 89.0% 6.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.semispace.admin.InternalQuery
org.semispace.admin.SemiSpaceAdminInterface
org.semispace.admin.DaemonDelegateFactory
org.semispace.admin.IdentifyAdminQuery
org.semispace.admin.PeriodicHarvest
org.semispace.admin.ScheduledSemiSpaceHarvester
org.semispace.admin.SemiSpaceAdmin
org.semispace.admin.SemiSpaceAdmin$1
org.semispace.admin.SemiSpaceAdmin$IdentifyAdminQueryComparator
org.semispace.admin.SemiSpaceRejectedExecutionHandler
org.semispace.admin.TimeAnswer
org.semispace.admin.TimeQuery
org.semispace
com.thoughtworks.xstream
java.io
java.lang
java.util
java.util.concurrent
org.semispace
org.semispace.event
org.slf4j

org.semispace.event

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 1 20.0% 25.0% 55.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.semispace.event.SemiEvent
org.semispace.event.SemiAvailabilityEvent
org.semispace.event.SemiExpirationEvent
org.semispace.event.SemiRenewalEvent
org.semispace.event.SemiTakenEvent
org.semispace
org.semispace.actor
org.semispace.admin
java.lang

org.semispace.exception

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 1 0.0% 33.0% 67.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.semispace.exception.ActorException
org.semispace.exception.SemiSpaceException
org.semispace.exception.SemiSpaceInternalException
org.semispace.exception.SemiSpaceObjectException
org.semispace.exception.SemiSpaceUsageException
org.semispace
org.semispace.actor
java.lang

Cycles

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

Package Package Dependencies
org.semispace org.semispace.admin
org.semispace
org.semispace.actor org.semispace
org.semispace.admin
org.semispace
org.semispace.admin org.semispace
org.semispace.admin

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.