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
net.sf.jtreemap.swing	21	4	17	2	9	0.19	82%	1%
net.sf.jtreemap.swing.example	16	0	16	0	17	0	100%	0%
net.sf.jtreemap.swing.provider	12	0	12	1	7	0	88%	12%
net.sf.statcvs	2	0	2	10	8	0	44%	56%
net.sf.statcvs.ant	1	0	1	0	6	0	100%	0%
net.sf.statcvs.charts	25	2	23	2	30	0.08	94%	2%
net.sf.statcvs.input	11	1	10	2	9	0.09	82%	9%
net.sf.statcvs.model	10	1	9	9	4	0.1	31%	59%
net.sf.statcvs.output	18	2	16	10	22	0.11	69%	20%
net.sf.statcvs.pages	25	3	22	7	16	0.12	70%	18%
net.sf.statcvs.pages.xml	11	0	11	3	14	0	82%	18%
net.sf.statcvs.renderer	5	1	4	3	9	0.2	75%	5%
net.sf.statcvs.reportmodel	14	2	12	4	6	0.14	60%	26%
net.sf.statcvs.reports	21	3	18	4	11	0.14	73%	12%
net.sf.statcvs.util	11	0	11	7	7	0	50%	50%
net.sf.statcvs.weblinks.bugs	4	1	3	3	4	0.25	57%	18%

Packages

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

Cycles

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

Package	Cyclic Dependencies
net.sf.statcvs	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.ant	net.sf.statcvs.input net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.charts	net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model net.sf.statcvs.util
net.sf.statcvs.input	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.model	net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.output	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output
net.sf.statcvs.pages	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.pages.xml	net.sf.statcvs.reports net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.renderer	net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model net.sf.statcvs.util
net.sf.statcvs.reportmodel	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.reports	net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model
net.sf.statcvs.util	net.sf.statcvs.output net.sf.statcvs.model net.sf.statcvs.util
net.sf.statcvs.weblinks.bugs	net.sf.statcvs.pages net.sf.statcvs.model net.sf.statcvs.util net.sf.statcvs.output net.sf.statcvs.model

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.