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 ]

PackageTCCCACCaCeAIDV
org.bitrepository220190.0%90.0%10.0%1
org.bitrepository.dashboard141400110.0%100.0%0.0%1
org.bitrepository.utils330180.0%89.0%11.0%1
org.bitrepository.webservice6602110.0%85.0%15.000001%1

Packages

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

org.bitrepository

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
190.0%90.0%10.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.BasicClient
org.bitrepository.BasicClientFactory
org.bitrepository.webservice
java.io
java.lang
java.util
javax.jms
org.bitrepository.common.settings
org.bitrepository.protocol.messagebus
org.bitrepository.settings.repositorysettings
org.bitrepository.webservice
org.slf4j

org.bitrepository.dashboard

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0110.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.dashboard.DashboardDataCache
org.bitrepository.dashboard.DashboardServlet
org.bitrepository.dashboard.GetCollectionInformation
org.bitrepository.dashboard.GetIntegrityStatus
org.bitrepository.dashboard.GetWorkflowSetup
org.bitrepository.dashboard.IntegrityClient
org.bitrepository.dashboard.IntegrityClient$1
org.bitrepository.dashboard.IntegrityClient$2
org.bitrepository.dashboard.IntegrityClient$3
org.bitrepository.dashboard.IntegrityClient$4
org.bitrepository.dashboard.IntegrityClient$5
org.bitrepository.dashboard.IntegrityClient$6
org.bitrepository.dashboard.IntegrityClient$7
org.bitrepository.dashboard.IntegrityClient$8
Nonecom.google.gson
com.google.gson.reflect
com.sun.jersey.api.client
java.io
java.lang
java.util
javax.servlet
javax.servlet.http
org.bitrepository.common.webobjects
org.bitrepository.webservice
org.slf4j

org.bitrepository.utils

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
180.0%89.0%11.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.utils.HexUtils
org.bitrepository.utils.LogbackConfigLoader
org.bitrepository.utils.XMLGregorianCalendarConverter
org.bitrepository.webservice
ch.qos.logback.classic
ch.qos.logback.classic.joran
ch.qos.logback.core.joran.spi
java.io
java.lang
java.util
javax.xml.datatype
org.slf4j

org.bitrepository.webservice

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2110.0%85.0%15.000001%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.webservice.Reposervice
org.bitrepository.webservice.ServiceUrl
org.bitrepository.webservice.ServiceUrlFactory
org.bitrepository.webservice.WebclientContextListener
org.bitrepository.webservice.WebserviceIllegalArgumentException
org.bitrepository.webservice.WebserviceInputChecker
org.bitrepository
org.bitrepository.dashboard
java.io
java.lang
java.net
java.util
javax.servlet
javax.ws.rs
javax.ws.rs.core
org.bitrepository
org.bitrepository.utils
org.json
org.slf4j

Cycles

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

PackagePackage Dependencies
org.bitrepositoryorg.bitrepository.webservice
org.bitrepository
org.bitrepository.dashboardorg.bitrepository.webservice
org.bitrepository
org.bitrepository.webservice
org.bitrepository.webserviceorg.bitrepository
org.bitrepository.webservice

Explanation

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

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

TermDescription
Number of ClassesThe number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent CouplingsThe number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent CouplingsThe number of other packages that the classes in the package depend upon is an indicator of the package's independence.
AbstractnessThe 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.
InstabilityThe 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.
DistanceThe 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.
CyclesPackages 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.