SourceForge.net Logo

Ohloh project report for domingo

Metric Results

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

The following document contains the results of a JDepend metric 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
de.bea.domingo 3626101480,7236%9%
de.bea.domingo.cache 422140,580%30%
de.bea.domingo.exception 312560,3355%12%
de.bea.domingo.groupware 16313180,1989%8%
de.bea.domingo.groupware.map 20119170,0588%7%
de.bea.domingo.http 293260170,1100%10%
de.bea.domingo.i18n 20274036%64%
de.bea.domingo.map 241212260,575%25%
de.bea.domingo.mock 303040100%0%
de.bea.domingo.monitor 1257780,4253%5%
de.bea.domingo.notes 211170,588%38%
de.bea.domingo.proxy 405352130,1287%1%
de.bea.domingo.queue 211240,567%17%
de.bea.domingo.server 1028160,286%6%
de.bea.domingo.service 8080120100%0%
de.bea.domingo.servlet 202070100%0%
de.bea.domingo.threadpool 523160,486%26%
de.bea.domingo.util 1501546060%40%

Packages

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

de.bea.domingo.cache

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1450%80%30%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

de.bea.domingo.exception

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
5633%55%12%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

de.bea.domingo.i18n

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
740%36%64%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

de.bea.domingo.mock

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

de.bea.domingo.notes

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1750%88%38%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

de.bea.domingo.queue

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

de.bea.domingo.servlet

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

de.bea.domingo.threadpool

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1640%86%26%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

Cycles

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

PackageCyclic Dependencies
de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.groupware
  • de.bea.domingo.map
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.groupware.map
  • de.bea.domingo.map
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.http
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.map
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.mock
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.monitor
  • de.bea.domingo
  • de.bea.domingo.monitor
de.bea.domingo.notes
  • de.bea.domingo.monitor
  • de.bea.domingo
  • de.bea.domingo.monitor
de.bea.domingo.proxy
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.queue
  • de.bea.domingo.monitor
  • de.bea.domingo
  • de.bea.domingo.monitor
de.bea.domingo.server
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.service
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.servlet
  • de.bea.domingo.server
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.threadpool
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo
de.bea.domingo.util
  • de.bea.domingo
  • de.bea.domingo.monitor
  • de.bea.domingo

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.