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
fr.paris.lutece.plugins.form.modules.exportdirectory.business 15 13 2 2 33 13.0% 94.0% 8.0% 1
fr.paris.lutece.plugins.form.modules.exportdirectory.service 2 2 0 2 6 0.0% 75.0% 25.0% 1
fr.paris.lutece.plugins.form.modules.exportdirectory.utils 1 1 0 1 29 0.0% 97.0% 3.0% 1

Packages

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

fr.paris.lutece.plugins.form.modules.exportdirectory.business

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 33 13.0% 94.0% 8.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
fr.paris.lutece.plugins.form.modules.exportdirectory.business.IEntryConfigurationDAO
fr.paris.lutece.plugins.form.modules.exportdirectory.business.IFormConfigurationDAO
fr.paris.lutece.plugins.form.modules.exportdirectory.business.EntryConfiguration
fr.paris.lutece.plugins.form.modules.exportdirectory.business.EntryConfigurationDAO
fr.paris.lutece.plugins.form.modules.exportdirectory.business.EntryConfigurationEntryDirectoryRemovalListener
fr.paris.lutece.plugins.form.modules.exportdirectory.business.EntryConfigurationEntryFormRemovalListener
fr.paris.lutece.plugins.form.modules.exportdirectory.business.EntryConfigurationHome
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormConfiguration
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormConfigurationDAO
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormConfigurationDirectoryRemovalListener
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormConfigurationFormRemovalListener
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormConfigurationHome
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormEntryConfiguration
fr.paris.lutece.plugins.form.modules.exportdirectory.business.FormIterableEntryConfiguration
fr.paris.lutece.plugins.form.modules.exportdirectory.business.ProcessorExportdirectory
fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.modules.exportdirectory.utils
fr.paris.lutece.plugins.directory.business
fr.paris.lutece.plugins.directory.service
fr.paris.lutece.plugins.directory.utils
fr.paris.lutece.plugins.form.business
fr.paris.lutece.plugins.form.business.iteration
fr.paris.lutece.plugins.form.business.outputprocessor
fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.modules.exportdirectory.utils
fr.paris.lutece.plugins.form.service
fr.paris.lutece.plugins.form.service.entrytype
fr.paris.lutece.plugins.form.utils
fr.paris.lutece.plugins.form.web
fr.paris.lutece.plugins.genericattributes.business
fr.paris.lutece.portal.business.rbac
fr.paris.lutece.portal.service.admin
fr.paris.lutece.portal.service.i18n
fr.paris.lutece.portal.service.plugin
fr.paris.lutece.portal.service.rbac
fr.paris.lutece.portal.service.spring
fr.paris.lutece.portal.service.template
fr.paris.lutece.portal.service.util
fr.paris.lutece.portal.service.workflow
fr.paris.lutece.portal.web.constants
fr.paris.lutece.util
fr.paris.lutece.util.html
fr.paris.lutece.util.sql
java.io
java.lang
java.util
javax.servlet.http
org.apache.commons.lang
org.apache.commons.lang.math
org.apache.commons.lang3.math

fr.paris.lutece.plugins.form.modules.exportdirectory.service

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 6 0.0% 75.0% 25.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None fr.paris.lutece.plugins.form.modules.exportdirectory.service.ExportdirectoryPlugin
fr.paris.lutece.plugins.form.modules.exportdirectory.service.ExportdirectoryResourceIdService
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.form.modules.exportdirectory.utils
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.portal.service.plugin
fr.paris.lutece.portal.service.rbac
fr.paris.lutece.util
java.lang
java.util

fr.paris.lutece.plugins.form.modules.exportdirectory.utils

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 29 0.0% 97.0% 3.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None fr.paris.lutece.plugins.form.modules.exportdirectory.utils.ExportDirectoryUtils
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.directory.business
fr.paris.lutece.plugins.directory.service
fr.paris.lutece.plugins.directory.utils
fr.paris.lutece.plugins.form.business
fr.paris.lutece.plugins.form.business.iteration
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.service
fr.paris.lutece.plugins.form.utils
fr.paris.lutece.plugins.genericattributes.business
fr.paris.lutece.plugins.workflowcore.business.state
fr.paris.lutece.portal.business.file
fr.paris.lutece.portal.business.physicalfile
fr.paris.lutece.portal.service.i18n
fr.paris.lutece.portal.service.plugin
fr.paris.lutece.portal.service.spring
fr.paris.lutece.portal.service.util
fr.paris.lutece.portal.service.workflow
fr.paris.lutece.util.date
fr.paris.lutece.util.image
java.io
java.lang
java.util
javax.imageio
javax.servlet.http
org.apache.commons.io
org.apache.commons.lang
org.apache.commons.lang3
org.apache.commons.lang3.math

Cycles

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

Package Package Dependencies
fr.paris.lutece.plugins.form.modules.exportdirectory.business fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.form.modules.exportdirectory.service fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.modules.exportdirectory.utils fr.paris.lutece.plugins.form.modules.exportdirectory.service
fr.paris.lutece.plugins.form.modules.exportdirectory.business
fr.paris.lutece.plugins.form.modules.exportdirectory.service

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.