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.alarm43121625.0%89.0%14.0%1
org.bitrepository.alarm.alarmservice220060.0%100.0%0.0%1
org.bitrepository.alarm.handling2112550.0%71.0%21.0%1
org.bitrepository.alarm.handling.handlers3301110.0%92.0%8.0%1
org.bitrepository.alarm.store65121017.0%83.0%0.0%1

Packages

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

org.bitrepository.alarm

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21625.0%89.0%14.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.bitrepository.alarm.AlarmService
org.bitrepository.alarm.AlarmException
org.bitrepository.alarm.AlarmServiceFactory
org.bitrepository.alarm.BasicAlarmService
org.bitrepository.alarm.alarmservice
org.bitrepository.alarm.handling.handlers
java.io
java.lang
java.util
javax.jms
org.bitrepository.alarm.handling
org.bitrepository.alarm.handling.handlers
org.bitrepository.alarm.store
org.bitrepository.bitrepositoryelements
org.bitrepository.common.settings
org.bitrepository.protocol
org.bitrepository.protocol.messagebus
org.bitrepository.protocol.security
org.bitrepository.service
org.bitrepository.service.contributor
org.bitrepository.settings.referencesettings
org.slf4j

org.bitrepository.alarm.alarmservice

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
060.0%100.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.alarm.alarmservice.AlarmServiceContextListener
org.bitrepository.alarm.alarmservice.RestAlarmService
Nonejava.lang
java.util
org.bitrepository.alarm
org.bitrepository.bitrepositoryelements
org.bitrepository.service
org.slf4j

org.bitrepository.alarm.handling

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2550.0%71.0%21.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.bitrepository.alarm.handling.AlarmHandler
org.bitrepository.alarm.handling.AlarmMediator
org.bitrepository.alarm
org.bitrepository.alarm.handling.handlers
java.lang
java.util
org.bitrepository.bitrepositorymessages
org.bitrepository.protocol.messagebus
org.slf4j

org.bitrepository.alarm.handling.handlers

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1110.0%92.0%8.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Noneorg.bitrepository.alarm.handling.handlers.AlarmLogger
org.bitrepository.alarm.handling.handlers.AlarmMailer
org.bitrepository.alarm.handling.handlers.AlarmStorer
org.bitrepository.alarm
java.lang
java.net
java.util
javax.mail
javax.mail.internet
org.bitrepository.alarm
org.bitrepository.alarm.handling
org.bitrepository.alarm.store
org.bitrepository.bitrepositorymessages
org.bitrepository.settings.referencesettings
org.slf4j

org.bitrepository.alarm.store

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
21017.0%83.0%0.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.bitrepository.alarm.store.AlarmStore
org.bitrepository.alarm.store.AlarmDatabaseConstants
org.bitrepository.alarm.store.AlarmDatabaseExtractionModel
org.bitrepository.alarm.store.AlarmDatabaseExtractor
org.bitrepository.alarm.store.AlarmDatabaseIngestor
org.bitrepository.alarm.store.AlarmServiceDAO
org.bitrepository.alarm
org.bitrepository.alarm.handling.handlers
java.lang
java.sql
java.util
org.bitrepository.bitrepositoryelements
org.bitrepository.common
org.bitrepository.common.settings
org.bitrepository.common.utils
org.bitrepository.service.database
org.bitrepository.settings.referencesettings
org.slf4j

Cycles

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

PackagePackage Dependencies
org.bitrepository.alarmorg.bitrepository.alarm.handling.handlers
org.bitrepository.alarm
org.bitrepository.alarm.alarmserviceorg.bitrepository.alarm
org.bitrepository.alarm.handling.handlers
org.bitrepository.alarm
org.bitrepository.alarm.handling.handlersorg.bitrepository.alarm
org.bitrepository.alarm.handling.handlers

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.