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
net.cmp4oaw.uml2export.mwe87102712.0%100.0%12.0%1
net.cmp4oaw.uml2export.mwe.ant4400130.0%100.0%0.0%1

Packages

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

net.cmp4oaw.uml2export.mwe

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
02712.0%100.0%12.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
net.cmp4oaw.uml2export.mwe.EA_Xmi2ExportBase
net.cmp4oaw.uml2export.mwe.EA_DiagramExporter
net.cmp4oaw.uml2export.mwe.EA_IssueProxy
net.cmp4oaw.uml2export.mwe.EA_Xmi2End
net.cmp4oaw.uml2export.mwe.EA_Xmi2Exporter
net.cmp4oaw.uml2export.mwe.EA_Xmi2ProfileExporter
net.cmp4oaw.uml2export.mwe.EA_XmiWriter
net.cmp4oaw.uml2export.mwe.EA_XmiWriter$EA_URIConverter
Nonejava.io
java.lang
java.util
net.cmp4oaw.common.impl
net.cmp4oaw.ea.uml2writer
net.cmp4oaw.ea_com.common
net.cmp4oaw.ea_com.diagram
net.cmp4oaw.ea_com.exception
net.cmp4oaw.ea_com.project_interface
net.cmp4oaw.ea_com.repository
net.cmp4oaw.ea_com.util.uuid
net.cmp4oaw.uml2.support
net.cmp4oaw.uml2export
org.apache.commons.logging
org.eclipse.emf.common.util
org.eclipse.emf.ecore
org.eclipse.emf.ecore.resource
org.eclipse.emf.ecore.resource.impl
org.eclipse.emf.ecore.util
org.eclipse.emf.ecore.xmi
org.eclipse.emf.mwe.core
org.eclipse.emf.mwe.core.issues
org.eclipse.emf.mwe.core.lib
org.eclipse.emf.mwe.core.monitor
org.eclipse.emf.mwe.core.resources
org.eclipse.uml2.uml
org.eclipse.xtend.typesystem.emf

net.cmp4oaw.uml2export.mwe.ant

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0130.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonenet.cmp4oaw.uml2export.mwe.ant.EA_ExportIssues
net.cmp4oaw.uml2export.mwe.ant.EA_ExporterBase
net.cmp4oaw.uml2export.mwe.ant.EA_UML2Export
net.cmp4oaw.uml2export.mwe.ant.EA_UML2ProfileExporter
Nonejava.io
java.lang
java.util
net.cmp4oaw.common
net.cmp4oaw.common.impl
net.cmp4oaw.ea.uml2writer
net.cmp4oaw.ea_com.exception
net.cmp4oaw.ea_com.repository
net.cmp4oaw.uml2.support
net.cmp4oaw.uml2export
org.apache.tools.ant
org.eclipse.emf.mwe.core.resources
org.eclipse.xtend.typesystem.uml2

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.