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 ]

PackageTCCCACCaCeAIDV
org.mlc.swing.example220070.0%100.0%0.0%1
org.mlc.swing.layout646311242.0%96.0%2.0%1

Packages

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

org.mlc.swing.example

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
070.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.mlc.swing.example.CustomerPanel
org.mlc.swing.example.ExamplePanel
Nonecom.jgoodies.forms.factories
java.awt
java.io
java.lang
javax.swing
javax.swing.plaf
org.mlc.swing.layout

org.mlc.swing.layout

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1242.0%96.0%2.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.mlc.swing.layout.ComponentBuilder
org.mlc.swing.layout.BeanProperty
org.mlc.swing.layout.ButtonBarComponentBuilder
org.mlc.swing.layout.ComponentDef
org.mlc.swing.layout.ContainerLayout
org.mlc.swing.layout.ContainerLayout$LocationScore
org.mlc.swing.layout.DefaultComponentBuilder
org.mlc.swing.layout.DnDTable
org.mlc.swing.layout.DndList
org.mlc.swing.layout.FormDebugPanel
org.mlc.swing.layout.FormEditor
org.mlc.swing.layout.FormEditor$1
org.mlc.swing.layout.FormEditor$2
org.mlc.swing.layout.FormEditor$3
org.mlc.swing.layout.FormEditor$4
org.mlc.swing.layout.FormEditor$5
org.mlc.swing.layout.FormEditor$6
org.mlc.swing.layout.FormEditor$7
org.mlc.swing.layout.FormEditor$8
org.mlc.swing.layout.FormEditor$9
org.mlc.swing.layout.FormEditor$ColSpanSpinnerModel
org.mlc.swing.layout.FormEditor$ComponentListCellRenderer
org.mlc.swing.layout.FormEditor$ComponentPaletteListModel
org.mlc.swing.layout.FormEditor$ComponentPaletteListRenderer
org.mlc.swing.layout.FormEditor$ComponentSelectionListModel
org.mlc.swing.layout.FormEditor$ConstraintTableCellRenderer
org.mlc.swing.layout.FormEditor$DeleteColumnAction
org.mlc.swing.layout.FormEditor$DeleteRowAction
org.mlc.swing.layout.FormEditor$GridTableModel
org.mlc.swing.layout.FormEditor$InsertColumnAfterAction
org.mlc.swing.layout.FormEditor$InsertColumnBeforeAction
org.mlc.swing.layout.FormEditor$InsertRowAfterAction
org.mlc.swing.layout.FormEditor$InsertRowBeforeAction
org.mlc.swing.layout.FormEditor$NewComponentAction
org.mlc.swing.layout.FormEditor$NewComponentDialog0
org.mlc.swing.layout.FormEditor$NewComponentDialog0$1
org.mlc.swing.layout.FormEditor$NewComponentDialog0$2
org.mlc.swing.layout.FormEditor$NewComponentDialog0$3
org.mlc.swing.layout.FormEditor$NewComponentDialog0$PropertyTableModel
org.mlc.swing.layout.FormEditor$RemoveComponentAction
org.mlc.swing.layout.FormEditor$RowSpanSpinnerModel
org.mlc.swing.layout.JListComponentBuilder
org.mlc.swing.layout.JTableComponentBuilder
org.mlc.swing.layout.JTableComponentBuilder$1
org.mlc.swing.layout.JToolBarComponentBuilder
org.mlc.swing.layout.JTreeComponentBuilder
org.mlc.swing.layout.LayoutConstraintsManager
org.mlc.swing.layout.LayoutConstraintsManager$1
org.mlc.swing.layout.LayoutFrame
org.mlc.swing.layout.LayoutFrame$1
org.mlc.swing.layout.LayoutFrame$2
org.mlc.swing.layout.LayoutFrame$3
org.mlc.swing.layout.LayoutFrame$4
org.mlc.swing.layout.LayoutFrame$5
org.mlc.swing.layout.LayoutFrame$CodeDialog
org.mlc.swing.layout.LayoutFrame$CodeDialog$1
org.mlc.swing.layout.LayoutFrame$XmlFileFilter
org.mlc.swing.layout.NewComponentDialog
org.mlc.swing.layout.NewComponentDialog$1
org.mlc.swing.layout.NewComponentDialog$2
org.mlc.swing.layout.NewComponentDialog$3
org.mlc.swing.layout.SeparatorComponentBuilder
org.mlc.swing.layout.TransferableWrapper
org.mlc.swing.layout.UserPrefs
org.mlc.swing.example
bsh
com.jgoodies.forms.factories
com.jgoodies.forms.layout
java.awt
java.awt.datatransfer
java.awt.dnd
java.awt.event
java.beans
java.io
java.lang
java.lang.reflect
java.util
java.util.jar
java.util.prefs
javax.swing
javax.swing.border
javax.swing.event
javax.swing.filechooser
javax.swing.table
javax.xml.parsers
javax.xml.transform
javax.xml.transform.dom
javax.xml.transform.stream
org.w3c.dom

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.

TermDescription
Number of ClassesThe number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent CouplingsThe number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent CouplingsThe number of other packages that the classes in the package depend upon is an indicator of the package's independence.
AbstractnessThe 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.
InstabilityThe 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.
DistanceThe 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.
CyclesPackages 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.