<?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: What&#8217;s the difference between architecture and design?</title>
	<atom:link href="http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/</link>
	<description>Random ramblings over the metaphoric edge</description>
	<lastBuildDate>Thu, 29 Jul 2010 12:35:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darko Bohinc</title>
		<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/comment-page-1/#comment-38762</link>
		<dc:creator>Darko Bohinc</dc:creator>
		<pubDate>Wed, 12 May 2010 00:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.tomgraves.org/?p=364#comment-38762</guid>
		<description>Hi Tom,

From my perspective, architecture is design and design may be an architecture, depending on what the scope and objective of the design activity is. Perhaps by distinguishing between &quot;enterprise&quot; and &quot;solution&quot; focused architecture/design activity we&#039;d be in more alignment with what the expected outputs and outcomes are. It really does not matter how you call it as long you get the desired outputs and outcomes. 
See my post &lt;a href=&quot;http://www.fronde.com/blog/2010/04/how-many-architectures-do-you-see&quot; rel=&quot;nofollow&quot;&gt;How many architectures do you see?&lt;/a&gt; on this subject.</description>
		<content:encoded><![CDATA[<p>Hi Tom,</p>
<p>From my perspective, architecture is design and design may be an architecture, depending on what the scope and objective of the design activity is. Perhaps by distinguishing between &#8220;enterprise&#8221; and &#8220;solution&#8221; focused architecture/design activity we&#8217;d be in more alignment with what the expected outputs and outcomes are. It really does not matter how you call it as long you get the desired outputs and outcomes.<br />
See my post <a href="http://www.fronde.com/blog/2010/04/how-many-architectures-do-you-see" rel="nofollow">How many architectures do you see?</a> on this subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit Kabra</title>
		<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/comment-page-1/#comment-33695</link>
		<dc:creator>Amit Kabra</dc:creator>
		<pubDate>Fri, 27 Nov 2009 09:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.tomgraves.org/?p=364#comment-33695</guid>
		<description>Nice Article, got good sense of both.</description>
		<content:encoded><![CDATA[<p>Nice Article, got good sense of both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jörgen Dahlberg</title>
		<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/comment-page-1/#comment-32064</link>
		<dc:creator>Jörgen Dahlberg</dc:creator>
		<pubDate>Sat, 10 Oct 2009 13:14:44 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.tomgraves.org/?p=364#comment-32064</guid>
		<description>Architects plan, design and review the construction of dynamic systems (not just IT systems) or building blocks for the use of organisations to secure a particular outcome.</description>
		<content:encoded><![CDATA[<p>Architects plan, design and review the construction of dynamic systems (not just IT systems) or building blocks for the use of organisations to secure a particular outcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Grigoriu</title>
		<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/comment-page-1/#comment-32060</link>
		<dc:creator>Adrian Grigoriu</dc:creator>
		<pubDate>Sat, 10 Oct 2009 08:33:06 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.tomgraves.org/?p=364#comment-32060</guid>
		<description>Tom, 

I would add that they are part of the same development process. Design comes after the Architecture phase and that may explain why it is closer to implementation. 
They may be also seen as two perspectives/rows in Zachman&#039;s.

Adrian</description>
		<content:encoded><![CDATA[<p>Tom, </p>
<p>I would add that they are part of the same development process. Design comes after the Architecture phase and that may explain why it is closer to implementation.<br />
They may be also seen as two perspectives/rows in Zachman&#8217;s.</p>
<p>Adrian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat Ferdinandi</title>
		<link>http://weblog.tomgraves.org/index.php/2009/10/09/architecture-versus-design/comment-page-1/#comment-32037</link>
		<dc:creator>Pat Ferdinandi</dc:creator>
		<pubDate>Fri, 09 Oct 2009 14:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.tomgraves.org/?p=364#comment-32037</guid>
		<description>One way to identify if a person is architectually-focused versus design-focused is by the questions he or she asks. Architects will ask thought-provoking questions that challenge the current vision and strategy. He or she helps define a path. Design-focused individuals tend to also ask thought-provoking questions. These questions resolve specifics within a specific existing boundary.</description>
		<content:encoded><![CDATA[<p>One way to identify if a person is architectually-focused versus design-focused is by the questions he or she asks. Architects will ask thought-provoking questions that challenge the current vision and strategy. He or she helps define a path. Design-focused individuals tend to also ask thought-provoking questions. These questions resolve specifics within a specific existing boundary.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
