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 com.reallifedeveloper.tools 1 0 1 0 1 100.0% 100.0% 100.0% 1 com.reallifedeveloper.tools.gis 4 2 2 0 12 50.0% 100.0% 50.0% 1 com.reallifedeveloper.tools.rabbitmq 2 1 1 0 4 50.0% 100.0% 50.0% 1 com.reallifedeveloper.tools.test 1 0 1 1 1 100.0% 50.0% 50.0% 1 com.reallifedeveloper.tools.test.database.dbunit 3 1 2 0 17 67.0% 100.0% 67.0% 1 com.reallifedeveloper.tools.test.database.inmemory 7 5 2 0 4 29.0% 100.0% 29.0% 1 com.reallifedeveloper.tools.test.fitnesse 1 0 1 0 1 100.0% 100.0% 100.0% 1

Packages

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

com.reallifedeveloper.tools

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 1 100.0% 100.0% 100.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.package-info
None None java.lang

com.reallifedeveloper.tools.gis

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 12 50.0% 100.0% 50.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.gis.ShapefileProcessor$FeatureProcessor
com.reallifedeveloper.tools.gis.package-info
com.reallifedeveloper.tools.gis.GeometryDrawingPanel
com.reallifedeveloper.tools.gis.ShapefileProcessor
None java.awt
java.awt.geom
java.io
java.lang
java.net
java.util
javax.swing
org.geotools.api.data
org.geotools.api.feature
org.geotools.data.simple
org.geotools.geometry.jts
org.locationtech.jts.geom

com.reallifedeveloper.tools.rabbitmq

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 4 50.0% 100.0% 50.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.rabbitmq.package-info
com.reallifedeveloper.tools.rabbitmq.MoveMessages
None com.rabbitmq.client
java.io
java.lang
java.util.concurrent

com.reallifedeveloper.tools.test

Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 1 100.0% 50.0% 50.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.test.package-info
None com.reallifedeveloper.tools.test.database.inmemory
java.lang

com.reallifedeveloper.tools.test.database.dbunit

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 17 67.0% 100.0% 67.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.test.database.dbunit.AbstractDbTest
com.reallifedeveloper.tools.test.database.dbunit.package-info
com.reallifedeveloper.tools.test.database.dbunit.DbUnitDtdGenerator
None java.io
java.lang
java.sql
java.util
javax.sql
org.dbunit
org.dbunit.database
org.dbunit.dataset
org.dbunit.dataset.datatype
org.dbunit.dataset.xml
org.dbunit.ext.mssql
org.dbunit.operation
org.slf4j
org.springframework.beans.factory
org.springframework.context
org.springframework.context.annotation
org.springframework.context.support

com.reallifedeveloper.tools.test.database.inmemory

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 4 29.0% 100.0% 29.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.test.database.inmemory.PrimaryKeyGenerator
com.reallifedeveloper.tools.test.database.inmemory.package-info
com.reallifedeveloper.tools.test.database.inmemory.IntegerPrimaryKeyGenerator
com.reallifedeveloper.tools.test.database.inmemory.LongPrimaryKeyGenerator
com.reallifedeveloper.tools.test.database.inmemory.SortUtil
com.reallifedeveloper.tools.test.database.inmemory.SortUtil$FieldComparator
com.reallifedeveloper.tools.test.database.inmemory.UUIDPrimaryKeyGenerator
None com.reallifedeveloper.tools.test
java.lang
java.util
org.springframework.data.domain

com.reallifedeveloper.tools.test.fitnesse

Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 1 100.0% 100.0% 100.0% Abstract Classes Concrete Classes Used by Packages Uses Packages com.reallifedeveloper.tools.test.fitnesse.package-info
None None java.lang

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.