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
net.truelicense.core 16 15 1 0 12 6.0% 100.0% 6.0% 1
net.truelicense.core.auth 6 6 0 0 13 0.0% 100.0% 0.0% 1
net.truelicense.core.crypto 1 0 1 0 9 100.0% 100.0% 100.0% 1
net.truelicense.core.misc 1 1 0 0 2 0.0% 100.0% 0.0% 1
net.truelicense.core.passwd 4 4 0 0 4 0.0% 100.0% 0.0% 1

Packages

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

net.truelicense.core

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 12 6.0% 100.0% 6.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseManagerBuilder
net.truelicense.core.Cache
net.truelicense.core.Messages
net.truelicense.core.TrueLicenseApplicationContext$1
net.truelicense.core.TrueLicenseApplicationContext$CheckedPasswordProtection
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$ConsumerTrueLicenseManagerBuilder
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$ConsumerTrueLicenseManagerBuilder$ParentConsumerTrueLicenseManagerBuilder
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseInitialization
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseManagementParameters$CachingTrueLicenseManager
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseManagementParameters$ChainedTrueLicenseManager
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseManagerBuilder$TrueAuthenticationBuilder
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseManagerBuilder$TrueEncryptionBuilder
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$TrueLicenseValidation
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContext$VendorTrueLicenseManagerBuilder
net.truelicense.core.TrueLicenseApplicationContext$TrueLicenseManagementContextBuilder
net.truelicense.core.TrueLicenseManagementAuthorization
None java.lang
java.nio.file
java.util
javax.security.auth.x500
net.truelicense.api
net.truelicense.api.auth
net.truelicense.api.codec
net.truelicense.api.i18n
net.truelicense.api.io
net.truelicense.api.misc
net.truelicense.api.passwd
net.truelicense.spi.i18n

net.truelicense.core.auth

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 13 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None net.truelicense.core.auth.Messages
net.truelicense.core.auth.Notary
net.truelicense.core.auth.Notary$1
net.truelicense.core.auth.Notary$Cache
net.truelicense.core.auth.Notary$Cache$1
net.truelicense.core.auth.NotaryException
None java.io
java.lang
java.security
java.security.cert
java.util
java.util.logging
net.truelicense.api.auth
net.truelicense.api.codec
net.truelicense.api.i18n
net.truelicense.api.io
net.truelicense.api.passwd
net.truelicense.obfuscate
net.truelicense.spi.i18n

net.truelicense.core.crypto

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 100.0% 100.0% 100.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
net.truelicense.core.crypto.BasicEncryption
None None java.io
java.lang
java.util
java.util.concurrent
javax.crypto
javax.crypto.spec
net.truelicense.api.crypto
net.truelicense.api.io
net.truelicense.api.passwd

net.truelicense.core.misc

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 2 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None net.truelicense.core.misc.Strings
None java.lang
java.util

net.truelicense.core.passwd

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 4 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None net.truelicense.core.passwd.MinimumPasswordPolicy
net.truelicense.core.passwd.ObfuscatedPasswordProtection
net.truelicense.core.passwd.ObfuscatedPasswordProtection$1
net.truelicense.core.passwd.ObfuscatedPasswordProtection$ObfuscatedPassword
None java.lang
java.util
net.truelicense.api.passwd
net.truelicense.obfuscate

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.