<?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 for Angry Architect</title>
	<atom:link href="http://www.angryarchitect.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.angryarchitect.com</link>
	<description></description>
	<lastBuildDate>Sun, 22 Aug 2010 02:58:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Dear Angry by Imhotep</title>
		<link>http://www.angryarchitect.com/?page_id=330&#038;cpage=1#comment-63</link>
		<dc:creator>Imhotep</dc:creator>
		<pubDate>Sun, 22 Aug 2010 02:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?page_id=330#comment-63</guid>
		<description>Mridul,

As is often the case with EA, the answer is it depends. But, like all good architects I&#039;ll start by stating my assumptions. 

1) By IT Architecture you mean predominately solution architecture, which you are already comfortable with. 

2) By EA consulting you intended to cover the full gambit of architecture. 

With these in mind I&#039;d suggest the following. 

Enterprise Architecture Planning by Spewak and Hill.
Enterprise Architecture as Strategy Ross, Weil and Robertson.

These should position you for planning EA. 

Then a little closer to the metal I&#039;d suggest
An Introduction to Enterprise Architecture by Scott Bernard and Dynamic Enterprise Architecture by Wagter et. al to help with project governance.

Finally ORourke, Fishman and Selkow&#039;s book Enterprise Architecture, Using the Zachman Framework, because  solution architects typically don&#039;t get EA.</description>
		<content:encoded><![CDATA[<p>Mridul,</p>
<p>As is often the case with EA, the answer is it depends. But, like all good architects I&#8217;ll start by stating my assumptions. </p>
<p>1) By IT Architecture you mean predominately solution architecture, which you are already comfortable with. </p>
<p>2) By EA consulting you intended to cover the full gambit of architecture. </p>
<p>With these in mind I&#8217;d suggest the following. </p>
<p>Enterprise Architecture Planning by Spewak and Hill.<br />
Enterprise Architecture as Strategy Ross, Weil and Robertson.</p>
<p>These should position you for planning EA. </p>
<p>Then a little closer to the metal I&#8217;d suggest<br />
An Introduction to Enterprise Architecture by Scott Bernard and Dynamic Enterprise Architecture by Wagter et. al to help with project governance.</p>
<p>Finally ORourke, Fishman and Selkow&#8217;s book Enterprise Architecture, Using the Zachman Framework, because  solution architects typically don&#8217;t get EA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear Angry by Mridul</title>
		<link>http://www.angryarchitect.com/?page_id=330&#038;cpage=1#comment-62</link>
		<dc:creator>Mridul</dc:creator>
		<pubDate>Sun, 22 Aug 2010 02:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?page_id=330#comment-62</guid>
		<description>Hi, We need to know the top five books you will recommend to start EA consulting Practice. Our background is in IT Architecture.

Thanks in Advance.

