<?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; Dependency Management</title>
	<atom:link href="http://www.headwaysoftware.com/blog/category/dependency-management/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>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>Travelin&#8217; lite (the only way to fly)</title>
		<link>http://www.headwaysoftware.com/blog/2009/03/travelin-lite/</link>
		<comments>http://www.headwaysoftware.com/blog/2009/03/travelin-lite/#comments</comments>
		<pubDate>Fri, 06 Mar 2009 09:40:59 +0000</pubDate>
		<dc:creator>Ian Sutton</dc:creator>
				<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Static analysis]]></category>

		<guid isPermaLink="false">http://www.headwaysoftware.com/blog/?p=214</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2009/03/travelin-lite/";</script>Of course, you can&#8217;t code up a (meaningful) system without some number of building blocks. So even in a perfectly architected and layered system, you inevitably accumulate some baggage as you move up the stack. The trick, though, is to &#8230; <a href="http://www.headwaysoftware.com/blog/2009/03/travelin-lite/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2009/03/travelin-lite/feed/</wfw:commentRss>
		<slash:comments>2</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>Spring Framework 2.1 M3 Architecture</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/spring-framework-21-m3-architecture/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/spring-framework-21-m3-architecture/#comments</comments>
		<pubDate>Thu, 02 Aug 2007 06:35:53 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Structure101]]></category>
		<category><![CDATA[Spring]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=15</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/spring-framework-21-m3-architecture/";</script>Here are some architecture diagrams for Spring Framework 2.1 M3 (released yesterday). You can point the (free) structure101 plug-in at these and get IDE warnings if your customizations break Jeurgen&#8217;s architecture. Here is the top level breakout of org.springframwork: Structure101 &#8230; <a href="http://www.headwaysoftware.com/blog/2007/08/spring-framework-21-m3-architecture/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/spring-framework-21-m3-architecture/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Code Organization Guidelines for Large Code Bases</title>
		<link>http://www.headwaysoftware.com/blog/2007/08/code-organization-guidelines-for-large-code-bases/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/08/code-organization-guidelines-for-large-code-bases/#comments</comments>
		<pubDate>Wed, 01 Aug 2007 08:43:29 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Spring]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=16</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/08/code-organization-guidelines-for-large-code-bases/";</script>In an excellent on-line presentation Juergen Hoeller gives rationale and guidelines for controlling the structure of large, evolving code-bases. Juergen is the chief architect of the Spring framework, which as I have previously pointed out is structurally almost perfect. This &#8230; <a href="http://www.headwaysoftware.com/blog/2007/08/code-organization-guidelines-for-large-code-bases/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/08/code-organization-guidelines-for-large-code-bases/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Eclipse Plugin (OSGi) Visualization</title>
		<link>http://www.headwaysoftware.com/blog/2007/02/eclipse-plugin-osgi-visualization/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/02/eclipse-plugin-osgi-visualization/#comments</comments>
		<pubDate>Tue, 27 Feb 2007 15:09:46 +0000</pubDate>
		<dc:creator>Chris Chedgey</dc:creator>
				<category><![CDATA[Dependency Management]]></category>
		<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[OSGi]]></category>

		<guid isPermaLink="false">http://headway.structure101.com/blog/?p=21</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://www.headwaysoftware.com/blog/2007/02/eclipse-plugin-osgi-visualization/";</script>If you are going mad trying to figure out the dependencies between lots of Eclipse plug-ins, or work with other large OSGi systems, you may be interested in this. We&#8217;ve had a few people looking for an Eclipse/OSGi backend for &#8230; <a href="http://www.headwaysoftware.com/blog/2007/02/eclipse-plugin-osgi-visualization/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/02/eclipse-plugin-osgi-visualization/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Jar Hell</title>
		<link>http://www.headwaysoftware.com/blog/2007/02/jar-hell/</link>
		<comments>http://www.headwaysoftware.com/blog/2007/02/jar-hell/#comments</comments>
		<pubDate>Mon, 19 Feb 2007 12:59:42 +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://headway.structure101.com/blog/?p=22</guid>
		<description><![CDATA[
 <a href="http://www.headwaysoftware.com/blog/2007/02/jar-hell/">Continue reading</a>]]></description>
		<wfw:commentRss>http://www.headwaysoftware.com/blog/2007/02/jar-hell/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>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>
	</channel>
</rss>

