[ 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
eu.fbk.knowledgestore.elastic 7 7 0 0 42 0.0% 100.0% 0.0% 1

Packages

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

eu.fbk.knowledgestore.elastic

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 42 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None eu.fbk.knowledgestore.elastic.DataStoreElastic
eu.fbk.knowledgestore.elastic.DataTransactionElastic$1
eu.fbk.knowledgestore.elastic.ElasticConfigurations
eu.fbk.knowledgestore.elastic.MappingHandler
eu.fbk.knowledgestore.elastic.SearchResponseStream
eu.fbk.knowledgestore.elastic.URIHandler
eu.fbk.knowledgestore.elastic.Utility
None com.google.common.base
com.google.common.collect
com.google.common.io
eu.fbk.knowledgestore.data
eu.fbk.knowledgestore.datastore
eu.fbk.knowledgestore.runtime
java.io
java.lang
java.net
java.util
java.util.concurrent
java.util.concurrent.atomic
org.elasticsearch.action
org.elasticsearch.action.admin.cluster.health
org.elasticsearch.action.admin.indices.create
org.elasticsearch.action.admin.indices.exists.indices
org.elasticsearch.action.admin.indices.flush
org.elasticsearch.action.admin.indices.mapping.get
org.elasticsearch.action.admin.indices.mapping.put
org.elasticsearch.action.admin.indices.optimize
org.elasticsearch.action.bulk
org.elasticsearch.action.get
org.elasticsearch.action.index
org.elasticsearch.action.search
org.elasticsearch.client
org.elasticsearch.client.transport
org.elasticsearch.cluster.metadata
org.elasticsearch.common.collect
org.elasticsearch.common.hppc
org.elasticsearch.common.hppc.cursors
org.elasticsearch.common.settings
org.elasticsearch.common.transport
org.elasticsearch.common.unit
org.elasticsearch.common.xcontent
org.elasticsearch.index.query
org.elasticsearch.indices
org.elasticsearch.node
org.elasticsearch.search
org.openrdf.model
org.openrdf.model.impl
org.openrdf.model.vocabulary
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.

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.

Back to top

Last Published: 2016/02/08.

Reflow Maven skin by Andrius Velykis.

Data and Knowledge Management tools