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.scenario.consistencycheck 4 4 0 2 19 0.0% 90.0% 10.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.api 1 1 0 0 3 0.0% 100.0% 0.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config 1 1 0 5 4 0.0% 44.0% 56.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.config 1 1 0 1 3 0.0% 75.0% 25.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper 1 1 0 1 8 0.0% 89.0% 11.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context 3 3 0 2 14 0.0% 88.0% 12.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor 1 1 0 0 6 0.0% 100.0% 0.0% 1 org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task 3 3 0 1 21 0.0% 95.0% 5.0% 1

Packages

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

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 2 19 0.0% 90.0% 10.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.ConsistencyCheckJob
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.ConsistencyCheckJobExecutorCallback
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.ConsistencyCheckJobId
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.ConsistencyCheckJobType
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
java.lang
java.sql
org.apache.shardingsphere.data.pipeline.core.context
org.apache.shardingsphere.data.pipeline.core.datasource
org.apache.shardingsphere.data.pipeline.core.job
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.data.pipeline.core.job.engine
org.apache.shardingsphere.data.pipeline.core.job.executor
org.apache.shardingsphere.data.pipeline.core.job.id
org.apache.shardingsphere.data.pipeline.core.job.progress
org.apache.shardingsphere.data.pipeline.core.job.type
org.apache.shardingsphere.data.pipeline.core.pojo
org.apache.shardingsphere.data.pipeline.core.task.runner
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.util
org.apache.shardingsphere.elasticjob.api

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.api

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 3 0.0% 100.0% 0.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.api.CreateConsistencyCheckJobParameter
None java.lang
java.util
org.apache.shardingsphere.database.connector.core.type

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 5 4 0.0% 44.0% 56.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.ConsistencyCheckJobConfiguration
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
java.lang
java.util
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.database.connector.core.type

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.config

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.scenario.consistencycheck.config.yaml.config.YamlConsistencyCheckJobConfiguration
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper
java.lang
java.util
org.apache.shardingsphere.data.pipeline.core.job.config.yaml.config

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 8 0.0% 89.0% 11.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.swapper.YamlConsistencyCheckJobConfigurationSwapper
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
java.lang
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.data.pipeline.core.job.config.yaml.swapper
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config.yaml.config
org.apache.shardingsphere.database.connector.core.type
org.apache.shardingsphere.infra.spi.type.typed
org.apache.shardingsphere.infra.util.yaml

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 2 14 0.0% 88.0% 12.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context.ConsistencyCheckJobItemContext
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context.ConsistencyCheckProcessContext
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context.ConsistencyCheckProcessContext$1
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
java.lang
java.util
java.util.concurrent.atomic
org.apache.commons.lang3.concurrent
org.apache.shardingsphere.data.pipeline.core.consistencycheck
org.apache.shardingsphere.data.pipeline.core.context
org.apache.shardingsphere.data.pipeline.core.execute
org.apache.shardingsphere.data.pipeline.core.job
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.data.pipeline.core.job.progress
org.apache.shardingsphere.data.pipeline.core.job.progress.config
org.apache.shardingsphere.data.pipeline.core.util
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config
org.apache.shardingsphere.database.connector.core.type

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 0 6 0.0% 100.0% 0.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor.ConsistencyCheckJobConfigurationChangedProcessor
None java.lang
org.apache.shardingsphere.data.pipeline.core.job
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.data.pipeline.core.metadata.node.config.processor
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config

org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 21 0.0% 95.0% 5.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task.ConsistencyCheckTasksRunner
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task.ConsistencyCheckTasksRunner$1
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task.ConsistencyCheckTasksRunner$CheckPipelineLifecycleRunnable
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
java.lang
java.util
java.util.concurrent.atomic
org.apache.shardingsphere.data.pipeline.core.consistencycheck
org.apache.shardingsphere.data.pipeline.core.context
org.apache.shardingsphere.data.pipeline.core.execute
org.apache.shardingsphere.data.pipeline.core.job.api
org.apache.shardingsphere.data.pipeline.core.job.config
org.apache.shardingsphere.data.pipeline.core.job.id
org.apache.shardingsphere.data.pipeline.core.job.progress.config
org.apache.shardingsphere.data.pipeline.core.job.service
org.apache.shardingsphere.data.pipeline.core.job.type
org.apache.shardingsphere.data.pipeline.core.metadata
org.apache.shardingsphere.data.pipeline.core.registrycenter.repository
org.apache.shardingsphere.data.pipeline.core.registrycenter.repository.job
org.apache.shardingsphere.data.pipeline.core.task.runner
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.config
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.context
org.apache.shardingsphere.infra.spi.type.typed
org.slf4j

Cycles

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

Cycles Package Package Dependencies org.apache.shardingsphere.data.pipeline.scenario.consistencycheck org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.metadata.processor org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task org.apache.shardingsphere.data.pipeline.scenario.consistencycheck
org.apache.shardingsphere.data.pipeline.scenario.consistencycheck.task

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.