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.sf.jmorse 7 5 2 3 5 29.0% 62.0% 9.0% 1
net.sf.jmorse.ant 1 1 0 0 3 0.0% 100.0% 0.0% 1
net.sf.jmorse.log4j 1 1 0 0 3 0.0% 100.0% 0.0% 1
net.sf.jmorse.logging 2 2 0 0 3 0.0% 100.0% 0.0% 1
net.sf.jmorse.util.logging 1 1 0 1 2 0.0% 67.0% 33.0% 1

Packages

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

net.sf.jmorse

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 5 29.0% 62.0% 9.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
net.sf.jmorse.AbstractMorseWriter
net.sf.jmorse.MorseWriter
 net.sf.jmorse.AudioMorseWriter
net.sf.jmorse.JMorse
net.sf.jmorse.MorseAudioFileWriter
net.sf.jmorse.MorseBeep
net.sf.jmorse.MorseUtil
 net.sf.jmorse.ant
net.sf.jmorse.log4j
net.sf.jmorse.logging
 java.io
java.lang
java.util
javax.sound.sampled
net.sf.jmorse.util.logging

net.sf.jmorse.ant

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 net.sf.jmorse.ant.MorseTask
 None java.lang
net.sf.jmorse
org.apache.tools.ant

net.sf.jmorse.log4j

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 net.sf.jmorse.log4j.AudioMorseAppender
 None net.sf.jmorse
org.apache.log4j
org.apache.log4j.spi

net.sf.jmorse.logging

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 net.sf.jmorse.logging.AudioMorseHandler
net.sf.jmorse.logging.AudioMorseHandler$PassThroughFormatter
 None java.lang
java.util.logging
net.sf.jmorse

net.sf.jmorse.util.logging

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 net.sf.jmorse.util.logging.Logger
 net.sf.jmorse
 java.lang
java.util.logging

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.