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.

Summary

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

Package TC AC CC AC EC A I D
org.codehaus.xfire 7258130.2962%10%
org.codehaus.xfire.attachments 422370.570%20%
org.codehaus.xfire.client 33014180%80%
org.codehaus.xfire.client.http 312060.33100%33%
org.codehaus.xfire.fault 7167100.1459%27%
org.codehaus.xfire.handler 6333120.580%30%
org.codehaus.xfire.service 6248100.3356%11%
org.codehaus.xfire.service.event 11022150%50%
org.codehaus.xfire.soap 514630.233%47%
org.codehaus.xfire.test 2200141100%100%
org.codehaus.xfire.transport 6424140.6778%44%
org.codehaus.xfire.transport.http 5050140100%0%
org.codehaus.xfire.util 606214088%12%
org.codehaus.xfire.wsdl 321370.6770%37%
org.codehaus.xfire.wsdl11 11023160%60%

Packages

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

org.codehaus.xfire.attachments

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3750%70%20%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.codehaus.xfire.client

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
14100%80%80%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.codehaus.xfire.client.http

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

org.codehaus.xfire.service.event

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

org.codehaus.xfire.soap

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
6320%33%47%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.codehaus.xfire.test

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

org.codehaus.xfire.wsdl

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3767%70%37%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.codehaus.xfire.wsdl11

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
23100%60%60%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

Cycles

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

PackageCyclic Dependencies
org.codehaus.xfire
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.attachments
  • org.codehaus.xfire
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.client
  • org.codehaus.xfire.attachments
  • org.codehaus.xfire
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.client.http
  • org.codehaus.xfire.fault
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.fault
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.handler
  • org.codehaus.xfire.fault
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
org.codehaus.xfire.test
  • org.codehaus.xfire
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.transport
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.transport.http
  • org.codehaus.xfire.fault
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.util
  • org.codehaus.xfire
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service
org.codehaus.xfire.wsdl11
  • org.codehaus.xfire.service
  • org.codehaus.xfire.service.event
  • org.codehaus.xfire.service

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.