<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Explicit Design</title>
	<atom:link href="http://www.rodenas.org/blog/2008/11/27/explicit-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rodenas.org/blog/2008/11/27/explicit-design/</link>
	<description>Software Development Life Cycle: Methodologies and Tools for the Enterprise</description>
	<lastBuildDate>Sun, 07 Aug 2011 12:44:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ferdy</title>
		<link>http://www.rodenas.org/blog/2008/11/27/explicit-design/#comment-7941</link>
		<dc:creator>Ferdy</dc:creator>
		<pubDate>Sun, 07 Dec 2008 23:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.rodenas.org/blog/?p=488#comment-7941</guid>
		<description>Bill, thanks for the link! A very interesting reading, a natural thing as it comes from Grady.

Some conclusions after reading the article:

1) We need to enumerate architectural patterns or styles, even if they come from accidental architectures. Something that I believe Grady is working on (&lt;a href=&quot;http://www.handbookofsoftwarearchitecture.com/index.jsp?page=Main&quot; rel=&quot;nofollow&quot;&gt;Handbook of Software Architecture&lt;/a&gt;), and, with a wide aim, &lt;a href=&quot;http://www.hillside.net/&quot; rel=&quot;nofollow&quot;&gt;The Hillside Group&lt;/a&gt;.

2) Most architectures come from previous works (theft): bifurcations, scrap and rework. Although most of them are accidental architectures, they are inevitable and some of them could become useful in future systems, but only if we&#039;re able to describe them as a pattern.</description>
		<content:encoded><![CDATA[<p>Bill, thanks for the link! A very interesting reading, a natural thing as it comes from Grady.</p>
<p>Some conclusions after reading the article:</p>
<p>1) We need to enumerate architectural patterns or styles, even if they come from accidental architectures. Something that I believe Grady is working on (<a href="http://www.handbookofsoftwarearchitecture.com/index.jsp?page=Main" rel="nofollow">Handbook of Software Architecture</a>), and, with a wide aim, <a href="http://www.hillside.net/" rel="nofollow">The Hillside Group</a>.</p>
<p>2) Most architectures come from previous works (theft): bifurcations, scrap and rework. Although most of them are accidental architectures, they are inevitable and some of them could become useful in future systems, but only if we&#8217;re able to describe them as a pattern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Higgins</title>
		<link>http://www.rodenas.org/blog/2008/11/27/explicit-design/#comment-7937</link>
		<dc:creator>Bill Higgins</dc:creator>
		<pubDate>Wed, 03 Dec 2008 05:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rodenas.org/blog/?p=488#comment-7937</guid>
		<description>Grady Booch has an interesting take around this topic area:

&quot;Every interesting software-intensive system has an architecture. While some of these architectures are intentional, most appear to be accidental.&quot;

Links:
http://www.informit.com/articles/article.aspx?p=471929
http://www2.computer.org/portal/web/computingnow/onarchitecture

- Bill</description>
		<content:encoded><![CDATA[<p>Grady Booch has an interesting take around this topic area:</p>
<p>&#8220;Every interesting software-intensive system has an architecture. While some of these architectures are intentional, most appear to be accidental.&#8221;</p>
<p>Links:<br />
<a href="http://www.informit.com/articles/article.aspx?p=471929" rel="nofollow">http://www.informit.com/articles/article.aspx?p=471929</a><br />
<a href="http://www2.computer.org/portal/web/computingnow/onarchitecture" rel="nofollow">http://www2.computer.org/portal/web/computingnow/onarchitecture</a></p>
<p>- Bill</p>
]]></content:encoded>
	</item>
</channel>
</rss>

