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
cn.home1.oss.lib.webmvc.api 12 9 3 2 12 25.0% 86.0% 11.0% 1
cn.home1.oss.lib.webmvc.internal 3 3 0 1 15 0.0% 94.0% 6.0% 1
cn.home1.oss.lib.webmvc.starter 3 3 0 0 11 0.0% 100.0% 0.0% 1
org.springframework.http.converter 1 1 0 1 6 0.0% 86.0% 14.0% 1
org.springframework.web 1 1 0 1 14 0.0% 93.0% 7.0% 1

Packages

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

cn.home1.oss.lib.webmvc.api

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 12 25.0% 86.0% 11.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
cn.home1.oss.lib.webmvc.api.DomainResolver
cn.home1.oss.lib.webmvc.api.RequestResolver
cn.home1.oss.lib.webmvc.api.TypeSafeToken
cn.home1.oss.lib.webmvc.api.Jetty9ServerCustomizers$1
cn.home1.oss.lib.webmvc.api.Jetty9ServerCustomizers$NullSessionIdManager
cn.home1.oss.lib.webmvc.api.Jetty9ServerCustomizers$Pool
cn.home1.oss.lib.webmvc.api.JsonToken
cn.home1.oss.lib.webmvc.api.JsonWebToken
cn.home1.oss.lib.webmvc.api.SecureToken
cn.home1.oss.lib.webmvc.api.StringToken
cn.home1.oss.lib.webmvc.api.TokenBasedCookie
cn.home1.oss.lib.webmvc.api.UrlEncodedToken
cn.home1.oss.lib.webmvc.internal
cn.home1.oss.lib.webmvc.starter
cn.home1.oss.lib.common
cn.home1.oss.lib.common.crypto
com.fasterxml.jackson.databind
com.google.common.base
java.lang
java.util.function
javax.servlet.http
org.apache.commons.lang3
org.eclipse.jetty.server
org.eclipse.jetty.util.thread
org.slf4j
org.springframework.boot.context.embedded.jetty

cn.home1.oss.lib.webmvc.internal

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 15 0.0% 94.0% 6.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None cn.home1.oss.lib.webmvc.internal.DefaultDomainResolver
cn.home1.oss.lib.webmvc.internal.DefaultHttpEntityMethodProcessor
cn.home1.oss.lib.webmvc.internal.DefaultRequestResolver
cn.home1.oss.lib.webmvc.starter
cn.home1.oss.lib.webmvc.api
java.lang
java.util
javax.servlet.http
org.apache.commons.lang3
org.slf4j
org.springframework.beans.factory
org.springframework.core
org.springframework.core.env
org.springframework.http
org.springframework.web
org.springframework.web.accept
org.springframework.web.context.request
org.springframework.web.method.support
org.springframework.web.servlet.mvc.method.annotation

cn.home1.oss.lib.webmvc.starter

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 11 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None cn.home1.oss.lib.webmvc.starter.GsonConfiguration
cn.home1.oss.lib.webmvc.starter.Jackson2Configuration
cn.home1.oss.lib.webmvc.starter.WebApplicationAutoConfiguration
None cn.home1.oss.boot.autoconfigure
cn.home1.oss.lib.common
cn.home1.oss.lib.webmvc.api
cn.home1.oss.lib.webmvc.internal
com.fasterxml.jackson.databind
com.google.gson
java.lang
org.apache.commons.lang3
org.springframework.boot.autoconfigure.web
org.springframework.core.env
org.springframework.web.servlet.config.annotation

org.springframework.http.converter

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 6 0.0% 86.0% 14.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.springframework.http.converter.Utf8StringHttpMessageConverter
org.springframework.web
com.google.common.base
com.google.common.collect
java.nio.charset
java.util
org.slf4j
org.springframework.http

org.springframework.web

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 14 0.0% 93.0% 7.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.springframework.web.HttpMessageConverterUtils
cn.home1.oss.lib.webmvc.internal
cn.home1.oss.lib.common
com.fasterxml.jackson.databind
com.google.common.collect
java.lang
java.nio.charset
java.util
org.slf4j
org.springframework.core.env
org.springframework.http
org.springframework.http.converter
org.springframework.http.converter.json
org.springframework.http.converter.xml
org.springframework.util
org.springframework.web.accept

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.