<?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: Improving architectural maintainability</title>
	<atom:link href="http://thediscoblog.com/2006/03/14/improving-architectural-maintainability/feed/" rel="self" type="application/rss+xml" />
	<link>http://thediscoblog.com/2006/03/14/improving-architectural-maintainability/</link>
	<description>Can you dig it man?</description>
	<pubDate>Sat, 22 Nov 2008 05:48:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: The Disco Blog &#187; Proactive monitoring of maintenance metrics</title>
		<link>http://thediscoblog.com/2006/03/14/improving-architectural-maintainability/#comment-1706</link>
		<dc:creator>The Disco Blog &#187; Proactive monitoring of maintenance metrics</dc:creator>
		<pubDate>Fri, 22 Sep 2006 03:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/?p=23#comment-1706</guid>
		<description>[...] I tend to categorize Afferent and Efferent coupling as Maintenance metrics, meaning that these two copasetic metrics, in collaboration with Instability, Abstractness and coverage facilitate understanding how change will affect aspects of an architecture. One thing about metrics, though, is that they are only marginally useful as one time measurements. Real value comes from watching metrics over time and noticing trends. Once a baseline has been established (say for code coverage), then you can set goals and work to achieve them (like ensuring coverage doesnâ€™t precipitously drop). [...]</description>
		<content:encoded><![CDATA[<p>[...] I tend to categorize Afferent and Efferent coupling as Maintenance metrics, meaning that these two copasetic metrics, in collaboration with Instability, Abstractness and coverage facilitate understanding how change will affect aspects of an architecture. One thing about metrics, though, is that they are only marginally useful as one time measurements. Real value comes from watching metrics over time and noticing trends. Once a baseline has been established (say for code coverage), then you can set goals and work to achieve them (like ensuring coverage doesnâ€™t precipitously drop). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://thediscoblog.com/2006/03/14/improving-architectural-maintainability/#comment-43</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 12 Apr 2006 02:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/?p=23#comment-43</guid>
		<description>Yes, there is a tool which will allow side by side comparisons of these metrics. Check out &lt;a href="http://www.stelligent.com/content/pureCms.php?section=Misc&#038;page=product-convergence"&gt;Convergence&lt;/a&gt; and watch this (dated) &lt;a href="http://vanwardtechnologies.com/demo/ConvergenceDemo2_viewlet_swf.html"&gt;demo &lt;/a&gt;(features the Java edition, however, the .NET edition has the similar features).</description>
		<content:encoded><![CDATA[<p>Yes, there is a tool which will allow side by side comparisons of these metrics. Check out <a href="http://www.stelligent.com/content/pureCms.php?section=Misc&#038;page=product-convergence">Convergence</a> and watch this (dated) <a href="http://vanwardtechnologies.com/demo/ConvergenceDemo2_viewlet_swf.html">demo </a>(features the Java edition, however, the .NET edition has the similar features).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://thediscoblog.com/2006/03/14/improving-architectural-maintainability/#comment-42</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Sun, 09 Apr 2006 15:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/?p=23#comment-42</guid>
		<description>Side by side metrics?

Greetings,
Great post about these tools. These tools are really good, but the practice is left unfished if there is no mechanism for side-by-side comparison between revisions. Do you know of any tools that can accomplish this?

For example, we are using Subversion for source control and I cannot find any good tool that can give me so much as a simple Lines Changed / Lines Added / Lines Deleted report for two given revisions. 

That would be a great start, but being able to use something like NDepend or one of these other tools to line up the stats between one version of a project and another and show the measure of improvement or worse, regression, between the two would be nothing short of amazing.</description>
		<content:encoded><![CDATA[<p>Side by side metrics?</p>
<p>Greetings,<br />
Great post about these tools. These tools are really good, but the practice is left unfished if there is no mechanism for side-by-side comparison between revisions. Do you know of any tools that can accomplish this?</p>
<p>For example, we are using Subversion for source control and I cannot find any good tool that can give me so much as a simple Lines Changed / Lines Added / Lines Deleted report for two given revisions. </p>
<p>That would be a great start, but being able to use something like NDepend or one of these other tools to line up the stats between one version of a project and another and show the measure of improvement or worse, regression, between the two would be nothing short of amazing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
