<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Deconstructing Software &#187; Complexity</title>
	<atom:link href="http://www.headwaysoftware.com/blog/category/complexity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.headwaysoftware.com/blog</link>
	<description></description>
	<lastBuildDate>Tue, 24 Jan 2012 20:39:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Making JUnit 4.8.2 tangle free – a possible solution</title>
		<link>http://www.headwaysoftware.com/blog/2011/03/making-junit-4-8-2-tangle-free-%e2%80%93-a-possible-solution/</link>
		<comments>http://www.headwaysoftware.com/blog/2011/03/making-junit-4-8-2-tangle-free-%e2%80%93-a-possible-solution/#comments</comments>
		<pubDate>Thu, 31 Mar 2011 13:03:08 +0000</pubDate>
		<dc:creator>Paul O'Reilly</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Restructure101]]></category>
		<category><![CDATA[Structure101]]></category>
		<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[JUnit]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=337</guid>
		<description><![CDATA[The purpose of this exercise was to use Restructure101 to solve tangles in JUnit version 4.8.2.  <a href="http://www.headwaysoftware.com/blog/2011/03/making-junit-4-8-2-tangle-free-%e2%80%93-a-possible-solution/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2011/03/making-junit-4-8-2-tangle-free-%e2%80%93-a-possible-solution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software erosion and package tangles</title>
		<link>http://www.headwaysoftware.com/blog/2008/12/software-erosion-and-package-tangles/</link>
		<comments>http://www.headwaysoftware.com/blog/2008/12/software-erosion-and-package-tangles/#comments</comments>
		<pubDate>Wed, 03 Dec 2008 10:26:30 +0000</pubDate>
		<dc:creator>Ian Sutton</dc:creator>
				<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Package design]]></category>
		<category><![CDATA[Software Architecture]]></category>
		<category><![CDATA[Software erosion]]></category>
		<category><![CDATA[Transformations]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=158</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2008/12/software-erosion-and-package-tangles/";</script>My recent post on architectural erosion in the findbugs code-base was generally well received, but there were some skeptical voices. In a comment, Emeric questioned whether cyclic dependencies at the package level are anything more than a smell (if that). &#8230; <a href="http://www.headwaysoftware.com/blog/2008/12/software-erosion-and-package-tangles/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2008/12/software-erosion-and-package-tangles/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Software erosion in pictures &#8211; Findbugs</title>
		<link>http://www.headwaysoftware.com/blog/2008/11/software-erosion-findbugs/</link>
		<comments>http://www.headwaysoftware.com/blog/2008/11/software-erosion-findbugs/#comments</comments>
		<pubDate>Thu, 27 Nov 2008 10:23:08 +0000</pubDate>
		<dc:creator>Ian Sutton</dc:creator>
				<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Design entropy]]></category>
		<category><![CDATA[Software Architecture]]></category>
		<category><![CDATA[Software erosion]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=131</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2008/11/software-erosion-findbugs/";</script>My particular area of interest in software these days is the importance of levels of abstraction above the raw code. In Java, the most natural place for these to manifest themselves is through the package structure (though this is certainly &#8230; <a href="http://www.headwaysoftware.com/blog/2008/11/software-erosion-findbugs/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2008/11/software-erosion-findbugs/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Package design matters &#8211; Part 1</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/package-design-matters-part-1/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/package-design-matters-part-1/#comments</comments>
		<pubDate>Mon, 13 Aug 2007 09:16:54 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Emergent Design]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=11</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/package-design-matters-part-1/";</script>Java packages are often used like file-system folders to organize source. But source files differ from &#8220;normal&#8221; files in that they are highly inter-dependent. Considering this interdependence as a package hierarchy evolves can have significant productivity benefits. Packages as Folders &#8230; <a href="http://www.headwaysoftware.com/blog/2007/08/package-design-matters-part-1/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/package-design-matters-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Martin Fowler &#8211; the design pseudo-graph</title>
		<link>http://www.headwaysoftware.com/blog/2007/06/martin-fowler-the-design-pseudo-graph/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/06/martin-fowler-the-design-pseudo-graph/#comments</comments>
		<pubDate>Thu, 28 Jun 2007 16:12:19 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=20</guid>
		<description><![CDATA[
 <a href="http://www.headwaysoftware.com/blog/2007/06/martin-fowler-the-design-pseudo-graph/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/06/martin-fowler-the-design-pseudo-graph/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DevX review of Structure101</title>
		<link>http://www.headwaysoftware.com/blog/2006/11/devx-review-of-structure101/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/11/devx-review-of-structure101/#comments</comments>
		<pubDate>Tue, 21 Nov 2006 11:54:33 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=23</guid>
		<description><![CDATA[
 <a href="http://www.headwaysoftware.com/blog/2006/11/devx-review-of-structure101/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/11/devx-review-of-structure101/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Complexity Debt &#8211; don&#8217;t &#8220;fix it&#8221;, &#8220;keep a lid on it&#8221;</title>
		<link>http://www.headwaysoftware.com/blog/2006/10/complexity-debt-dont-fix-it-keep-a-lid-on-it/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/10/complexity-debt-dont-fix-it-keep-a-lid-on-it/#comments</comments>
		<pubDate>Thu, 19 Oct 2006 13:55:31 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=24</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2006/10/complexity-debt-dont-fix-it-keep-a-lid-on-it/";</script>So you just discovered that your code-base has racked up a whole load of complexity debt. This  maybe explains why progress seems so painfully slow lately. You briefly think of suggesting a major complexity-reducing refactoring effort. This will delay the &#8230; <a href="http://www.headwaysoftware.com/blog/2006/10/complexity-debt-dont-fix-it-keep-a-lid-on-it/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/10/complexity-debt-dont-fix-it-keep-a-lid-on-it/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Structure101 v2 goes GA today</title>
		<link>http://www.headwaysoftware.com/blog/2006/10/structure101-v2-goes-ga-today/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/10/structure101-v2-goes-ga-today/#comments</comments>
		<pubDate>Tue, 10 Oct 2006 13:09:18 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=25</guid>
		<description><![CDATA[
 <a href="http://www.headwaysoftware.com/blog/2006/10/structure101-v2-goes-ga-today/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/10/structure101-v2-goes-ga-today/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tracking complexity debt</title>
		<link>http://www.headwaysoftware.com/blog/2006/09/tracking-complexity-debt/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/09/tracking-complexity-debt/#comments</comments>
		<pubDate>Wed, 13 Sep 2006 07:07:26 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/2006/09/tracking-complexity-debt/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2006/09/tracking-complexity-debt/";</script>Un-monitored, the complexity of a code-base increases with its size. Jboss and Struts are perfect examples. However monitoring complexity helps you keep complexity debt under control, or even down to zero. If you publish the last couple of years worth &#8230; <a href="http://www.headwaysoftware.com/blog/2006/09/tracking-complexity-debt/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/09/tracking-complexity-debt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manage complexity like debt</title>
		<link>http://www.headwaysoftware.com/blog/2006/09/manage-complexity-like-debt/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/09/manage-complexity-like-debt/#comments</comments>
		<pubDate>Thu, 07 Sep 2006 06:26:00 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Complexity]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/2006/09/manage-complexity-like-debt/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2006/09/manage-complexity-like-debt/";</script>Ben Hosking writes in Managing Complexity &#8211; The aim of Designing Code that: &#8220;The most important part of design is managing complexity&#8220; I like the simplicity of that. What happens if you don&#8217;t manage complexity. Well, it starts to cost. &#8230; <a href="http://www.headwaysoftware.com/blog/2006/09/manage-complexity-like-debt/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/09/manage-complexity-like-debt/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

