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.distsql.parser.autogen 17 16 1 1 6 6.0% 86.0% 8.0% 1 org.apache.shardingsphere.transaction.distsql.parser.core 3 3 0 1 13 0.0% 93.0% 7.0% 1 org.apache.shardingsphere.transaction.distsql.parser.facade 1 1 0 0 3 0.0% 100.0% 0.0% 1

Packages

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

org.apache.shardingsphere.distsql.parser.autogen

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 6 6.0% 86.0% 8.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementVisitor
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementBaseVisitor
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementLexer
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$AlterTransactionRuleContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$BuildInDefaultTransactionTypeContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$BuildInProviderTypeNameContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$DefaultTypeContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$ExecuteContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$LiteralContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$PropertiesContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$PropertiesDefinitionContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$PropertyContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$ProviderDefinitionContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$ProviderNameContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$ShowTransactionRuleContext
org.apache.shardingsphere.distsql.parser.autogen.TransactionDistSQLStatementParser$TransactionRuleDefinitionContext
org.apache.shardingsphere.transaction.distsql.parser.core
java.lang
java.util
org.antlr.v4.runtime
org.antlr.v4.runtime.atn
org.antlr.v4.runtime.dfa
org.antlr.v4.runtime.tree

org.apache.shardingsphere.transaction.distsql.parser.core

Packages Afferent Couplings Efferent Couplings Abstractness Instability Distance 1 13 0.0% 93.0% 7.0% Packages Abstract Classes Concrete Classes Used by Packages Uses Packages None org.apache.shardingsphere.transaction.distsql.parser.core.TransactionDistSQLLexer
org.apache.shardingsphere.transaction.distsql.parser.core.TransactionDistSQLParser
org.apache.shardingsphere.transaction.distsql.parser.core.TransactionDistSQLStatementVisitor
org.apache.shardingsphere.transaction.distsql.parser.facade
java.lang
java.util
org.antlr.v4.runtime
org.apache.shardingsphere.database.connector.core.metadata.database.enums
org.apache.shardingsphere.distsql.parser.autogen
org.apache.shardingsphere.sql.parser.api
org.apache.shardingsphere.sql.parser.api.parser
org.apache.shardingsphere.sql.parser.api.visitor
org.apache.shardingsphere.sql.parser.engine.core
org.apache.shardingsphere.sql.parser.statement.core.util
org.apache.shardingsphere.transaction.distsql.segment
org.apache.shardingsphere.transaction.distsql.statement.queryable
org.apache.shardingsphere.transaction.distsql.statement.updatable

org.apache.shardingsphere.transaction.distsql.parser.facade

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.transaction.distsql.parser.facade.TransactionDistSQLParserFacade
None java.lang
org.apache.shardingsphere.distsql.parser.engine.spi
org.apache.shardingsphere.transaction.distsql.parser.core

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.