This project has retired. For details please refer to its Attic page.
jUDDI GUI WAR – JDepend Report Metrics Fork me on GitHub

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.juddi.webconsole 6 5 1 2 11 17.0% 85.0% 1.0% 1
org.apache.juddi.webconsole.hub 7 7 0 1 36 0.0% 97.0% 3.0% 1
org.apache.juddi.webconsole.hub.builders 3 3 0 1 15 0.0% 94.0% 6.0% 1
org.apache.juddi.webconsole.resources 1 1 0 2 3 0.0% 60.000004% 40.0% 1

Packages

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

org.apache.juddi.webconsole

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 11 17.0% 85.0% 1.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.juddi.webconsole.PostBackConstants
org.apache.juddi.webconsole.AES
org.apache.juddi.webconsole.CrossSiteRequestForgeryException
org.apache.juddi.webconsole.NoCacheFilter
org.apache.juddi.webconsole.StartupServlet
org.apache.juddi.webconsole.YesCacheFilter
org.apache.juddi.webconsole.hub
org.apache.juddi.webconsole.hub.builders
java.io
java.lang
java.text
java.util
java.util.logging
javax.crypto
javax.crypto.spec
javax.servlet
javax.servlet.http
org.apache.commons.codec.binary
org.apache.commons.logging

org.apache.juddi.webconsole.hub

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 36 0.0% 97.0% 3.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.juddi.webconsole.hub.PagableContainer
org.apache.juddi.webconsole.hub.UDDIRequestsAsXML
org.apache.juddi.webconsole.hub.UddiHub
org.apache.juddi.webconsole.hub.UddiHub$1
org.apache.juddi.webconsole.hub.UddiHub$AuthStyle
org.apache.juddi.webconsole.hub.UddiHub$CriteriaType
org.apache.juddi.webconsole.hub.UddiHub$FindType
org.apache.juddi.webconsole.hub.builders
java.io
java.lang
java.net
java.rmi
java.security
java.security.cert
java.util
java.util.concurrent.atomic
java.util.logging
javax.servlet
javax.servlet.http
javax.xml
javax.xml.bind
javax.xml.datatype
javax.xml.soap
javax.xml.transform
javax.xml.transform.stream
javax.xml.ws
javax.xml.ws.soap
org.apache.commons.codec.binary
org.apache.commons.configuration
org.apache.commons.lang
org.apache.commons.logging
org.apache.juddi.api_v3
org.apache.juddi.v3.client
org.apache.juddi.v3.client.config
org.apache.juddi.v3.client.cryptor
org.apache.juddi.v3.client.transport
org.apache.juddi.webconsole
org.apache.juddi.webconsole.hub.builders
org.apache.juddi.webconsole.resources
org.uddi.api_v3
org.uddi.custody_v3
org.uddi.sub_v3
org.uddi.v3_service
org.w3._2000._09.xmldsig_

org.apache.juddi.webconsole.hub.builders

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 org.apache.juddi.webconsole.hub.builders.Builders
org.apache.juddi.webconsole.hub.builders.Printers
org.apache.juddi.webconsole.hub.builders.SubscriptionHelper
org.apache.juddi.webconsole.hub
java.lang
java.text
java.util
java.util.concurrent.atomic
java.util.regex
javax.servlet.http
javax.xml.datatype
org.apache.commons.lang
org.apache.commons.logging
org.apache.juddi.webconsole
org.apache.juddi.webconsole.hub
org.apache.juddi.webconsole.resources
org.uddi.api_v3
org.uddi.sub_v3
org.w3._2000._09.xmldsig_

org.apache.juddi.webconsole.resources

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 3 0.0% 60.000004% 40.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.juddi.webconsole.resources.ResourceLoader
org.apache.juddi.webconsole.hub
org.apache.juddi.webconsole.hub.builders
java.lang
java.util
javax.servlet.http

Cycles

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

Package Package Dependencies
org.apache.juddi.webconsole.hub org.apache.juddi.webconsole.hub.builders
org.apache.juddi.webconsole.hub
org.apache.juddi.webconsole.hub.builders org.apache.juddi.webconsole.hub
org.apache.juddi.webconsole.hub.builders

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.