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.springframework.batch.integration.chunk 8 7 1 0 13 12.0% 100.0% 12.0% 1
org.springframework.batch.integration.file 3 2 1 0 19 33.0% 100.0% 33.0% 1
org.springframework.batch.integration.item 1 1 0 1 4 0.0% 80.0% 20.0% 1
org.springframework.batch.integration.job 5 5 0 0 9 0.0% 100.0% 0.0% 1
org.springframework.batch.integration.launch 2 2 0 0 3 0.0% 100.0% 0.0% 1

Packages

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

org.springframework.batch.integration.chunk

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 13 12.0% 100.0% 12.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.springframework.batch.integration.chunk.ChunkHandler
org.springframework.batch.integration.chunk.AsynchronousFailureException
org.springframework.batch.integration.chunk.ChunkMessageChannelItemWriter
org.springframework.batch.integration.chunk.ChunkMessageChannelItemWriter$1
org.springframework.batch.integration.chunk.ChunkMessageChannelItemWriter$LocalState
org.springframework.batch.integration.chunk.ChunkRequest
org.springframework.batch.integration.chunk.ChunkResponse
org.springframework.batch.integration.chunk.ItemWriterChunkHandler
None java.io
java.lang
java.util
org.apache.commons.logging
org.springframework.batch.core
org.springframework.batch.core.listener
org.springframework.batch.core.step.skip
org.springframework.batch.item
org.springframework.batch.repeat
org.springframework.integration.channel
org.springframework.integration.message
org.springframework.transaction.support
org.springframework.util

org.springframework.batch.integration.file

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 19 33.0% 100.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.springframework.batch.integration.file.MessageToJobParametersStrategy
org.springframework.batch.integration.file.FileToMessagesJobFactoryBean
org.springframework.batch.integration.file.ResourcePayloadAsJobParameterStrategy
None java.io
java.lang
java.net
org.springframework.batch.core
org.springframework.batch.core.job
org.springframework.batch.core.repository
org.springframework.batch.core.resource
org.springframework.batch.core.step.item
org.springframework.batch.integration.item
org.springframework.batch.item
org.springframework.batch.item.file
org.springframework.batch.item.xml
org.springframework.beans.factory
org.springframework.core.io
org.springframework.integration.channel
org.springframework.integration.dispatcher
org.springframework.integration.message
org.springframework.transaction
org.springframework.util

org.springframework.batch.integration.item

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 4 0.0% 80.0% 20.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.springframework.batch.integration.item.MessageChannelItemWriter
org.springframework.batch.integration.file
java.lang
org.springframework.batch.item.support
org.springframework.integration.channel
org.springframework.integration.message

org.springframework.batch.integration.job

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.springframework.batch.integration.job.JobExecutionReply
org.springframework.batch.integration.job.JobExecutionRequest
org.springframework.batch.integration.job.MessageOrientedStep
org.springframework.batch.integration.job.StepExecutionMessageHandler
org.springframework.batch.integration.job.StepExecutionTimeoutException
None java.lang
org.springframework.batch.core
org.springframework.batch.core.repository
org.springframework.batch.core.step
org.springframework.batch.item
org.springframework.batch.repeat
org.springframework.integration.channel
org.springframework.integration.message
org.springframework.util

org.springframework.batch.integration.launch

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 3 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.springframework.batch.integration.launch.JobLaunchRequest
org.springframework.batch.integration.launch.JobLaunchingMessageHandler
None java.lang
org.springframework.batch.core
org.springframework.batch.core.launch

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.