<?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; Architecture</title>
	<atom:link href="http://www.headwaysoftware.com/blog/category/architecture/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>Disentangling .NET Namespaces</title>
		<link>http://www.headwaysoftware.com/blog/2011/06/disentangling-net-namespaces/</link>
		<comments>http://www.headwaysoftware.com/blog/2011/06/disentangling-net-namespaces/#comments</comments>
		<pubDate>Mon, 27 Jun 2011 08:03:20 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Restructure101]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=504</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2011/06/disentangling-net-namespaces/";</script>If architectural drift is addressed before monolithic code tangles have formed, the higher-level components can be disentangled by relatively low cost/risk relocation of classes between components. Otherwise more invasive class-level surgery is needed &#8211; this is possible with Restructure101, but &#8230; <a href="http://www.headwaysoftware.com/blog/2011/06/disentangling-net-namespaces/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2011/06/disentangling-net-namespaces/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>Structure101 New Feature: Class Name-map</title>
		<link>http://www.headwaysoftware.com/blog/2011/01/structure101-new-feature-class-name-map/</link>
		<comments>http://www.headwaysoftware.com/blog/2011/01/structure101-new-feature-class-name-map/#comments</comments>
		<pubDate>Wed, 26 Jan 2011 14:26:09 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Restructure101]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=326</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2011/01/structure101-new-feature-class-name-map/";</script>The name-map is a feature that most users will not require. But, there are certain use cases where its use can be invaluable. For example: If you have a large volume of class to class transformations, you may notice the &#8230; <a href="http://www.headwaysoftware.com/blog/2011/01/structure101-new-feature-class-name-map/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2011/01/structure101-new-feature-class-name-map/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mapping Architecture Diagrams to Code &#8211; the &#8220;most specific pattern&#8221; rule</title>
		<link>http://www.headwaysoftware.com/blog/2009/11/mapping-architecture-diagrams-to-code-the-most-specific-pattern-rule/</link>
		<comments>http://www.headwaysoftware.com/blog/2009/11/mapping-architecture-diagrams-to-code-the-most-specific-pattern-rule/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 17:44:51 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=292</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2009/11/mapping-architecture-diagrams-to-code-the-most-specific-pattern-rule/";</script>Architecture Diagrams in Structure101 are mapped to the physical code by patterns associated with each cell in the diagram. This enables the visual specification of rules that can then be applied to a specific version of your code so that &#8230; <a href="http://www.headwaysoftware.com/blog/2009/11/mapping-architecture-diagrams-to-code-the-most-specific-pattern-rule/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2009/11/mapping-architecture-diagrams-to-code-the-most-specific-pattern-rule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Structure101 3.1 &#8211; Software Architecture Sandboxing</title>
		<link>http://www.headwaysoftware.com/blog/2007/12/structure101-31-software-architecture-sandboxing/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/12/structure101-31-software-architecture-sandboxing/#comments</comments>
		<pubDate>Thu, 13 Dec 2007 10:33:59 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=6</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/12/structure101-31-software-architecture-sandboxing/";</script>Just released, Version 3.1 adds lots of new stuff to the Architecture perspective to make it much easier to discover the current structure and move classes or packages around to define a preferred architecture. First thing is a simple expand &#8230; <a href="http://www.headwaysoftware.com/blog/2007/12/structure101-31-software-architecture-sandboxing/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/12/structure101-31-software-architecture-sandboxing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spring 2.5 Architecture Diagrams</title>
		<link>http://www.headwaysoftware.com/blog/2007/11/spring-25-architecture-diagrams/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/11/spring-25-architecture-diagrams/#comments</comments>
		<pubDate>Thu, 01 Nov 2007 13:08:51 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Structure101]]></category>
		<category><![CDATA[Spring]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=7</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/11/spring-25-architecture-diagrams/";</script>I have updated the architecture diagrams for the just-released Spring 2.5. Any new or changed packages are highlighted (since 2.0.6). The diagrams are also online &#8211; if you pointed your IDE plugin at these after my previous entry, you will &#8230; <a href="http://www.headwaysoftware.com/blog/2007/11/spring-25-architecture-diagrams/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/11/spring-25-architecture-diagrams/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Structure101 V3 Released, Adds Architecture Control for Teams</title>
		<link>http://www.headwaysoftware.com/blog/2007/10/structure101-v3-released-adds-architecture-control-for-teams/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/10/structure101-v3-released-adds-architecture-control-for-teams/#comments</comments>
		<pubDate>Wed, 17 Oct 2007 14:28:21 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Emergent Design]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Structure101]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=8</guid>
		<description><![CDATA[
 <a href="http://www.headwaysoftware.com/blog/2007/10/structure101-v3-released-adds-architecture-control-for-teams/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/10/structure101-v3-released-adds-architecture-control-for-teams/feed/</wfw:commentRss>
		<slash:comments>0</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>An Overview of Structure101 Architecture Diagrams</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/an-overview-of-structure101-architecture-diagrams/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/an-overview-of-structure101-architecture-diagrams/#comments</comments>
		<pubDate>Fri, 10 Aug 2007 10:59:16 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Structure101]]></category>
		<category><![CDATA[Eclipse]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=12</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/an-overview-of-structure101-architecture-diagrams/";</script>Structure101 lets you work with both structure (the whole code-base as it is) and architecture (the subset of the structure that you really care about, and how it should be). It lets you define the architecture in the context of &#8230; <a href="http://www.headwaysoftware.com/blog/2007/08/an-overview-of-structure101-architecture-diagrams/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/an-overview-of-structure101-architecture-diagrams/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Structure101 IntelliJ Plug-in Build 104</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/structure101-intellij-plug-in-build-104/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/structure101-intellij-plug-in-build-104/#comments</comments>
		<pubDate>Tue, 07 Aug 2007 13:57:37 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Structure101]]></category>
		<category><![CDATA[IntelliJ]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=13</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/structure101-intellij-plug-in-build-104/";</script>This update now checks for architecture violations automatically when you do a build (previous version was &#8220;on-demand&#8221; only).  More on structure101 IDE plug-ins.]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/structure101-intellij-plug-in-build-104/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

