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 Total

Classes
Abstract

Classes
Concrete

Classes
Afferent

Couplings
Efferent

Couplings
Abstractness Instability Distance
org.xpcards 19 0 19 2 16 0 89% 11%
org.xpcards.actions 13 1 12 1 12 0,08 92% 0%
org.xpcards.components 6 0 6 0 8 0 100% 0%
org.xpcards.composites 11 0 11 2 9 0 82% 18%
org.xpcards.dialogs 11 0 11 0 8 0 100% 0%
org.xpcards.model 30 6 24 7 8 0,2 53% 27%
org.xpcards.model.test 1 0 1 0 7 0 100% 0%
org.xpcards.utils 4 1 3 3 3 0,25 50% 25%
org.xpcards.views 9 2 7 1 13 0,22 93% 15%
org.xpcards.wizards 46 1 45 1 16 0,02 94% 4%

Packages

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

org.xpcards.model.test

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 7 0% 100% 0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
ProjectsCollectionTest

java.beans

java.io

java.lang

java.util

junit.framework

junit.textui

org.xpcards.model

org.xpcards.utils

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 3 25% 50% 25%
Abstract Classes Concrete Classes Used by Packages Uses Packages
IIdProvider

EventListenersSupport

IntArray

ResourceBundleHelper

org.xpcards.composites

org.xpcards.model

org.xpcards.wizards

java.lang

java.util

org.eclipse.swt.widgets

org.xpcards.wizards

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 16 2% 94% 4%
Abstract Classes Concrete Classes Used by Packages Uses Packages
ResourceWizardPage

NewIterationWizard

NewIterationWizardLocationPage

NewIterationWizardLocationPage$1

NewIterationWizardLocationPage$2

NewIterationWizardLocationPage$3

NewIterationWizardNewIterationPage

NewIterationWizardNewIterationPage$1

NewIterationWizardNewIterationPage$2

NewProjectWizard

NewProjectWizardImportFilePage

NewProjectWizardImportFilePage$1

NewProjectWizardImportFilePage$2

NewProjectWizardMainPage

NewProjectWizardMainPage$1

NewProjectWizardModel

NewProjectWizardNewFilePage

NewProjectWizardNewFilePage$1

NewProjectWizardNewFilePage$1A

NewProjectWizardNewFilePage$2

NewProjectWizardNewFilePage$3

NewProjectWizardNewProjectPage

NewProjectWizardNewProjectPage$1

NewProjectWizardNewProjectPage$2

NewProjectWizardTestLauncher

NewStoryWizard

NewStoryWizardLocationPage

NewStoryWizardLocationPage$1

NewStoryWizardLocationPage$2

NewStoryWizardLocationPage$3

NewStoryWizardNewStoryPage

NewStoryWizardNewStoryPage$1

NewStoryWizardNewStoryPage$2

NewStoryWizardNewStoryPage$3

NewStoryWizardNewStoryPage$4

NewStoryWizardNewStoryPage$5

NewStoryWizardNewStoryPage$6

NewStoryWizardTestLauncher

NewTaskWizard

NewTaskWizardLocationPage

NewTaskWizardLocationPage$1

NewTaskWizardLocationPage$2

NewTaskWizardLocationPage$3

NewTaskWizardNewTaskPage

NewTaskWizardNewTaskPage$1

NewTaskWizardNewTaskPage$2

org.xpcards.actions

java.io

java.lang

java.util

org.eclipse.jface.dialogs

org.eclipse.jface.resource

org.eclipse.jface.viewers

org.eclipse.jface.window

org.eclipse.jface.wizard

org.eclipse.swt.custom

org.eclipse.swt.events

org.eclipse.swt.graphics

org.eclipse.swt.layout

org.eclipse.swt.widgets

org.xpcards.composites

org.xpcards.model

org.xpcards.utils

Cycles

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

Package Cyclic Dependencies
org.xpcards org.xpcards.actions

org.xpcards

org.xpcards.actions org.xpcards

org.xpcards.actions

org.xpcards.views org.xpcards

org.xpcards.actions

org.xpcards

Explanations

[ summary ] [ packages ] [ cycles ] [ explan ations ]

The following explanations are for quick reference and are lifted directly from the original JDepend documentation .

Term Description
Number of Classes The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent Couplings The number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent Couplings The number of other packages that the classes in the package depend upon is an indicator of the package's independence.
Abstractness The 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.
Instability The 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.
Distance The 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 completel y 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.
Cycles Packages 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.