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]

com.amazon.webservices.awseCommerceService.x20041019

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2949%82%31%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

com.amazon.webservices.awseCommerceService.x20041019.impl

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

schema.system.s10726F55DB64F7AC19ABAC602BE0EDE8

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

schema.system.s15E1267FE77F58556D359674445BA5D7

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

schema.system.s162AAB91F94F551CACD901021EDCCD6F

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

schema.system.s3579979AB9685CCF942E6F54C59717AF

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

schema.system.s92B6598D9343B47E9DBD110164078EC5

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

schema.system.sAD878A901945DA42FC1BEFF22A33ABDE

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

schema.system.sDC9E8E9B309165681A3A70EA89A10264

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

schema.system.sFEEA961C625B3A0BC2F8A76C55F9BE57

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

Cycles

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

There are no cyclic dependencies.

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.