[ 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
io.fixture.controller 7 7 0 0 7 0.0% 100.0% 0.0% 1
io.fixture.controller.form 1 1 0 1 2 0.0% 67.0% 33.0% 1
io.fixture.domain 6 6 0 2 5 0.0% 71.0% 29.0% 1
io.fixture.interceptor 2 2 0 0 11 0.0% 100.0% 0.0% 1
io.fixture.repository 8 4 4 1 5 50.0% 83.0% 33.0% 1
io.fixture.security 10 10 0 0 15 0.0% 100.0% 0.0% 1

Packages

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

io.fixture.controller

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 io.fixture.controller.AdministrationController
io.fixture.controller.RegistrationController
io.fixture.controller.SecureController
io.fixture.controller.StaticController
io.fixture.controller.ValidationController
io.fixture.controller.ValidationController$handleValidationError$1
io.fixture.controller.ValidationController$handleValidationError$1$1
None io.fixture.controller.form
java.lang
java.util
jet
kotlin
org.springframework.validation
org.springframework.web.bind

io.fixture.controller.form

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 0.0% 67.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None io.fixture.controller.form.RegistrationForm
io.fixture.controller
java.lang
jet

io.fixture.domain

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 5 0.0% 71.0% 29.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None io.fixture.domain.BasePersistable
io.fixture.domain.Group
io.fixture.domain.PersistentLogin
io.fixture.domain.User
io.fixture.domain.User$TokenType
io.fixture.domain.UserProfile
io.fixture.repository
io.fixture.security
java.io
java.lang
java.util
jet
org.springframework.data.domain

io.fixture.interceptor

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 io.fixture.interceptor.NextThemeInterceptor
io.fixture.interceptor.NextThemeInterceptor$unsorted$1
None java.lang
java.util
javax.servlet.http
jet
jet.runtime
kotlin
org.springframework.core.io
org.springframework.core.io.support
org.springframework.web.servlet
org.springframework.web.servlet.handler
org.springframework.web.servlet.support

io.fixture.repository

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 5 50.0% 83.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
io.fixture.repository.GroupRepository
io.fixture.repository.PersistentLoginRepository
io.fixture.repository.UserProfileRepository
io.fixture.repository.UserRepository
io.fixture.repository.GroupRepository$$TImpl
io.fixture.repository.PersistentLoginRepository$$TImpl
io.fixture.repository.UserProfileRepository$$TImpl
io.fixture.repository.UserRepository$$TImpl
io.fixture.security
io.fixture.domain
java.lang
java.util
jet
org.springframework.data.jpa.repository

io.fixture.security

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 15 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None io.fixture.security.GroupManagerImpl
io.fixture.security.GroupManagerImpl$addGroupAuthority$1
io.fixture.security.GroupManagerImpl$createGroup$1
io.fixture.security.GroupManagerImpl$findGroupAuthorities$1
io.fixture.security.GroupManagerImpl$removeGroupAuthority$1
io.fixture.security.PersistentTokenRepositoryImpl
io.fixture.security.UserDetailsManagerImpl
io.fixture.security.UserDetailsManagerImpl$createUser$1
io.fixture.security.UserDetailsManagerImpl$toUserDetails$1
io.fixture.security.UserDetailsManagerImpl$updateUser$1
None io.fixture.domain
io.fixture.repository
java.lang
java.util
jet
jet.runtime
kotlin
org.springframework.security.access
org.springframework.security.authentication
org.springframework.security.core
org.springframework.security.core.authority
org.springframework.security.core.context
org.springframework.security.core.userdetails
org.springframework.security.provisioning
org.springframework.security.web.authentication.rememberme

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.

Back to top

Version: 0.1-SNAPSHOT. Last Published: 2013-07-17.