SuperSearch - JDepend Source Code Analysis

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
net.sf.supersearch	2	1	1	3	3	50%	50%	0%
net.sf.supersearch.actions	1	0	1	0	11	0%	100%	0%
net.sf.supersearch.preferences	1	0	1	0	5	0%	100%	0%
net.sf.supersearch.util	1	0	1	0	0	0%	0%	100%
net.sf.supersearch.views	3	0	3	1	14	0%	93%	7%
com.grandrapid.component	No stats available: package referenced, but not analyzed.
org.eclipse.core.resources	No stats available: package referenced, but not analyzed.
org.eclipse.core.runtime	No stats available: package referenced, but not analyzed.
org.eclipse.jdt.internal.ui	No stats available: package referenced, but not analyzed.
org.eclipse.jface.action	No stats available: package referenced, but not analyzed.
org.eclipse.jface.preference	No stats available: package referenced, but not analyzed.
org.eclipse.jface.resource	No stats available: package referenced, but not analyzed.
org.eclipse.jface.text	No stats available: package referenced, but not analyzed.
org.eclipse.jface.util	No stats available: package referenced, but not analyzed.
org.eclipse.jface.viewers	No stats available: package referenced, but not analyzed.
org.eclipse.swt.events	No stats available: package referenced, but not analyzed.
org.eclipse.swt.layout	No stats available: package referenced, but not analyzed.
org.eclipse.swt.widgets	No stats available: package referenced, but not analyzed.
org.eclipse.ui	No stats available: package referenced, but not analyzed.
org.eclipse.ui.part	No stats available: package referenced, but not analyzed.
org.eclipse.ui.plugin	No stats available: package referenced, but not analyzed.
s	No stats available: package referenced, but not analyzed.

Packages

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

net.sf.supersearch

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
3	3	50%	50%	0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
SuperSearchConstants	SuperSearchPlugin	net.sf.supersearch.actions net.sf.supersearch.preferences net.sf.supersearch.views	org.eclipse.core.resources org.eclipse.core.runtime org.eclipse.ui.plugin

net.sf.supersearch.actions

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	11	0%	100%	0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	UpdateSearchAction	None	net.sf.supersearch net.sf.supersearch.views org.eclipse.core.runtime org.eclipse.jdt.internal.ui org.eclipse.jface.action org.eclipse.jface.preference org.eclipse.jface.text org.eclipse.jface.util org.eclipse.jface.viewers org.eclipse.ui org.eclipse.ui.plugin

net.sf.supersearch.preferences

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	5	0%	100%	0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	SuperSearchPreferenceBasePage	None	net.sf.supersearch org.eclipse.jface.preference org.eclipse.swt.widgets org.eclipse.ui org.eclipse.ui.plugin

net.sf.supersearch.util

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	0	0%	0%	100%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	FileLogger	None	None

net.sf.supersearch.views

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
1	14	0%	93%	7%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	InputAddress Status SuperSearchView	net.sf.supersearch.actions	com.grandrapid.component net.sf.supersearch org.eclipse.core.runtime org.eclipse.jface.action org.eclipse.jface.preference org.eclipse.jface.resource org.eclipse.jface.util org.eclipse.swt.events org.eclipse.swt.layout org.eclipse.swt.widgets org.eclipse.ui org.eclipse.ui.part org.eclipse.ui.plugin s

Cycles

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

There are no cyclic dependancies.

Explanations

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

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