Mridul.</description>
		<content:encoded><![CDATA[<p>Hi, We need to know the top five books you will recommend to start EA consulting Practice. Our background is in IT Architecture.</p>
<p>Thanks in Advance.</p>
<p>Mridul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture Best Practice Handbook by Handbook of Children&#8217;s Religious Education &#124; Best Stock Trading tips.</title>
		<link>http://www.angryarchitect.com/?p=277&#038;cpage=1#comment-52</link>
		<dc:creator>Handbook of Children&#8217;s Religious Education &#124; Best Stock Trading tips.</dc:creator>
		<pubDate>Mon, 07 Jun 2010 11:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=277#comment-52</guid>
		<description>[...] Enterprise Architecture Best Practice Handbook &#124; Angry Architect [...]</description>
		<content:encoded><![CDATA[<p>[...] Enterprise Architecture Best Practice Handbook | Angry Architect [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Patterns of Enterprise Application Architecture by Imhotep</title>
		<link>http://www.angryarchitect.com/?p=249&#038;cpage=1#comment-50</link>
		<dc:creator>Imhotep</dc:creator>
		<pubDate>Mon, 10 May 2010 00:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=249#comment-50</guid>
		<description>Igor,

Perhaps you could gives us your thoughts on the DM and TS approaches in more detail? It&#039;s obviously a space in which you&#039;ve accumulated some knowledge.</description>
		<content:encoded><![CDATA[<p>Igor,</p>
<p>Perhaps you could gives us your thoughts on the DM and TS approaches in more detail? It&#8217;s obviously a space in which you&#8217;ve accumulated some knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Patterns of Enterprise Application Architecture by Igor L</title>
		<link>http://www.angryarchitect.com/?p=249&#038;cpage=1#comment-49</link>
		<dc:creator>Igor L</dc:creator>
		<pubDate>Sun, 09 May 2010 12:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=249#comment-49</guid>
		<description>Well said! I would add that the book&#039;s most helpful part is persistence. Being an architect I have used it as an aid to describing the difference between Domain Model and Transaction Script approaches and arguing that former is more adequate to needs of a project. Also, while most of code samples in &quot;persistence department&quot; are obsolete in the light of modern persistence solutions like JPA (actually, already were obsolete in 2008), the patterns behind them are realy help to explain how things work in such frameworks.</description>
		<content:encoded><![CDATA[<p>Well said! I would add that the book&#8217;s most helpful part is persistence. Being an architect I have used it as an aid to describing the difference between Domain Model and Transaction Script approaches and arguing that former is more adequate to needs of a project. Also, while most of code samples in &#8220;persistence department&#8221; are obsolete in the light of modern persistence solutions like JPA (actually, already were obsolete in 2008), the patterns behind them are realy help to explain how things work in such frameworks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture A to Z by Book author</title>
		<link>http://www.angryarchitect.com/?p=270&#038;cpage=1#comment-48</link>
		<dc:creator>Book author</dc:creator>
		<pubDate>Sun, 09 May 2010 09:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=270#comment-48</guid>
		<description>[you can contact book author directly at above e-mail.]

One of the goals of the book was to bring architectural concepts to the technology layer (networks, storage, workstations, etc.), where they are NOT normally applied by the architectural frameworks that are out there; that is the reason for focusing on that topic in Part 2 (the book clearly states that is comprised of TWO parts -- so no surprise there to anyone that looks at the Table of Contents.)

Having written several books, I very often state in my Preface the following concept: No one can learn a topic in all its glory from a SINGLE book -- read this book (of mine), see its approach and focus, and then go out and buy/read 10 books!

DM/May 2010.</description>
		<content:encoded><![CDATA[<p>[you can contact book author directly at above e-mail.]</p>
<p>One of the goals of the book was to bring architectural concepts to the technology layer (networks, storage, workstations, etc.), where they are NOT normally applied by the architectural frameworks that are out there; that is the reason for focusing on that topic in Part 2 (the book clearly states that is comprised of TWO parts &#8212; so no surprise there to anyone that looks at the Table of Contents.)</p>
<p>Having written several books, I very often state in my Preface the following concept: No one can learn a topic in all its glory from a SINGLE book &#8212; read this book (of mine), see its approach and focus, and then go out and buy/read 10 books!</p>
<p>DM/May 2010.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture Good Practices Guide by Tweets that mention Enterprise Architecture Good Practices Guide: If you’ve read any of Schekkerman’s other books this will have a fa... -- Topsy.com</title>
		<link>http://www.angryarchitect.com/?p=284&#038;cpage=1#comment-47</link>
		<dc:creator>Tweets that mention Enterprise Architecture Good Practices Guide: If you’ve read any of Schekkerman’s other books this will have a fa... -- Topsy.com</dc:creator>
		<pubDate>Thu, 06 May 2010 18:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=284#comment-47</guid>
		<description>[...] This post was mentioned on Twitter by gerold kathan. gerold kathan said: Enterprise Architecture Good Practices Guide: If you’ve read any of Schekkerman’s other books this will have a fa... http://bit.ly/aLLkKU [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by gerold kathan. gerold kathan said: Enterprise Architecture Good Practices Guide: If you’ve read any of Schekkerman’s other books this will have a fa&#8230; <a href="http://bit.ly/aLLkKU" rel="nofollow">http://bit.ly/aLLkKU</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture Good Practices Guide by System News for Sun Users – The Blog » Blog Archive » JAPS (Java … &#124; Java WebDev Insider</title>
		<link>http://www.angryarchitect.com/?p=284&#038;cpage=1#comment-46</link>
		<dc:creator>System News for Sun Users – The Blog » Blog Archive » JAPS (Java … &#124; Java WebDev Insider</dc:creator>
		<pubDate>Thu, 06 May 2010 01:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=284#comment-46</guid>
		<description>[...] Enterprise Architecture Good Practices Guide &#124; Angry Architect [...]</description>
		<content:encoded><![CDATA[<p>[...] Enterprise Architecture Good Practices Guide | Angry Architect [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture A to Z by Tweets that mention Enterprise Architecture A to Z &#124; Angry Architect -- Topsy.com</title>
		<link>http://www.angryarchitect.com/?p=270&#038;cpage=1#comment-45</link>
		<dc:creator>Tweets that mention Enterprise Architecture A to Z &#124; Angry Architect -- Topsy.com</dc:creator>
		<pubDate>Sun, 02 May 2010 19:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=270#comment-45</guid>
		<description>[...] This post was mentioned on Twitter by SOAvignon. SOAvignon said: Enterprise Architecture A to Z #SOA #books http://ow.ly/1ETAe #libros [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by SOAvignon. SOAvignon said: Enterprise Architecture A to Z #SOA #books <a href="http://ow.ly/1ETAe" rel="nofollow">http://ow.ly/1ETAe</a> #libros [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Patterns of Enterprise Application Architecture by Including start-ups in your SOA infrastructure: A Guide for Enterprise Architects &#124; Hot Daily Gossip</title>
		<link>http://www.angryarchitect.com/?p=249&#038;cpage=1#comment-36</link>
		<dc:creator>Including start-ups in your SOA infrastructure: A Guide for Enterprise Architects &#124; Hot Daily Gossip</dc:creator>
		<pubDate>Sun, 04 Apr 2010 08:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=249#comment-36</guid>
		<description>[...] Patterns of Enterprise Application Architecture &#124; Angry Architect [...]</description>
		<content:encoded><![CDATA[<p>[...] Patterns of Enterprise Application Architecture | Angry Architect [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
