Metric Results

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

The following document contains the results of a JDependmetric analysis. The various metrics are defined at the bottom of this document.

Packages

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

org.neo.swarm.core.aop.silc

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
260%75%25%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.core.container

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3450%57%7%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.core.container.pico

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1933%90%23%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.interceptor.appContext

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
160%86%14%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.interceptor.asyncQueue

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
050%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.interceptor.jmx

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
180%89%11%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.interceptor.logging

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
11017%91%8%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.interceptor.sync

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
040%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.interceptor.tcp

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
190%90%10%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.network

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
030%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.services

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
42100%33%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.services.classloader

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0450%100%50%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.services.jxta

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
060%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.services.multicast

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
160%86%14%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.services.tcp

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
01133%100%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.neo.swarm.util.io

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2420%67%13%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.util.network.jrms

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
080%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.util.network.jxta

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
080%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

org.neo.swarm.util.network.multicast

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
5350%38%12%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.util.network.tcp.client

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
4733%64%3%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.neo.swarm.util.threads

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
5250%29%21%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

Cycles

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

PackageCyclic Dependencies
org.neo.swarm
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.config
  • org.neo.swarm.interceptor.jmx
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
org.neo.swarm.core.aop.silc
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.core.container
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.core.container.pico
  • org.neo.swarm.core.aop.silc
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.interceptor.appContext
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.interceptor.asyncQueue
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.interceptor.jmx
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.interceptor.logging
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
org.neo.swarm.interceptor.sync
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.interceptor.tcp
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.services.binding
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.services.classloader
  • org.neo.swarm
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp
org.neo.swarm.services.tcp
  • org.neo.swarm.core.aop.silc.comp
  • org.neo.swarm.core.aop
  • org.neo.swarm.core.aop.silc.comp

Explanations

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