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 ]

Summary Package TC CC AC Ca Ce A I D V org.apache.shardingsphere.data.pipeline.cdc.client 2 2 0 0 23 0.0% 100.0% 0.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.config 1 1 0 1 2 0.0% 67.0% 33.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.constant 1 1 0 1 1 0.0% 50.0% 50.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.context 1 1 0 2 5 0.0% 71.0% 29.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.exception 2 2 0 1 1 0.0% 50.0% 50.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.handler 2 0 2 1 3 100.0% 75.0% 75.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.parameter 2 2 0 1 3 0.0% 75.0% 25.0% 1 org.apache.shardingsphere.data.pipeline.cdc.client.util 4 4 0 2 12 0.0% 86.0% 14.0% 1

Packages

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

org.apache.shardingsphere.data.pipeline.cdc.client

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 23 0.0% 100.0% 0.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.CDCClient
org.apache.shardingsphere.data.pipeline.cdc.client.CDCClient$1
None com.google.common.base
com.google.common.hash
io.netty.bootstrap
io.netty.buffer
io.netty.channel
io.netty.channel.nio
io.netty.channel.socket.nio
io.netty.handler.codec.protobuf
io.netty.util
java.lang
java.util
java.util.concurrent
java.util.concurrent.atomic
java.util.function
org.apache.shardingsphere.data.pipeline.cdc.client.config
org.apache.shardingsphere.data.pipeline.cdc.client.constant
org.apache.shardingsphere.data.pipeline.cdc.client.context
org.apache.shardingsphere.data.pipeline.cdc.client.handler
org.apache.shardingsphere.data.pipeline.cdc.client.parameter
org.apache.shardingsphere.data.pipeline.cdc.client.util
org.apache.shardingsphere.data.pipeline.cdc.protocol.request
org.apache.shardingsphere.data.pipeline.cdc.protocol.response
org.slf4j

org.apache.shardingsphere.data.pipeline.cdc.client.config

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 2 0.0% 67.0% 33.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.config.CDCClientConfiguration
org.apache.shardingsphere.data.pipeline.cdc.client
com.google.common.base
java.lang

org.apache.shardingsphere.data.pipeline.cdc.client.constant

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 1 0.0% 50.0% 50.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.constant.ClientConnectionStatus
org.apache.shardingsphere.data.pipeline.cdc.client
java.lang

org.apache.shardingsphere.data.pipeline.cdc.client.context

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 2 5 0.0% 71.0% 29.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.context.ClientConnectionContext
org.apache.shardingsphere.data.pipeline.cdc.client
org.apache.shardingsphere.data.pipeline.cdc.client.util
io.netty.util
java.lang
java.util
java.util.concurrent
java.util.concurrent.atomic

org.apache.shardingsphere.data.pipeline.cdc.client.exception

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 1 0.0% 50.0% 50.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.exception.GetResultTimeoutException
org.apache.shardingsphere.data.pipeline.cdc.client.exception.ServerResultException
org.apache.shardingsphere.data.pipeline.cdc.client.util
java.lang

org.apache.shardingsphere.data.pipeline.cdc.client.handler

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 3 100.0% 75.0% 75.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages org.apache.shardingsphere.data.pipeline.cdc.client.handler.ExceptionHandler
org.apache.shardingsphere.data.pipeline.cdc.client.handler.ServerErrorResultHandler
None org.apache.shardingsphere.data.pipeline.cdc.client
io.netty.channel
java.lang
org.apache.shardingsphere.data.pipeline.cdc.client.util

org.apache.shardingsphere.data.pipeline.cdc.client.parameter

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 3 0.0% 75.0% 25.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.parameter.CDCLoginParameter
org.apache.shardingsphere.data.pipeline.cdc.client.parameter.StartStreamingParameter
org.apache.shardingsphere.data.pipeline.cdc.client
java.lang
java.util
org.apache.shardingsphere.data.pipeline.cdc.protocol.request

org.apache.shardingsphere.data.pipeline.cdc.client.util

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 2 12 0.0% 86.0% 14.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.cdc.client.util.ProtobufAnyValueConverter
org.apache.shardingsphere.data.pipeline.cdc.client.util.RequestIdUtils
org.apache.shardingsphere.data.pipeline.cdc.client.util.ResponseFuture
org.apache.shardingsphere.data.pipeline.cdc.client.util.ServerErrorResult
org.apache.shardingsphere.data.pipeline.cdc.client
org.apache.shardingsphere.data.pipeline.cdc.client.handler
com.google.common.base
com.google.protobuf
com.google.protobuf.util
java.lang
java.sql
java.util
java.util.concurrent
org.apache.shardingsphere.data.pipeline.cdc.client.context
org.apache.shardingsphere.data.pipeline.cdc.client.exception
org.apache.shardingsphere.data.pipeline.cdc.protocol.request
org.apache.shardingsphere.data.pipeline.cdc.protocol.response
org.slf4j

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.

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