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 ]

PackageTCCCACCaCeAIDV
nl.gridshore.samples.raffle.web.wicket5501110.0%92.0%8.0%1
nl.gridshore.samples.raffle.web.wicket.raffle313011123.0%92.0%4.0%1

Packages

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

nl.gridshore.samples.raffle.web.wicket

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1110.0%92.0%8.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenl.gridshore.samples.raffle.web.wicket.BasePage
nl.gridshore.samples.raffle.web.wicket.BasePage$1
nl.gridshore.samples.raffle.web.wicket.HomePage
nl.gridshore.samples.raffle.web.wicket.MenuItem
nl.gridshore.samples.raffle.web.wicket.RaffleWicketApplication
nl.gridshore.samples.raffle.web.wicket.raffle
java.io
java.lang
java.util
nl.gridshore.samples.raffle.business
nl.gridshore.samples.raffle.web.wicket.raffle
org.apache.wicket.markup.html
org.apache.wicket.markup.html.basic
org.apache.wicket.markup.html.link
org.apache.wicket.markup.html.list
org.apache.wicket.protocol.http
org.apache.wicket.spring.injection.annot

nl.gridshore.samples.raffle.web.wicket.raffle

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1123.0%92.0%4.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
nl.gridshore.samples.raffle.web.wicket.raffle.RaffleConstants
nl.gridshore.samples.raffle.web.wicket.raffle.AllRafflesPage
nl.gridshore.samples.raffle.web.wicket.raffle.AllRafflesPage$1
nl.gridshore.samples.raffle.web.wicket.raffle.AllRafflesPage$2
nl.gridshore.samples.raffle.web.wicket.raffle.AllRafflesPage$3
nl.gridshore.samples.raffle.web.wicket.raffle.DeleteRafflePage
nl.gridshore.samples.raffle.web.wicket.raffle.DeleteRafflePage$1
nl.gridshore.samples.raffle.web.wicket.raffle.DeleteRafflePage$2
nl.gridshore.samples.raffle.web.wicket.raffle.DeleteRafflePage$3
nl.gridshore.samples.raffle.web.wicket.raffle.DoTheRafflePage
nl.gridshore.samples.raffle.web.wicket.raffle.DoTheRafflePage$1
nl.gridshore.samples.raffle.web.wicket.raffle.DoTheRafflePage$1$1
nl.gridshore.samples.raffle.web.wicket.raffle.DoTheRafflePage$ChooseRaffleForm
nl.gridshore.samples.raffle.web.wicket.raffle.DoTheRafflePage$ChooseRaffleFormModel
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$ParticipantForm
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$ParticipantForm$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$ParticipantsListView
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$ParticipantsListView$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$PrizeForm
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$PrizeForm$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$PrizesListView
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$PrizesListView$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$RaffleForm
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$RaffleForm$1
nl.gridshore.samples.raffle.web.wicket.raffle.EditRafflePage$RaffleForm$2
nl.gridshore.samples.raffle.web.wicket.raffle.ViewRafflePage
nl.gridshore.samples.raffle.web.wicket.raffle.ViewRafflePage$1
nl.gridshore.samples.raffle.web.wicket.raffle.ViewRafflePage$2
nl.gridshore.samples.raffle.web.wicket.raffle.ViewRafflePage$3
nl.gridshore.samples.raffle.web.wicket
java.io
java.lang
java.util
nl.gridshore.samples.raffle.business
nl.gridshore.samples.raffle.domain
nl.gridshore.samples.raffle.web.wicket
org.apache.wicket
org.apache.wicket.markup.html.basic
org.apache.wicket.markup.html.form
org.apache.wicket.markup.html.link
org.apache.wicket.markup.html.list
org.apache.wicket.model

Cycles

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

PackagePackage Dependencies
nl.gridshore.samples.raffle.web.wicketnl.gridshore.samples.raffle.web.wicket.raffle
nl.gridshore.samples.raffle.web.wicket
nl.gridshore.samples.raffle.web.wicket.rafflenl.gridshore.samples.raffle.web.wicket
nl.gridshore.samples.raffle.web.wicket.raffle

Explanation

[ 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.