<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Aggregate Cyclomatic complexity is meaningless</title>
	<atom:link href="http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/feed/" rel="self" type="application/rss+xml" />
	<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/</link>
	<description>Can you dig it man?</description>
	<pubDate>Sat, 22 Nov 2008 07:26:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Andy</title>
		<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3497</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sun, 28 Jan 2007 14:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3497</guid>
		<description>Ayaz- right on! I tend to use JavaNCSS, in concert with PMD for determining code size complexities. One thing I have found time and time again is that big code (either a method or a class) usually has a high CC.</description>
		<content:encoded><![CDATA[<p>Ayaz- right on! I tend to use JavaNCSS, in concert with PMD for determining code size complexities. One thing I have found time and time again is that big code (either a method or a class) usually has a high CC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3496</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sun, 28 Jan 2007 14:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3496</guid>
		<description>Chris- going point regarding measuring relationships in a class. PMD has a few rules around this notion that I've found helpful. Once such rule, &lt;a href="http://pmd.sourceforge.net/xref/net/sourceforge/pmd/rules/CouplingBetweenObjects.html" rel="nofollow"&gt;CouplingBetweenObjects&lt;/a&gt;, "attempts to capture all unique Class attributes, local variables, and return types to determine how many objects a class is coupled to."</description>
		<content:encoded><![CDATA[<p>Chris- going point regarding measuring relationships in a class. PMD has a few rules around this notion that I&#8217;ve found helpful. Once such rule, <a href="http://pmd.sourceforge.net/xref/net/sourceforge/pmd/rules/CouplingBetweenObjects.html" rel="nofollow">CouplingBetweenObjects</a>, &#8220;attempts to capture all unique Class attributes, local variables, and return types to determine how many objects a class is coupled to.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayaz Anwar</title>
		<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3053</link>
		<dc:creator>Ayaz Anwar</dc:creator>
		<pubDate>Thu, 18 Jan 2007 17:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-3053</guid>
		<description>The cyclomatic complexity of a class is meaningless because it is based on the concept of control-flow of a code. Complexity of a class is not measured by cyclomatic complexity rather it is being treated as design and code size complexity. Finding Design complexity of a class is something on which different views exist.So, considering cyclomatic complexity to determine the complexity of a class is actually you are making fool yourself.</description>
		<content:encoded><![CDATA[<p>The cyclomatic complexity of a class is meaningless because it is based on the concept of control-flow of a code. Complexity of a class is not measured by cyclomatic complexity rather it is being treated as design and code size complexity. Finding Design complexity of a class is something on which different views exist.So, considering cyclomatic complexity to determine the complexity of a class is actually you are making fool yourself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-2769</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 09 Jan 2007 10:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-2769</guid>
		<description>I agree that as a measure of class-level complexity, aggregate CC is at best an indicator to take a closer look at some classes. 
For controlling class complexity, I prefer to measure the total number of relationships between methods and fields in the class.  If the methods themselves are kept to a reasonable CC limit, then this gives a good indication of class-level complexity.</description>
		<content:encoded><![CDATA[<p>I agree that as a measure of class-level complexity, aggregate CC is at best an indicator to take a closer look at some classes.<br />
For controlling class complexity, I prefer to measure the total number of relationships between methods and fields in the class.  If the methods themselves are kept to a reasonable CC limit, then this gives a good indication of class-level complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Test Early &#187; Boiling frogs and code metrics</title>
		<link>http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-2716</link>
		<dc:creator>Test Early &#187; Boiling frogs and code metrics</dc:creator>
		<pubDate>Sun, 07 Jan 2007 14:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/01/07/aggregate-cyclomatic-complexity-is-meaningless/#comment-2716</guid>
		<description>[...] The whole point being that if you don&#8217;t monitor metrics like Cyclomatic complexity, all of a sudden you could have a problem on your hands, especially when dealing with legacy code. What a great analogy! Jeremy&#8217;s posting is an excellent read; however, it&#8217;s unclear towards the conclusion if the measured Cyclomatic complexity values are for single methods or classes in the aggregate. [...]</description>
		<content:encoded><![CDATA[<p>[...] The whole point being that if you don&#8217;t monitor metrics like Cyclomatic complexity, all of a sudden you could have a problem on your hands, especially when dealing with legacy code. What a great analogy! Jeremy&#8217;s posting is an excellent read; however, it&#8217;s unclear towards the conclusion if the measured Cyclomatic complexity values are for single methods or classes in the aggregate. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
