Fork me on GitHub

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 ]

Package TC CC AC Ca Ce A I D V
org.miloss.fgsms.presentation 45 44 1 0 41 2.0% 100.0% 2.0% 1

Packages

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

org.miloss.fgsms.presentation

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 41 2.0% 100.0% 2.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.miloss.fgsms.presentation.IProxyLoader
org.miloss.fgsms.presentation.AvailabilityChart
org.miloss.fgsms.presentation.GetPluginInformationExt
org.miloss.fgsms.presentation.Helper
org.miloss.fgsms.presentation.Helper$1
org.miloss.fgsms.presentation.LogHelper
org.miloss.fgsms.presentation.LoginFilter
org.miloss.fgsms.presentation.MachineNetworkData
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeCPU
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeHDFreeSpace
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeHDRates
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeMem
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeNIC
org.miloss.fgsms.presentation.MachinePerfLogsOverTimeThreads
org.miloss.fgsms.presentation.ManageHelper
org.miloss.fgsms.presentation.MessageBrokerQueueDepthChart
org.miloss.fgsms.presentation.OpStatHelper
org.miloss.fgsms.presentation.OpStatWrapper
org.miloss.fgsms.presentation.OsAgentStatusHelper
org.miloss.fgsms.presentation.PKIHandler
org.miloss.fgsms.presentation.PerformanceViewerAvgResTime
org.miloss.fgsms.presentation.PerformanceViewerCache
org.miloss.fgsms.presentation.PerformanceViewerInvocations
org.miloss.fgsms.presentation.ProcessPerfLogsOverTimeCPU
org.miloss.fgsms.presentation.ProcessPerfLogsOverTimeFileHandles
org.miloss.fgsms.presentation.ProcessPerfLogsOverTimeMem
org.miloss.fgsms.presentation.ProcessPerfLogsOverTimeThreads
org.miloss.fgsms.presentation.ProxyLoader
org.miloss.fgsms.presentation.ProxyLoaderCXF
org.miloss.fgsms.presentation.RateStruct
org.miloss.fgsms.presentation.SortableStatusList
org.miloss.fgsms.presentation.SortableStatusList$1
org.miloss.fgsms.presentation.SortableStatusList$Status
org.miloss.fgsms.presentation.StatusHelper
org.miloss.fgsms.presentation.TransactionLogActionBreakDown
org.miloss.fgsms.presentation.TransactionLogActionData
org.miloss.fgsms.presentation.TransactionLogActionSet
org.miloss.fgsms.presentation.TransactionLogData
org.miloss.fgsms.presentation.TransactionLogStruct
org.miloss.fgsms.presentation.TransactionLogTimeStampStruct
org.miloss.fgsms.presentation.TransactionLogViewerData
org.miloss.fgsms.presentation.UDDIConfig
org.miloss.fgsms.presentation.UddiInquiry
org.miloss.fgsms.presentation.UserRequestWrapper
org.miloss.fgsms.presentation.UserRequestWrapper$1
None de.laures.cewolf
de.laures.cewolf.links
de.laures.cewolf.tooltips
java.io
java.lang
java.net
java.security
java.util
javax.servlet
javax.servlet.http
javax.xml.bind
javax.xml.datatype
javax.xml.soap
javax.xml.stream
javax.xml.ws
javax.xml.ws.handler
javax.xml.ws.handler.soap
org.apache.commons.codec.binary
org.apache.commons.lang3
org.apache.http
org.apache.http.auth
org.apache.http.client
org.apache.http.client.methods
org.apache.http.impl.client
org.apache.juddi.v3.client
org.apache.log4j
org.dom4j
org.dom4j.io
org.jfree.data.category
org.jfree.data.general
org.jfree.data.time
org.miloss.fgsms.common
org.miloss.fgsms.services.interfaces.agentcallbackservice
org.miloss.fgsms.services.interfaces.automatedreportingservice
org.miloss.fgsms.services.interfaces.common
org.miloss.fgsms.services.interfaces.dataaccessservice
org.miloss.fgsms.services.interfaces.policyconfiguration
org.miloss.fgsms.services.interfaces.reportingservice
org.miloss.fgsms.services.interfaces.status
org.uddi.api_v3
org.uddi.v3_service

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.

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.