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.apache.shardingsphere.sharding.distsql.segment.strategy 4 4 0 1 3 0.0% 75.0% 25.0% 1
org.apache.shardingsphere.sharding.distsql.segment.table 3 2 1 0 4 33.0% 100.0% 33.0% 1
org.apache.shardingsphere.sharding.distsql.statement 23 23 0 0 6 0.0% 100.0% 0.0% 1

Packages

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

org.apache.shardingsphere.sharding.distsql.segment.strategy

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 3 0.0% 75.0% 25.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.shardingsphere.sharding.distsql.segment.strategy.AuditStrategySegment
org.apache.shardingsphere.sharding.distsql.segment.strategy.KeyGenerateStrategySegment
org.apache.shardingsphere.sharding.distsql.segment.strategy.ShardingAuditorSegment
org.apache.shardingsphere.sharding.distsql.segment.strategy.ShardingStrategySegment
 org.apache.shardingsphere.sharding.distsql.segment.table
 java.lang
java.util
org.apache.shardingsphere.distsql.segment

org.apache.shardingsphere.sharding.distsql.segment.table

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 4 33.0% 100.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.apache.shardingsphere.sharding.distsql.segment.table.AbstractTableRuleSegment
 org.apache.shardingsphere.sharding.distsql.segment.table.AutoTableRuleSegment
org.apache.shardingsphere.sharding.distsql.segment.table.TableRuleSegment
 None java.lang
java.util
org.apache.shardingsphere.distsql.segment
org.apache.shardingsphere.sharding.distsql.segment.strategy

org.apache.shardingsphere.sharding.distsql.statement

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.apache.shardingsphere.sharding.distsql.statement.AlterDefaultShardingStrategyStatement
org.apache.shardingsphere.sharding.distsql.statement.AlterShardingTableRuleStatement
org.apache.shardingsphere.sharding.distsql.statement.CreateDefaultShardingStrategyStatement
org.apache.shardingsphere.sharding.distsql.statement.CreateShardingTableRuleStatement
org.apache.shardingsphere.sharding.distsql.statement.DropDefaultShardingStrategyStatement
org.apache.shardingsphere.sharding.distsql.statement.DropShardingAlgorithmStatement
org.apache.shardingsphere.sharding.distsql.statement.DropShardingAuditorStatement
org.apache.shardingsphere.sharding.distsql.statement.DropShardingKeyGeneratorStatement
org.apache.shardingsphere.sharding.distsql.statement.DropShardingTableReferenceRuleStatement
org.apache.shardingsphere.sharding.distsql.statement.DropShardingTableRuleStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowDefaultShardingStrategyStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingAlgorithmsStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingAuditorsStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingKeyGeneratorsStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableNodesStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableReferenceRulesStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableRulesStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableRulesUsedAlgorithmStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableRulesUsedAuditorStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowShardingTableRulesUsedKeyGeneratorStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowUnusedShardingAlgorithmsStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowUnusedShardingAuditorsStatement
org.apache.shardingsphere.sharding.distsql.statement.ShowUnusedShardingKeyGeneratorsStatement
 None java.lang
java.util
org.apache.shardingsphere.distsql.segment
org.apache.shardingsphere.distsql.statement.rdl.rule.database.type
org.apache.shardingsphere.distsql.statement.rql.rule.database
org.apache.shardingsphere.sql.parser.statement.core.segment.generic

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.