<?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; Structure</title>
	<atom:link href="http://www.headwaysoftware.com/blog/category/structure/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>Introducing Levelized Structure Maps (LSM)</title>
		<link>http://www.headwaysoftware.com/blog/2011/03/introducing-levelized-structure-maps-lsm/</link>
		<comments>http://www.headwaysoftware.com/blog/2011/03/introducing-levelized-structure-maps-lsm/#comments</comments>
		<pubDate>Thu, 10 Mar 2011 06:38:09 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Restructure101]]></category>
		<category><![CDATA[Structure]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=455</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2011/03/introducing-levelized-structure-maps-lsm/";</script>Levelized Structure Maps (LSM) are a new, intuitive way to visualize and manipulate software systems. Using LSM, large-scale refactoring to remove dependency tangles and other over-complexity, becomes second nature. LSM are the core of Restructure101. Items in the LSM are levelized &#8230; <a href="http://www.headwaysoftware.com/blog/2011/03/introducing-levelized-structure-maps-lsm/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2011/03/introducing-levelized-structure-maps-lsm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Holarchy 101</title>
		<link>http://www.headwaysoftware.com/blog/2009/03/holarchy-101/</link>
		<comments>http://www.headwaysoftware.com/blog/2009/03/holarchy-101/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 18:39:35 +0000</pubDate>
		<dc:creator>Ian Sutton</dc:creator>
				<category><![CDATA[Structure]]></category>
		<category><![CDATA[Holarchy]]></category>
		<category><![CDATA[Holon]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=212</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2009/03/holarchy-101/";</script>Herbert Simon&#8217;s parable of the watchmakers was constructed to convey his belief that complex systems will evolve from simple systems much more rapidly if there are stable intermediate forms present in that evolutionary process than if they are not present. &#8230; <a href="http://www.headwaysoftware.com/blog/2009/03/holarchy-101/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2009/03/holarchy-101/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The parable of the two watchmakers</title>
		<link>http://www.headwaysoftware.com/blog/2009/03/watchmakers-parable/</link>
		<comments>http://www.headwaysoftware.com/blog/2009/03/watchmakers-parable/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 14:14:49 +0000</pubDate>
		<dc:creator>Ian Sutton</dc:creator>
				<category><![CDATA[Structure]]></category>
		<category><![CDATA[Holarchy]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=208</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2009/03/watchmakers-parable/";</script>The parable of the two watchmakers was introduced by Nobel Prize winner Herbert Simon to describe the complex relationship of subsystems and their larger wholes. There once were two watchmakers, named Hora and Tempus, who made very fine watches. The &#8230; <a href="http://www.headwaysoftware.com/blog/2009/03/watchmakers-parable/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2009/03/watchmakers-parable/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Beautiful Structure</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/beautiful-structure/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/beautiful-structure/#comments</comments>
		<pubDate>Mon, 06 Aug 2007 09:45:16 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Structure]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=14</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/beautiful-structure/";</script>In response to O’Reilly&#8217;s just-published Beautiful Code, Johnathan Edwards explains why he couldn&#8217;t go along with the premise. One sentence in his excellent piece stood out for me: &#8220;The human mind can not grasp the complexity of a moderately sized &#8230; <a href="http://www.headwaysoftware.com/blog/2007/08/beautiful-structure/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/beautiful-structure/feed/</wfw:commentRss>
		<slash:comments>1</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>Spring 2&#8242;s architecture &#8211; A single dependency cycle slipped in</title>
		<link>http://www.headwaysoftware.com/blog/2006/09/spring-2s-architecture-a-single-dependency-cycle-slipped-in/</link>
		<comments>http://www.headwaysoftware.com/blog/2006/09/spring-2s-architecture-a-single-dependency-cycle-slipped-in/#comments</comments>
		<pubDate>Mon, 18 Sep 2006 12:59:03 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></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=28</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2006/09/spring-2s-architecture-a-single-dependency-cycle-slipped-in/";</script>The Spring guys have let a single dependency cycle into their architecture. A very small flaw, but it&#8217;s a perfect example of why you need to check your code-base at different levels to keep it truly tangle-free. I did a &#8230; <a href="http://www.headwaysoftware.com/blog/2006/09/spring-2s-architecture-a-single-dependency-cycle-slipped-in/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2006/09/spring-2s-architecture-a-single-dependency-cycle-slipped-in/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>

