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	CC	AC	Ca	Ce	A	I	D	V
de.smartics.exceptions	5	2	3	0	5	60.000004%	100.0%	60.000004%	1
de.smartics.exceptions.app	1	1	0	0	1	0.0%	100.0%	0.0%	1
de.smartics.exceptions.code	5	4	1	0	5	20.0%	100.0%	20.0%	1
de.smartics.exceptions.context	5	4	1	1	10	20.0%	91.0%	11.0%	1
de.smartics.exceptions.core	5	1	4	5	2	80.0%	29.0%	9.0%	1
de.smartics.exceptions.id	5	5	0	1	5	0.0%	83.0%	17.0%	1
de.smartics.exceptions.runtime	3	2	1	1	6	33.0%	86.0%	19.0%	1

Packages

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

de.smartics.exceptions

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	5	60.000004%	100.0%	60.000004%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
de.smartics.exceptions.AbstractCoreException de.smartics.exceptions.AbstractCoreRuntimeException de.smartics.exceptions.CoreException	de.smartics.exceptions.ExceptionInfo de.smartics.exceptions.Helper	None	de.smartics.exceptions.core de.smartics.exceptions.runtime java.io java.lang java.util

de.smartics.exceptions.app

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	1	0.0%	100.0%	0.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	de.smartics.exceptions.app.Constant	None	java.lang

de.smartics.exceptions.code

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	5	20.0%	100.0%	20.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
de.smartics.exceptions.code.NumberCode	de.smartics.exceptions.code.DefaultCodeComparator de.smartics.exceptions.code.NumberCodeComparator de.smartics.exceptions.code.NumberCodeInfo de.smartics.exceptions.code.TwoNumberCodeInfo	None	de.smartics.exceptions.core java.io java.lang java.util org.apache.commons.lang.builder

de.smartics.exceptions.context

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
1	10	20.0%	91.0%	11.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
de.smartics.exceptions.context.AbstractExceptionContext	de.smartics.exceptions.context.ConfiguredExceptionContext de.smartics.exceptions.context.ExceptionContextProperty de.smartics.exceptions.context.PropertiesConfiguredExceptionContext de.smartics.exceptions.context.SystemDefaultExceptionContext	de.smartics.exceptions.runtime	de.smartics.exceptions.core de.smartics.exceptions.id de.smartics.properties.core de.smartics.properties.util java.io java.lang java.net org.apache.commons.configuration org.apache.commons.io org.apache.commons.logging

de.smartics.exceptions.core

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
5	2	80.0%	29.0%	9.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
de.smartics.exceptions.core.Code de.smartics.exceptions.core.ExceptionContext de.smartics.exceptions.core.ExceptionId de.smartics.exceptions.core.IdFactory	de.smartics.exceptions.core.ThrowableHandleMode	de.smartics.exceptions de.smartics.exceptions.code de.smartics.exceptions.context de.smartics.exceptions.id de.smartics.exceptions.runtime	java.io java.lang

de.smartics.exceptions.id

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
1	5	0.0%	83.0%	17.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	de.smartics.exceptions.id.IncrementFactory de.smartics.exceptions.id.LongExceptionId de.smartics.exceptions.id.SignedIncrementFactory de.smartics.exceptions.id.UuidExceptionId de.smartics.exceptions.id.UuidFactory	de.smartics.exceptions.context	de.smartics.exceptions.core java.lang java.util java.util.concurrent.atomic org.apache.commons.logging

de.smartics.exceptions.runtime

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
1	6	33.0%	86.0%	19.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
de.smartics.exceptions.runtime.AbstractExceptionContextManager	de.smartics.exceptions.runtime.ExceptionContextManager de.smartics.exceptions.runtime.Helper	de.smartics.exceptions	de.smartics.exceptions.context de.smartics.exceptions.core java.io java.lang java.util.concurrent org.apache.commons.logging

Cycles

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

There are no cyclic dependencies.

Explanation

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