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.opendaylight.mdsal.dom.store.inmemory 60 44 16 0 23 27.000002% 100.0% 27.000002% 1

Packages

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

org.opendaylight.mdsal.dom.store.inmemory

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 23 27.000002% 100.0% 27.000002%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opendaylight.mdsal.dom.store.inmemory.AbstractDOMShardTreeChangePublisher
org.opendaylight.mdsal.dom.store.inmemory.CursorStrategy
org.opendaylight.mdsal.dom.store.inmemory.DOMDataTreeShardProducer
org.opendaylight.mdsal.dom.store.inmemory.DOMDataTreeShardWriteTransaction
org.opendaylight.mdsal.dom.store.inmemory.DelegatingReadableCursorOperation
org.opendaylight.mdsal.dom.store.inmemory.DelegatingWriteCursorStrategy
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer$State
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction$SimpleCursorOperation
org.opendaylight.mdsal.dom.store.inmemory.ModificationContextNodeBuilder
org.opendaylight.mdsal.dom.store.inmemory.ReadableCursorOperation
org.opendaylight.mdsal.dom.store.inmemory.ReadableWriteableDOMDataTreeShard
org.opendaylight.mdsal.dom.store.inmemory.WriteCursorStrategy
org.opendaylight.mdsal.dom.store.inmemory.WriteableDOMDataTreeShard
org.opendaylight.mdsal.dom.store.inmemory.WriteableModificationNode
org.opendaylight.mdsal.dom.store.inmemory.WriteableNodeOperation
org.opendaylight.mdsal.dom.store.inmemory.WriteableNodeWithSubshard
 org.opendaylight.mdsal.dom.store.inmemory.AbstractDOMShardTreeChangePublisher$1
org.opendaylight.mdsal.dom.store.inmemory.AbstractDOMShardTreeChangePublisher$EmptyDataTreeCandidateNode
org.opendaylight.mdsal.dom.store.inmemory.ChainedTransactionCommitImpl
org.opendaylight.mdsal.dom.store.inmemory.ChildShardContext
org.opendaylight.mdsal.dom.store.inmemory.DOMStoreTransactionChainImpl
org.opendaylight.mdsal.dom.store.inmemory.DataTreeModificationCursorAdaptor
org.opendaylight.mdsal.dom.store.inmemory.ForeignShardModificationContext
org.opendaylight.mdsal.dom.store.inmemory.ForeignShardThreePhaseCommitCohort
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataStore
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataStoreConfigProperties
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataStoreFactory
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShard$1
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShard$SubshardProducerSpecification
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer$1
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer$Allocated
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer$Idle
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardProducer$Shutdown
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMDataTreeShardThreePhaseCommitCohort
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMStoreThreePhaseCommitCohort
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMStoreTreeChangePublisher
org.opendaylight.mdsal.dom.store.inmemory.InMemoryDOMStoreTreeChangePublisher$1
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction$1
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction$SimpleCursorOperation$1
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction$SimpleCursorOperation$2
org.opendaylight.mdsal.dom.store.inmemory.InmemoryDOMDataTreeShardWriteTransaction$SimpleCursorOperation$3
org.opendaylight.mdsal.dom.store.inmemory.ModificationContextNodeBuilder$InteriorNodeBuilder
org.opendaylight.mdsal.dom.store.inmemory.ShardCanCommitCoordinationTask
org.opendaylight.mdsal.dom.store.inmemory.ShardCommitCoordinationTask
org.opendaylight.mdsal.dom.store.inmemory.ShardDataModification
org.opendaylight.mdsal.dom.store.inmemory.ShardDataModification$1
org.opendaylight.mdsal.dom.store.inmemory.ShardDataModificationCursor
org.opendaylight.mdsal.dom.store.inmemory.ShardDataModificationFactory
org.opendaylight.mdsal.dom.store.inmemory.ShardDataModificationFactoryBuilder
org.opendaylight.mdsal.dom.store.inmemory.ShardPreCommitCoordinationTask
org.opendaylight.mdsal.dom.store.inmemory.ShardRootModificationContext
org.opendaylight.mdsal.dom.store.inmemory.ShardSubmitCoordinationTask
org.opendaylight.mdsal.dom.store.inmemory.WritableInteriorNode
org.opendaylight.mdsal.dom.store.inmemory.WritableInteriorNode$1
org.opendaylight.mdsal.dom.store.inmemory.WriteableNodeOperation$1
org.opendaylight.mdsal.dom.store.inmemory.WriteableSubshardBoundaryNode
org.opendaylight.mdsal.dom.store.inmemory.WriteableSubshardBoundaryNode$1
org.opendaylight.mdsal.dom.store.inmemory.WriteableSubshardBoundaryNode$1$1
 None com.google.common.base
com.google.common.collect
com.google.common.util.concurrent
java.lang
java.util
java.util.concurrent
java.util.concurrent.atomic
org.opendaylight.mdsal.common.api
org.opendaylight.mdsal.dom.api
org.opendaylight.mdsal.dom.spi
org.opendaylight.mdsal.dom.spi.store
org.opendaylight.yangtools.concepts
org.opendaylight.yangtools.util
org.opendaylight.yangtools.util.concurrent
org.opendaylight.yangtools.yang.common
org.opendaylight.yangtools.yang.data.api
org.opendaylight.yangtools.yang.data.api.schema
org.opendaylight.yangtools.yang.data.api.schema.tree
org.opendaylight.yangtools.yang.data.impl.schema.builder.api
org.opendaylight.yangtools.yang.data.impl.schema.builder.impl
org.opendaylight.yangtools.yang.data.impl.schema.tree
org.opendaylight.yangtools.yang.model.api
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.