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.apache.fulcrum.security 13678100.4656%2%
org.apache.fulcrum.security.acl 211530.538%12%
org.apache.fulcrum.security.authenticator 514190.290%10%
org.apache.fulcrum.security.entity 550192110%10%
org.apache.fulcrum.security.entity.impl 10133050%50%
org.apache.fulcrum.security.model 211330.550%0%
org.apache.fulcrum.security.model.basic 422190.590%40%
org.apache.fulcrum.security.model.basic.entity 22044150%50%
org.apache.fulcrum.security.model.basic.entity.impl 20217088%12%
org.apache.fulcrum.security.model.basic.test 110081100%100%
org.apache.fulcrum.security.model.dynamic 5322100.683%43%
org.apache.fulcrum.security.model.dynamic.entity 44045156%56%
org.apache.fulcrum.security.model.dynamic.entity.impl 404060100%0%
org.apache.fulcrum.security.model.dynamic.test 110081100%100%
org.apache.fulcrum.security.model.test 440071100%100%
org.apache.fulcrum.security.model.turbine 33017188%88%
org.apache.fulcrum.security.model.turbine.entity 642360.6767%33%
org.apache.fulcrum.security.model.turbine.entity.impl 404070100%0%
org.apache.fulcrum.security.model.turbine.test 110081100%100%
org.apache.fulcrum.security.password 101020100%0%
org.apache.fulcrum.security.session 330011100%100%
org.apache.fulcrum.security.spi 660313181%81%
org.apache.fulcrum.security.util 10191750.123%67%

Packages

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

org.apache.fulcrum.security

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
81046%56%2%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.apache.fulcrum.security.acl

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

org.apache.fulcrum.security.authenticator

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

org.apache.fulcrum.security.entity

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

org.apache.fulcrum.security.entity.impl

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

org.apache.fulcrum.security.model

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3350%50%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.apache.fulcrum.security.model.basic

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1950%90%40%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.apache.fulcrum.security.model.basic.entity

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

org.apache.fulcrum.security.model.basic.entity.impl

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
170%88%12%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.apache.fulcrum.security.model.basic.test

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

org.apache.fulcrum.security.model.dynamic

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21060%83%43%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.apache.fulcrum.security.model.dynamic.entity

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
45100%56%56%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.apache.fulcrum.security.model.dynamic.entity.impl

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

org.apache.fulcrum.security.model.dynamic.test

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

org.apache.fulcrum.security.model.test

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

org.apache.fulcrum.security.model.turbine

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
17100%88%88%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.apache.fulcrum.security.model.turbine.entity

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3667%67%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

org.apache.fulcrum.security.model.turbine.entity.impl

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

org.apache.fulcrum.security.model.turbine.test

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

org.apache.fulcrum.security.password

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

org.apache.fulcrum.security.session

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

org.apache.fulcrum.security.spi

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
313100%81%81%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

org.apache.fulcrum.security.util

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
17510%23%67%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

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.