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 Total

Classes
Abstract

Classes
Concrete

Classes
Afferent

Couplings
Efferent

Couplings
Abstractness Instability Distance
juju.reattore 1 0 1 0 6 0 100% 0%
juju.reattore.core.reactor 6 6 0 3 4 1 57% 57%
juju.reattore.core.reactor.impl 1 0 1 3 9 0 75% 25%
juju.reattore.core.rr 2 2 0 0 1 1 100% 100%
juju.reattore.io 8 8 0 5 3 1 38% 38%
juju.reattore.io.impl 6 0 6 3 8 0 73% 27%
juju.reattore.loadtest 1 0 1 0 6 0 100% 0%
juju.reattore.loadtest.controller 2 2 0 1 2 1 67% 67%
juju.reattore.loadtest.controller.impl 3 0 3 1 10 0 91% 9%
juju.reattore.perfcap 1 0 1 1 10 0 91% 9%
juju.reattore.perfcap.reporter 1 1 0 2 3 1 60% 60%
juju.reattore.perfcap.reporter.impl 3 0 3 0 12 0 100% 0%
juju.reattore.perfcap.tester 2 2 0 4 2 1 33% 33%
juju.reattore.perfcap.tester.impl 3 0 3 0 11 0 100% 0%
juju.reattore.perfcap.var 1 1 0 4 1 1 20% 20%
juju.reattore.perfcap.var.impl 3 0 3 0 6 0 100% 0%
juju.reattore.protocol.http 7 6 1 4 4 0.86 50% 36%
juju.reattore.protocol.http.impl 7 0 7 1 8 0 89% 11%
juju.reattore.server.http 4 0 4 0 15 0 100% 0%
juju.reattore.server.intercept 2 2 0 2 2 1 50% 50%
juju.reattore.server.intercept.impl 12 0 12 0 13 0 100% 0%
juju.reattore.util 15 2 13 9 9 0.13 50% 37%

Packages

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

juju.reattore

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Reattore

java.io

java.lang

juju.reattore.core.reactor.impl

org.apache.commons.digester

org.apache.commons.digester.xmlrules

org.apache.commons.logging

juju.reattore.core.rr

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 1 100% 100% 100%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Request

Response

java.lang

juju.reattore.loadtest

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
LoadTest

java.io

java.lang

java.net

juju.reattore.core.reactor.impl

juju.reattore.loadtest.controller.impl

org.apache.commons.logging

juju.reattore.loadtest.controller

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 100% 67% 67%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Chooser

Controller

juju.reattore.loadtest.controller.impl

java.lang

java.net

juju.reattore.perfcap.reporter

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 3 100% 60% 60%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Reporter

juju.reattore.perfcap

juju.reattore.perfcap.reporter.impl

java.lang

java.util

juju.reattore.perfcap.tester

juju.reattore.perfcap.tester

Afferent Couplings Efferent Couplings Abstractness Instability Distance
4 2 100% 33% 33%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Results

Tester

juju.reattore.perfcap

juju.reattore.perfcap.reporter

juju.reattore.perfcap.reporter.impl

juju.reattore.perfcap.tester.impl

java.io

java.lang

juju.reattore.perfcap.var

Afferent Couplings Efferent Couplings Abstractness Instability Distance
4 1 100% 20% 20%
Abstract Classes Concrete Classes Used by Packages Uses Packages
Variable

juju.reattore.perfcap

juju.reattore.perfcap.reporter.impl

juju.reattore.perfcap.tester.impl

juju.reattore.perfcap.var.impl

java.lang

juju.reattore.perfcap.var.impl

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
CommandLineVar

ListVar

RangeVar

java.lang

java.util

java.util.regex

juju.reattore.perfcap.var

juju.reattore.util

org.apache.commons.logging

juju.reattore.server.intercept

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 2 100% 50% 50%
Abstract Classes Concrete Classes Used by Packages Uses Packages
CachableInterceptor

Interceptor

juju.reattore.server.http

juju.reattore.server.intercept.impl

java.lang

juju.reattore.protocol.http

Cycles

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

There are no cyclic dependancies.

Explanations

[ 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.