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
de.smartics.ci.comm 7 7 0 3 8 0.0% 73.0% 27.000002% 1
de.smartics.ci.comm.command 16 5 11 2 7 69.0% 78.0% 47.0% 1
de.smartics.ci.comm.hudson 1 1 0 0 3 0.0% 100.0% 0.0% 1
de.smartics.ci.comm.hudson.command 9 8 1 2 13 11.0% 87.0% 2.0% 1

Packages

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

de.smartics.ci.comm

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 8 0.0% 73.0% 27.000002%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None de.smartics.ci.comm.CiController
de.smartics.ci.comm.CiSystem
de.smartics.ci.comm.Credentials
de.smartics.ci.comm.LogHelper
de.smartics.ci.comm.LogLevel
de.smartics.ci.comm.ProxyCredentials
de.smartics.ci.comm.ProxyInformation
de.smartics.ci.comm.command
de.smartics.ci.comm.hudson
de.smartics.ci.comm.hudson.command
de.smartics.ci.comm.command
de.smartics.ci.comm.hudson.command
java.io
java.lang
java.util
org.apache.commons.httpclient
org.apache.commons.lang
org.slf4j

de.smartics.ci.comm.command

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 7 69.0% 78.0% 47.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
de.smartics.ci.comm.command.AbstractCheckStatusJobCommand
de.smartics.ci.comm.command.AbstractCommand
de.smartics.ci.comm.command.AbstractCreateJobCommand
de.smartics.ci.comm.command.AbstractDeleteJobCommand
de.smartics.ci.comm.command.AbstractDisableJobCommand
de.smartics.ci.comm.command.AbstractEnableJobCommand
de.smartics.ci.comm.command.AbstractGenericJobCommand
de.smartics.ci.comm.command.AbstractJobCommand
de.smartics.ci.comm.command.AbstractLoginCommand
de.smartics.ci.comm.command.AbstractUpdateJobCommand
de.smartics.ci.comm.command.Command
de.smartics.ci.comm.command.CommandException
de.smartics.ci.comm.command.CommandResult
de.smartics.ci.comm.command.CommandResult$HttpStatus
de.smartics.ci.comm.command.InvalidRequestException
de.smartics.ci.comm.command.LoginCommandException
de.smartics.ci.comm
de.smartics.ci.comm.hudson.command
de.smartics.ci.comm
java.io
java.lang
java.util
org.apache.commons.httpclient
org.apache.commons.lang
org.slf4j

de.smartics.ci.comm.hudson

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 3 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None de.smartics.ci.comm.hudson.HudsonCiSystemFactory
None de.smartics.ci.comm
de.smartics.ci.comm.hudson.command
java.lang

de.smartics.ci.comm.hudson.command

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 13 11.0% 87.0% 2.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
de.smartics.ci.comm.hudson.command.AbstractHudsonApiJob
de.smartics.ci.comm.hudson.command.HudsonCheckStatusJobCommand
de.smartics.ci.comm.hudson.command.HudsonCreateJobCommand
de.smartics.ci.comm.hudson.command.HudsonDeleteJobCommand
de.smartics.ci.comm.hudson.command.HudsonDisableJobCommand
de.smartics.ci.comm.hudson.command.HudsonEnableJobCommand
de.smartics.ci.comm.hudson.command.HudsonGenericJobCommand
de.smartics.ci.comm.hudson.command.HudsonLoginCommand
de.smartics.ci.comm.hudson.command.HudsonUpdateJobCommand
de.smartics.ci.comm
de.smartics.ci.comm.hudson
de.smartics.ci.comm
de.smartics.ci.comm.command
java.io
java.lang
java.util
java.util.regex
org.apache.commons.httpclient
org.apache.commons.httpclient.auth
org.apache.commons.httpclient.methods
org.apache.commons.httpclient.util
org.apache.commons.io
org.apache.commons.lang
org.slf4j

Cycles

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

Package Package Dependencies
de.smartics.ci.comm de.smartics.ci.comm.command
de.smartics.ci.comm
de.smartics.ci.comm.command de.smartics.ci.comm
de.smartics.ci.comm.command
de.smartics.ci.comm.hudson de.smartics.ci.comm
de.smartics.ci.comm.command
de.smartics.ci.comm
de.smartics.ci.comm.hudson.command de.smartics.ci.comm
de.smartics.ci.comm.command
de.smartics.ci.comm

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.