[ 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.dh.tint.simplifier 5 4 1 1 17 20.0% 94.0% 14.0% 1
eu.fbk.dh.tint.simplifier.rules 6 4 2 1 12 33.0% 92.0% 26.0% 1

Packages

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

eu.fbk.dh.tint.simplifier

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 17 20.0% 94.0% 14.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
eu.fbk.dh.tint.simplifier.Test$Action
eu.fbk.dh.tint.simplifier.Simplifier
eu.fbk.dh.tint.simplifier.Test
eu.fbk.dh.tint.simplifier.Test$Insert
eu.fbk.dh.tint.simplifier.Test$Remove
eu.fbk.dh.tint.simplifier.rules
com.google.common.collect
edu.stanford.nlp.ling
edu.stanford.nlp.pipeline
edu.stanford.nlp.semgraph
edu.stanford.nlp.trees
edu.stanford.nlp.util
eu.fbk.dh.tint.runner
eu.fbk.dh.tint.simplifier.rules
eu.fbk.utils.core
eu.fbk.utils.corenlp.outputters
java.io
java.lang
java.util
javax.xml.parsers
javax.xml.xpath
org.slf4j
org.w3c.dom

eu.fbk.dh.tint.simplifier.rules

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 12 33.0% 92.0% 26.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
eu.fbk.dh.tint.simplifier.rules.SimpleSplittingRule
eu.fbk.dh.tint.simplifier.rules.SimplificationRule
eu.fbk.dh.tint.simplifier.rules.DenominatiSplittingRule
eu.fbk.dh.tint.simplifier.rules.GarantendoSplittingRule
eu.fbk.dh.tint.simplifier.rules.PrecisandoSplittingRule
eu.fbk.dh.tint.simplifier.rules.ReplaceSubordinateRule
eu.fbk.dh.tint.simplifier
com.google.common.collect
edu.stanford.nlp.ling
edu.stanford.nlp.pipeline
edu.stanford.nlp.semgraph
edu.stanford.nlp.util
eu.fbk.dh.tint.digimorph.annotator
eu.fbk.dh.tint.inverse.digimorph.annotator
eu.fbk.dh.tint.simplifier
java.io
java.lang
java.util
java.util.regex

Cycles

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

Package Package Dependencies
eu.fbk.dh.tint.simplifier eu.fbk.dh.tint.simplifier.rules
eu.fbk.dh.tint.simplifier
eu.fbk.dh.tint.simplifier.rules eu.fbk.dh.tint.simplifier
eu.fbk.dh.tint.simplifier.rules

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: 2018/01/04.

Reflow Maven skin by Andrius Velykis.