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.bitrepository.pillar54121120.0%85.0%5.0%1
org.bitrepository.pillar.audit110150.0%83.0%17.0%1
org.bitrepository.pillar.exceptions220120.0%67.0%33.0%1
org.bitrepository.pillar.messagehandler151411257.0%96.0%3.0%1

Packages

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

org.bitrepository.pillar

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21120.0%85.0%5.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.bitrepository.pillar.AuditTrailManager
org.bitrepository.pillar.ReferenceArchive
org.bitrepository.pillar.ReferencePillar
org.bitrepository.pillar.ReferencePillarComponentFactory
org.bitrepository.pillar.ReferencePillarLauncher
org.bitrepository.pillar.audit
org.bitrepository.pillar.messagehandler
java.io
java.lang
java.util
org.bitrepository.common
org.bitrepository.common.settings
org.bitrepository.common.utils
org.bitrepository.pillar.messagehandler
org.bitrepository.protocol
org.bitrepository.protocol.messagebus
org.bitrepository.settings.referencesettings
org.slf4j

org.bitrepository.pillar.audit

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
150.0%83.0%17.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.pillar.audit.MemorybasedAuditTrailManager
org.bitrepository.pillar.messagehandler
java.lang
java.util
org.bitrepository.common
org.bitrepository.pillar
org.slf4j

org.bitrepository.pillar.exceptions

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
120.0%67.0%33.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.pillar.exceptions.IdentifyPillarsException
org.bitrepository.pillar.exceptions.InvalidMessageException
org.bitrepository.pillar.messagehandler
java.lang
org.bitrepository.bitrepositoryelements

org.bitrepository.pillar.messagehandler

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1257.0%96.0%3.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.bitrepository.pillar.messagehandler.PillarMessageHandler
org.bitrepository.pillar.messagehandler.AlarmDispatcher
org.bitrepository.pillar.messagehandler.DeleteFileRequestHandler
org.bitrepository.pillar.messagehandler.GetChecksumsRequestHandler
org.bitrepository.pillar.messagehandler.GetFileIDsRequestHandler
org.bitrepository.pillar.messagehandler.GetFileRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForDeleteFileRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForGetChecksumsRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForGetFileIDsRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForGetFileRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForPutFileRequestHandler
org.bitrepository.pillar.messagehandler.IdentifyPillarsForReplaceFileRequestHandler
org.bitrepository.pillar.messagehandler.PillarMediator
org.bitrepository.pillar.messagehandler.PutFileRequestHandler
org.bitrepository.pillar.messagehandler.ReplaceFileRequestHandler
org.bitrepository.pillar
java.io
java.lang
java.math
java.net
java.security
java.util
javax.xml.bind
org.apache.activemq.util
org.bitrepository.bitrepositorydata
org.bitrepository.bitrepositoryelements
org.bitrepository.bitrepositorymessages
org.bitrepository.common
org.bitrepository.common.settings
org.bitrepository.common.utils
org.bitrepository.pillar
org.bitrepository.pillar.audit
org.bitrepository.pillar.exceptions
org.bitrepository.protocol
org.bitrepository.protocol.exceptions
org.bitrepository.protocol.messagebus
org.bitrepository.protocol.time
org.bitrepository.settings.collectionsettings
org.bitrepository.settings.referencesettings
org.slf4j
org.xml.sax

Cycles

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

PackagePackage Dependencies
org.bitrepository.pillarorg.bitrepository.pillar.messagehandler
org.bitrepository.pillar
org.bitrepository.pillar.auditorg.bitrepository.pillar
org.bitrepository.pillar.messagehandler
org.bitrepository.pillar
org.bitrepository.pillar.messagehandlerorg.bitrepository.pillar
org.bitrepository.pillar.messagehandler

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.