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.workflow.modules.reply.business.config	2	2	0	1	4	0.0%	80.0%	20.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.business.task	3	2	1	4	4	33.0%	50.0%	17.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.service	3	2	1	3	9	33.0%	75.0%	8.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.service.provider	1	1	0	0	10	0.0%	100.0%	0.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.service.task	1	1	0	0	11	0.0%	100.0%	0.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.service.taskinfo	1	1	0	0	8	0.0%	100.0%	0.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.util.constants	1	1	0	1	1	0.0%	50.0%	50.0%	1
fr.paris.lutece.plugins.workflow.modules.reply.web.task	1	1	0	0	17	0.0%	100.0%	0.0%	1

Packages

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

fr.paris.lutece.plugins.workflow.modules.reply.business.config

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	fr.paris.lutece.plugins.workflow.modules.reply.business.config.TaskReplyConfig fr.paris.lutece.plugins.workflow.modules.reply.business.config.TaskReplyConfigDAO	fr.paris.lutece.plugins.workflow.modules.reply.web.task	fr.paris.lutece.plugins.workflow.utils fr.paris.lutece.plugins.workflowcore.business.config fr.paris.lutece.util.sql java.lang

fr.paris.lutece.plugins.workflow.modules.reply.business.task

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
4	4	33.0%	50.0%	17.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
fr.paris.lutece.plugins.workflow.modules.reply.business.task.IReplyDAO	fr.paris.lutece.plugins.workflow.modules.reply.business.task.Reply fr.paris.lutece.plugins.workflow.modules.reply.business.task.ReplyDAO	fr.paris.lutece.plugins.workflow.modules.reply.service fr.paris.lutece.plugins.workflow.modules.reply.service.task fr.paris.lutece.plugins.workflow.modules.reply.service.taskinfo fr.paris.lutece.plugins.workflow.modules.reply.web.task	fr.paris.lutece.portal.service.plugin fr.paris.lutece.util.sql java.lang java.util

fr.paris.lutece.plugins.workflow.modules.reply.service

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
3	9	33.0%	75.0%	8.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
fr.paris.lutece.plugins.workflow.modules.reply.service.IReplyService	fr.paris.lutece.plugins.workflow.modules.reply.service.ReplyPlugin fr.paris.lutece.plugins.workflow.modules.reply.service.ReplyService	fr.paris.lutece.plugins.workflow.modules.reply.service.task fr.paris.lutece.plugins.workflow.modules.reply.service.taskinfo fr.paris.lutece.plugins.workflow.modules.reply.web.task	fr.paris.lutece.plugins.workflow.modules.reply.business.task fr.paris.lutece.plugins.workflowcore.service.action fr.paris.lutece.plugins.workflowcore.service.state fr.paris.lutece.portal.service.message fr.paris.lutece.portal.service.plugin java.lang java.util javax.servlet.http org.apache.commons.lang

fr.paris.lutece.plugins.workflow.modules.reply.service.provider

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	10	0.0%	100.0%	0.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	fr.paris.lutece.plugins.workflow.modules.reply.service.provider.ReplyMarkerProvider	None	fr.paris.lutece.plugins.workflow.service.taskinfo fr.paris.lutece.plugins.workflowcore.business.action fr.paris.lutece.plugins.workflowcore.business.resource fr.paris.lutece.plugins.workflowcore.business.task fr.paris.lutece.plugins.workflowcore.service.provider fr.paris.lutece.plugins.workflowcore.service.task java.lang java.util javax.servlet.http net.sf.json

fr.paris.lutece.plugins.workflow.modules.reply.service.task

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	11	0.0%	100.0%	0.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	fr.paris.lutece.plugins.workflow.modules.reply.service.task.TaskReply	None	fr.paris.lutece.plugins.workflow.modules.reply.business.task fr.paris.lutece.plugins.workflow.modules.reply.service fr.paris.lutece.plugins.workflow.modules.reply.util.constants fr.paris.lutece.plugins.workflowcore.service.config fr.paris.lutece.plugins.workflowcore.service.task fr.paris.lutece.portal.business.user fr.paris.lutece.portal.service.i18n java.lang java.util javax.servlet.http org.apache.commons.lang

fr.paris.lutece.plugins.workflow.modules.reply.service.taskinfo

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	8	0.0%	100.0%	0.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	fr.paris.lutece.plugins.workflow.modules.reply.service.taskinfo.ReplyTaskInfoProvider	None	fr.paris.lutece.plugins.workflow.modules.reply.business.task fr.paris.lutece.plugins.workflow.modules.reply.service fr.paris.lutece.plugins.workflow.service.taskinfo fr.paris.lutece.portal.service.spring java.lang javax.servlet.http net.sf.json org.apache.commons.lang

fr.paris.lutece.plugins.workflow.modules.reply.util.constants

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
1	1	0.0%	50.0%	50.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	fr.paris.lutece.plugins.workflow.modules.reply.util.constants.ReplyConstants	fr.paris.lutece.plugins.workflow.modules.reply.service.task	java.lang

fr.paris.lutece.plugins.workflow.modules.reply.web.task

Afferent Couplings	Efferent Couplings	Abstractness	Instability	Distance
0	17	0.0%	100.0%	0.0%

Abstract Classes	Concrete Classes	Used by Packages	Uses Packages
None	fr.paris.lutece.plugins.workflow.modules.reply.web.task.TaskReplyComponent	None	fr.paris.lutece.plugins.workflow.modules.reply.business.config fr.paris.lutece.plugins.workflow.modules.reply.business.task fr.paris.lutece.plugins.workflow.modules.reply.service fr.paris.lutece.plugins.workflow.utils fr.paris.lutece.plugins.workflow.web.task fr.paris.lutece.plugins.workflowcore.service.config fr.paris.lutece.plugins.workflowcore.service.task fr.paris.lutece.portal.service.admin fr.paris.lutece.portal.service.message fr.paris.lutece.portal.service.spring fr.paris.lutece.portal.service.template fr.paris.lutece.portal.service.util fr.paris.lutece.util.html java.lang java.util javax.servlet.http org.apache.commons.lang

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.