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.shiro.guice 19 17 2 1 24 11.0% 96.0% 7.0% 1
org.apache.shiro.guice.aop 4 4 0 0 7 0.0% 100.0% 0.0% 1
org.apache.shiro.guice.web 12 11 1 0 24 8.0% 100.0% 8.0% 1

Packages

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

org.apache.shiro.guice

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 24 11.0% 96.0% 7.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.shiro.guice.DestroyableInjectionListener$DestroyableRegistry
org.apache.shiro.guice.ShiroModule
org.apache.shiro.guice.BeanTypeListener
org.apache.shiro.guice.BeanTypeListener$1
org.apache.shiro.guice.BeanTypeListener$BeanTypeKey
org.apache.shiro.guice.DestroyableInjectionListener
org.apache.shiro.guice.GuiceEnvironment
org.apache.shiro.guice.InitializableInjectionListener
org.apache.shiro.guice.LifecycleTypeListener
org.apache.shiro.guice.ShiroMatchers
org.apache.shiro.guice.ShiroMatchers$1
org.apache.shiro.guice.ShiroMatchers$2
org.apache.shiro.guice.ShiroModule$1
org.apache.shiro.guice.ShiroModule$EventBusAwareTypeListener
org.apache.shiro.guice.ShiroModule$EventBusAwareTypeListener$1
org.apache.shiro.guice.ShiroModule$SubscribedEventTypeListener
org.apache.shiro.guice.ShiroModule$SubscribedEventTypeListener$1
org.apache.shiro.guice.ShiroSessionScope
org.apache.shiro.guice.ShiroSessionScope$1
org.apache.shiro.guice.web
com.google.inject
com.google.inject.binder
com.google.inject.matcher
com.google.inject.multibindings
com.google.inject.name
com.google.inject.spi
com.google.inject.util
java.beans
java.lang
java.lang.reflect
java.util
org.apache.commons.beanutils
org.apache.shiro
org.apache.shiro.config
org.apache.shiro.env
org.apache.shiro.event
org.apache.shiro.event.support
org.apache.shiro.mgt
org.apache.shiro.realm
org.apache.shiro.session
org.apache.shiro.session.mgt
org.apache.shiro.subject
org.apache.shiro.util
org.slf4j

org.apache.shiro.guice.aop

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.shiro.guice.aop.AopAllianceMethodInterceptorAdapter
org.apache.shiro.guice.aop.AopAllianceMethodInvocationAdapter
org.apache.shiro.guice.aop.ShiroAopModule
org.apache.shiro.guice.aop.ShiroAopModule$1
None com.google.inject
com.google.inject.matcher
java.lang
java.lang.reflect
org.aopalliance.intercept
org.apache.shiro.aop
org.apache.shiro.authz.aop

org.apache.shiro.guice.web

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 24 8.0% 100.0% 8.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.shiro.guice.web.ShiroWebModule
org.apache.shiro.guice.web.AbstractInjectionProvider
org.apache.shiro.guice.web.FilterChainResolverProvider
org.apache.shiro.guice.web.GuiceShiroFilter
org.apache.shiro.guice.web.PathMatchingFilterProvider
org.apache.shiro.guice.web.ShiroWebModule$1
org.apache.shiro.guice.web.ShiroWebModule$FilterConfig
org.apache.shiro.guice.web.ShiroWebModule$FilterConfigKey
org.apache.shiro.guice.web.SimpleFilterChain
org.apache.shiro.guice.web.SimpleFilterChainResolver
org.apache.shiro.guice.web.SimpleFilterChainResolver$1
org.apache.shiro.guice.web.WebGuiceEnvironment
None com.google.inject
com.google.inject.binder
com.google.inject.name
com.google.inject.servlet
com.google.inject.spi
java.io
java.lang
java.lang.reflect
java.util
javax.servlet
org.apache.shiro.config
org.apache.shiro.guice
org.apache.shiro.mgt
org.apache.shiro.util
org.apache.shiro.web.env
org.apache.shiro.web.filter
org.apache.shiro.web.filter.authc
org.apache.shiro.web.filter.authz
org.apache.shiro.web.filter.mgt
org.apache.shiro.web.filter.session
org.apache.shiro.web.mgt
org.apache.shiro.web.servlet
org.apache.shiro.web.session.mgt
org.apache.shiro.web.util

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.