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
org.melati.poem.dbms.test.sql 63 19 44 0 9 70.0% 100.0% 70.0% 1

Packages

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

org.melati.poem.dbms.test.sql

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 70.0% 100.0% 70.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.melati.poem.dbms.test.sql.Thrower
org.melati.poem.dbms.test.sql.ThrowingArrayJdbc3
org.melati.poem.dbms.test.sql.ThrowingArrayJdbc4
org.melati.poem.dbms.test.sql.ThrowingArrayVariant
org.melati.poem.dbms.test.sql.ThrowingBlobJdbc3
org.melati.poem.dbms.test.sql.ThrowingBlobJdbc4
org.melati.poem.dbms.test.sql.ThrowingBlobVariant
org.melati.poem.dbms.test.sql.ThrowingCallableStatementJdbc3
org.melati.poem.dbms.test.sql.ThrowingCallableStatementJdbc4
org.melati.poem.dbms.test.sql.ThrowingCallableStatementJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingCallableStatementVariant
org.melati.poem.dbms.test.sql.ThrowingClobJdbc3
org.melati.poem.dbms.test.sql.ThrowingClobJdbc4
org.melati.poem.dbms.test.sql.ThrowingClobVariant
org.melati.poem.dbms.test.sql.ThrowingConnectionJdbc3
org.melati.poem.dbms.test.sql.ThrowingConnectionJdbc4
org.melati.poem.dbms.test.sql.ThrowingConnectionJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingConnectionVariant
org.melati.poem.dbms.test.sql.ThrowingDatabaseMetaDataJdbc3
org.melati.poem.dbms.test.sql.ThrowingDatabaseMetaDataJdbc4
org.melati.poem.dbms.test.sql.ThrowingDatabaseMetaDataJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingDatabaseMetaDataVariant
org.melati.poem.dbms.test.sql.ThrowingDriverJdbc3
org.melati.poem.dbms.test.sql.ThrowingDriverJdbc4
org.melati.poem.dbms.test.sql.ThrowingDriverJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingDriverVariant
org.melati.poem.dbms.test.sql.ThrowingParameterMetaDataJdbc3
org.melati.poem.dbms.test.sql.ThrowingParameterMetaDataJdbc4
org.melati.poem.dbms.test.sql.ThrowingParameterMetaDataVariant
org.melati.poem.dbms.test.sql.ThrowingPreparedStatementJdbc3
org.melati.poem.dbms.test.sql.ThrowingPreparedStatementJdbc4
org.melati.poem.dbms.test.sql.ThrowingPreparedStatementJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingPreparedStatementVariant
org.melati.poem.dbms.test.sql.ThrowingResultSetJdbc3
org.melati.poem.dbms.test.sql.ThrowingResultSetJdbc4
org.melati.poem.dbms.test.sql.ThrowingResultSetJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingResultSetMetaDataJdbc3
org.melati.poem.dbms.test.sql.ThrowingResultSetMetaDataJdbc4
org.melati.poem.dbms.test.sql.ThrowingResultSetMetaDataVariant
org.melati.poem.dbms.test.sql.ThrowingResultSetVariant
org.melati.poem.dbms.test.sql.ThrowingStatementJdbc3
org.melati.poem.dbms.test.sql.ThrowingStatementJdbc4
org.melati.poem.dbms.test.sql.ThrowingStatementJdbc4_1
org.melati.poem.dbms.test.sql.ThrowingStatementVariant
 org.melati.poem.dbms.test.sql.ThrowingArray
org.melati.poem.dbms.test.sql.ThrowingBlob
org.melati.poem.dbms.test.sql.ThrowingCallableStatement
org.melati.poem.dbms.test.sql.ThrowingClob
org.melati.poem.dbms.test.sql.ThrowingConnection
org.melati.poem.dbms.test.sql.ThrowingDatabaseMetaData
org.melati.poem.dbms.test.sql.ThrowingDriver
org.melati.poem.dbms.test.sql.ThrowingNClob
org.melati.poem.dbms.test.sql.ThrowingParameterMetaData
org.melati.poem.dbms.test.sql.ThrowingPreparedStatement
org.melati.poem.dbms.test.sql.ThrowingRef
org.melati.poem.dbms.test.sql.ThrowingRefJdbc3
org.melati.poem.dbms.test.sql.ThrowingResultSet
org.melati.poem.dbms.test.sql.ThrowingResultSetMetaData
org.melati.poem.dbms.test.sql.ThrowingRowId
org.melati.poem.dbms.test.sql.ThrowingSQLXML
org.melati.poem.dbms.test.sql.ThrowingSavepoint
org.melati.poem.dbms.test.sql.ThrowingStatement
org.melati.poem.dbms.test.sql.ThrowingStruct
 None java.io
java.lang
java.math
java.net
java.sql
java.util
java.util.concurrent
java.util.logging
javax.xml.transform

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.