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
aigames.soccer 20232040%60%
aigames.soccer.application 7070170100%0%
aigames.soccer.communication 2020140100%0%
aigames.soccer.field 312360,3367%0%
aigames.soccer.field.constructor 211340,557%7%
aigames.soccer.observer 110110170100%0%
snifos 101040100%0%
snifos.application 211360,567%17%
snifos.application.test 1010100100%0%
snifos.common 10181011%89%
snifos.common.test 11021133%33%
snifos.communication 211370,570%20%
snifos.communication.test 1010120100%0%
snifos.exception 30361014%86%
snifos.server 2118120,560%10%
snifos.server.test 101040100%0%

Packages

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

aigames.soccer

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

aigames.soccer.communication

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

aigames.soccer.field

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3633%67%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

aigames.soccer.field.constructor

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

snifos

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

snifos.application

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3650%67%17%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

snifos.application.test

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

snifos.common

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

snifos.common.test

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

snifos.communication

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

snifos.communication.test

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

snifos.exception

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

snifos.server.test

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

Cycles

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

PackageCyclic Dependencies
aigames.soccer.application
  • snifos.server
  • snifos.application
  • snifos.server
aigames.soccer.communication
  • snifos.server
  • snifos.application
  • snifos.server
aigames.soccer.field
  • aigames.soccer.field.constructor
  • aigames.soccer.field
aigames.soccer.field.constructor
  • aigames.soccer.field
  • aigames.soccer.field.constructor
aigames.soccer.observer
  • aigames.soccer.field
  • aigames.soccer.field.constructor
  • aigames.soccer.field
snifos
  • snifos.server
  • snifos.application
  • snifos.server
snifos.application
  • snifos.server
  • snifos.application
snifos.application.test
  • snifos.server
  • snifos.application
  • snifos.server
snifos.communication
  • snifos.server
  • snifos.application
  • snifos.server
snifos.communication.test
  • snifos.server
  • snifos.application
  • snifos.server
snifos.server
  • snifos.application
  • snifos.server
snifos.server.test
  • snifos.server
  • snifos.application
  • snifos.server

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.