<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
	<channel>
	<generator>Feed Editor</generator>
	<pubDate>14 Jun 2006 19:40:44 GMT</pubDate>
	<title>Cutter Consortium: Enterprise Architecture</title>
	<description>Expert recommendations and advice on the strategies and technologies for achieving enterprise architecture integration.</description>
	<link>http://www.cutter.com/architecture.html</link>
	<copyright>2006 Cutter Consortium</copyright>
	<language>en-us</language>
	<skipDays><day>Sunday</day></skipDays>
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/CutterConsortiumEnterpriseArchitecture" type="application/rss+xml" /><feedburner:emailServiceId>CutterConsortiumEnterpriseArchitecture</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><feedburner:browserFriendly>Expert recommendations and advice on the strategies and technologies for achieving enterprise architecture integration.</feedburner:browserFriendly><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
	<title>Is Your Perimeter Secure?</title>
	<description>Rosen, Mike | E-Mail Advisors | 17 June 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Is your perimeter secure? The answer to that is simple: NO. As business has become more distributed, outsourcing has gone global, supply chains are more connected, employees have become teleworkers, customers demand better information, and so on, we have systematically punched holes into perimeter security until it now resembles Swiss cheese.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090617.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qK1Lq6CfKtI:jy4MB6CuBjQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qK1Lq6CfKtI:jy4MB6CuBjQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qK1Lq6CfKtI:jy4MB6CuBjQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qK1Lq6CfKtI:jy4MB6CuBjQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qK1Lq6CfKtI:jy4MB6CuBjQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qK1Lq6CfKtI:jy4MB6CuBjQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qK1Lq6CfKtI:jy4MB6CuBjQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/qK1Lq6CfKtI" height="1" width="1"/&gt;</description>
	<pubDate>17 Jun 2009 19:58:09 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/qK1Lq6CfKtI/ea090617.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090617.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090617.html</feedburner:origLink></item>
	<item>
	<title>Are You at the Controls? Do You Know Where Your Data Is?</title>
	<description>Rosen, Mike | E-Mail Advisors | 10 June 2009 | Enterprise Architecture; Business Intelligence; Enterprise Risk Management &amp;amp; Governance &lt;BR&gt;&lt;BR&gt;Perhaps you remember the public service campaign from 1960s television that went something like, "It's 10 pm. Do you know where your children are?" For IT, we could rephrase it as; "It's 2009. Do you know where your data is?" You probably don't, especially if it's in the hands of your partners or outsourcers. So, the answer to the question in the title of this Advisor is most likely, "I don't know."&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090610.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=occ44ChhXDM:eORv-wO_i6c:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=occ44ChhXDM:eORv-wO_i6c:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=occ44ChhXDM:eORv-wO_i6c:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=occ44ChhXDM:eORv-wO_i6c:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=occ44ChhXDM:eORv-wO_i6c:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=occ44ChhXDM:eORv-wO_i6c:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=occ44ChhXDM:eORv-wO_i6c:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/occ44ChhXDM" height="1" width="1"/&gt;</description>
	<pubDate>10 Jun 2009 19:43:38 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/occ44ChhXDM/ea090610.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090610.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090610.html</feedburner:origLink></item>
	<item>
	<title>Open Source Java Frameworks: Development/Testing, Middleware, and Comprehensive Frameworks</title>
	<description>Welsh, Tom | Executive Updates | 05 June 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In Part V, I move on to the findings for development/testing, middleware, and comprehensive OSJFs. Then, before summing up the series and to put the OSJF findings into context, we take a look at the non-Java frameworks that respondents have been using.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0911.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afYYO8Jpjd0:1gq96uWV9Vo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afYYO8Jpjd0:1gq96uWV9Vo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afYYO8Jpjd0:1gq96uWV9Vo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afYYO8Jpjd0:1gq96uWV9Vo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afYYO8Jpjd0:1gq96uWV9Vo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afYYO8Jpjd0:1gq96uWV9Vo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afYYO8Jpjd0:1gq96uWV9Vo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/afYYO8Jpjd0" height="1" width="1"/&gt;</description>
	<pubDate>5 Jun 2009 16:21:10 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/afYYO8Jpjd0/eau0911.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0911.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0911.html</feedburner:origLink></item>
	<item>
	<title>The Cloud Machine: Some Tips to Get Behind the Haze</title>
	<description>Seiden, Mark | E-Mail Advisors | 03 June 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;"The cloud" is important, yes, but in my view it isn't rocket science (or even atmospheric science). I think of it as just another step in outsourcing and pushing everything into a commodity, which for me creates only "modified rapture."&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090603.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nqTz5vvjy_M:Fw5cmB0TFR8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nqTz5vvjy_M:Fw5cmB0TFR8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nqTz5vvjy_M:Fw5cmB0TFR8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nqTz5vvjy_M:Fw5cmB0TFR8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nqTz5vvjy_M:Fw5cmB0TFR8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nqTz5vvjy_M:Fw5cmB0TFR8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nqTz5vvjy_M:Fw5cmB0TFR8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nqTz5vvjy_M" height="1" width="1"/&gt;</description>
	<pubDate>3 Jun 2009 16:15:40 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nqTz5vvjy_M/ea090603.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090603.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090603.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Collaboration Architecture Webinar</title>
	<description>Rosen, Mike | Webinars/Multimedia | 03 June 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Collaboration is a hot topic within Web 2.0 and Enterprise 2.0 technologies. It seems that everybody wants it, but what does it really mean for an enterprise? How can collaboration help improve internal processes and development? And how can it improve interactions with customers and partners? In this Webinar, Mike Rosen, Director of Cutter's Enterprise Architecture practice, first looks at what we mean by collaboration and why we do it. Then, he looks at the impact on traditional business transaction processing when we try to add collaboration. Mike will discuss a detailed example of an extended business transaction and the benefits it can deliver, and finally he'll take a look at the application architecture necessary to integrate Enterprise 2.0 technologies into real business transactions at an enterprise level. Join Mike Rosen for this hour-long, interactive webinar. Ask questions, get answers. Discover the opportunities opened by Enterprise Collaboration Architecture, consider some approaches, and anticipate the obstacles.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/webinar/2009/enterprisecollaborationarchitecture.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=INSVBw57U04:HwlF8tTQM54:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=INSVBw57U04:HwlF8tTQM54:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=INSVBw57U04:HwlF8tTQM54:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=INSVBw57U04:HwlF8tTQM54:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=INSVBw57U04:HwlF8tTQM54:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=INSVBw57U04:HwlF8tTQM54:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=INSVBw57U04:HwlF8tTQM54:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/INSVBw57U04" height="1" width="1"/&gt;</description>
	<pubDate>3 Jun 2009 16:14:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/INSVBw57U04/enterprisecollaborationarchitecture.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/webinar/2009/enterprisecollaborationarchitecture.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/webinar/2009/enterprisecollaborationarchitecture.html</feedburner:origLink></item>
	<item>
	<title>For Hybrid Clouds, Fog of Confusion Is Burning Away</title>
	<description>Hall, Curt | E-Mail Advisors | 28 May 2009 | Business Technology Trends &amp;amp; Impacts; Sourcing &amp;amp; Vendor Relationships; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Most of the attention being paid to cloud computing has focused on public cloud providers, such as Amazon and Google, and software-as-a-service (SaaS) vendors, such as Salesforce.com. However, based on my research, including feedback I've received from readers, I believe that the future of corporate IT, especially when it comes to larger companies, will be based on "hybrid clouds" -- those employing both public and private clouds to meet business goals.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090528.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bL5mIKN8ZTQ:pnKzEtJlNcg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bL5mIKN8ZTQ:pnKzEtJlNcg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bL5mIKN8ZTQ:pnKzEtJlNcg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bL5mIKN8ZTQ:pnKzEtJlNcg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bL5mIKN8ZTQ:pnKzEtJlNcg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bL5mIKN8ZTQ:pnKzEtJlNcg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bL5mIKN8ZTQ:pnKzEtJlNcg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/bL5mIKN8ZTQ" height="1" width="1"/&gt;</description>
	<pubDate>28 May 2009 16:05:28 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/bL5mIKN8ZTQ/btt090528.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090528.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090528.html</feedburner:origLink></item>
	<item>
	<title>EA and SOA: A Marriage Made in Heaven?</title>
	<description>Allen, Paul | E-Mail Advisors | 27 May 2009 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;While EA and service-oriented architecture (SOA) have their own advocates and camps of followers, recent developments have seen many of the EA approaches and frameworks looking to offer increasing support for SOA. The fact that business is increasingly conducted in a collaborative fashion, using distributed Internet technologies, makes this very welcome. While I review these developments and more in an upcoming Executive Report ("EA Meets SOA in a Challenged Global Economy"), right now I want to offer some general observations on extending your EA to support SOA.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090527.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xxvaDXMfEQI:CcNyMpkAz2o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xxvaDXMfEQI:CcNyMpkAz2o:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xxvaDXMfEQI:CcNyMpkAz2o:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xxvaDXMfEQI:CcNyMpkAz2o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xxvaDXMfEQI:CcNyMpkAz2o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xxvaDXMfEQI:CcNyMpkAz2o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xxvaDXMfEQI:CcNyMpkAz2o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/xxvaDXMfEQI" height="1" width="1"/&gt;</description>
	<pubDate>27 May 2009 16:03:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/xxvaDXMfEQI/ea090527.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090527.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090527.html</feedburner:origLink></item>
	<item>
	<title>Architectural Challenges in Transforming to SaaS Solutions</title>
	<description>Markande, Krishna | Executive Updates | 22 May 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;To fully understand the advantages and challenges in software as a service (SaaS), we must analyze the emerging model thoroughly from the viewpoint of customers and independent software vendors (ISVs). The aim of such scrutiny is to reap the benefits and mitigate possible risks of SaaS.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0910.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RAl0bEM4BC0:ygaV4blTDh4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RAl0bEM4BC0:ygaV4blTDh4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RAl0bEM4BC0:ygaV4blTDh4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RAl0bEM4BC0:ygaV4blTDh4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RAl0bEM4BC0:ygaV4blTDh4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RAl0bEM4BC0:ygaV4blTDh4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RAl0bEM4BC0:ygaV4blTDh4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RAl0bEM4BC0" height="1" width="1"/&gt;</description>
	<pubDate>22 May 2009 15:50:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RAl0bEM4BC0/eau0910.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0910.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0910.html</feedburner:origLink></item>
	<item>
	<title>Aiming for the Big Picture, EA Goes Beyond 3D</title>
	<description>Orr, Ken | E-Mail Advisors | 20 May 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;For a long time, I have been advocating that the right analogy for enterprise architecture is urban/transportation planning versus building architecture. Now, while designing and building a single large building is a complex, difficult problem, what large IT organizations everywhere are faced with is not just developing or replacing individual systems, regardless of how difficult that that may be. Rather, they are managing networks or systems; in some cases networks of networks of systems. Enterprise architecture, like urban/transportation planning, is involved with trying to understand and shape the really big picture.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090520.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JTvDHomnxgQ:yPYBHskxaz4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JTvDHomnxgQ:yPYBHskxaz4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JTvDHomnxgQ:yPYBHskxaz4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JTvDHomnxgQ:yPYBHskxaz4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JTvDHomnxgQ:yPYBHskxaz4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JTvDHomnxgQ:yPYBHskxaz4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JTvDHomnxgQ:yPYBHskxaz4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/JTvDHomnxgQ" height="1" width="1"/&gt;</description>
	<pubDate>20 May 2009 15:40:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/JTvDHomnxgQ/ea090520.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090520.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090520.html</feedburner:origLink></item>
	<item>
	<title>COBIT Primer</title>
	<description>Rosen, Mike | E-Mail Advisors | 13 May 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;There are so many different frameworks with which architects work -- TOGAF, Zachmann, FEAF, ITIL -- to name just a few. All have different goals, strengths, weaknesses, audiences, and so on. The one that I find to be the least well known among architects is COBIT. Yet I find that many CIOs and executives are familiar with this framework and that it is important in communicating up to the C-level. COBIT, originally released in 1996, is currently at version 4.1 (you can download the guide from &lt;A href="http://www.isaca.org"&gt;www.isaca.org&lt;/A&gt;).&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090513.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YI2y0TrzQG4:1IUmYVWYoVc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YI2y0TrzQG4:1IUmYVWYoVc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YI2y0TrzQG4:1IUmYVWYoVc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YI2y0TrzQG4:1IUmYVWYoVc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YI2y0TrzQG4:1IUmYVWYoVc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YI2y0TrzQG4:1IUmYVWYoVc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YI2y0TrzQG4:1IUmYVWYoVc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/YI2y0TrzQG4" height="1" width="1"/&gt;</description>
	<pubDate>13 May 2009 15:30:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/YI2y0TrzQG4/ea090513.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090513.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090513.html</feedburner:origLink></item>
	<item>
	<title>Open Source Java Frameworks: GUI, Web, Web Services, and Persistence</title>
	<description>Welsh, Tom | Executive Updates | 12 May 2009 | Enterprise Architecture &lt;BR&gt;This is the fourth in a series of Executive Updates in which I analyze the results of a recent Cutter Consortium survey on the subject of open source Java frameworks (OSJFs). Part I1 explored Java EE's perceived strengths and weaknesses, to find out whether there is good reason for developers to look for alternatives. In Part II,2 we saw that nearly three in four respondents think that OSJFs always or often offer good solutions to Java's shortcomings, though there was some concern about the risk of lock-in, uncertainty over future plans, and lack of standardization.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0909.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fezsdxjyyK8:-si9p5N9Sio:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fezsdxjyyK8:-si9p5N9Sio:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fezsdxjyyK8:-si9p5N9Sio:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fezsdxjyyK8:-si9p5N9Sio:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fezsdxjyyK8:-si9p5N9Sio:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fezsdxjyyK8:-si9p5N9Sio:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fezsdxjyyK8:-si9p5N9Sio:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/fezsdxjyyK8" height="1" width="1"/&gt;</description>
	<pubDate>12 May 2009 14:52:03 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/fezsdxjyyK8/eau0909.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0909.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0909.html</feedburner:origLink></item>
	<item>
	<title>A Capability Trilogy, Part III: Triage Comes Into Play</title>
	<description>Allen, Paul | E-Mail Advisors | 06 May 2009 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;While the notion of core/context capabilities is central to the whole capability-driven approach, it is sometimes quite difficult to take a strictly binary view. Graduating capabilities in terms of their degree of commoditization can help, and it is possible to use several classifications along a spectrum from high to low commoditization. At the same time, it's important not to overegg the pudding.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090506.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Dp6FfJUxQAo:Fe-xi-izj2I:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Dp6FfJUxQAo:Fe-xi-izj2I:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Dp6FfJUxQAo:Fe-xi-izj2I:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Dp6FfJUxQAo:Fe-xi-izj2I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Dp6FfJUxQAo:Fe-xi-izj2I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Dp6FfJUxQAo:Fe-xi-izj2I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Dp6FfJUxQAo:Fe-xi-izj2I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Dp6FfJUxQAo" height="1" width="1"/&gt;</description>
	<pubDate>6 May 2009 16:00:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Dp6FfJUxQAo/ea090506.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090506.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090506.html</feedburner:origLink></item>
	<item>
	<title>Harnessing Your Architecture Repository to Value</title>
	<description>Rosen, Michael | E-Mail Advisors | 30 April 2009 | Business Technology Trends &amp;amp; Impacts; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;As more and more enterprises realize a need for architecture, the vendors of tools that support architecture are jumping on the opportunity. I'm seeing a growing trend in the acquisition of enterprise architecture repositories. Unfortunately, I haven't yet seen most organizations realize the value that these tools can bring. As always, technology itself does not provide business value; it only enables solutions. It is how you use the technology that brings value, and repositories are no exception.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090430.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iWYnnyb4I1g:Af87JzWmpzU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iWYnnyb4I1g:Af87JzWmpzU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iWYnnyb4I1g:Af87JzWmpzU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iWYnnyb4I1g:Af87JzWmpzU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iWYnnyb4I1g:Af87JzWmpzU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iWYnnyb4I1g:Af87JzWmpzU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iWYnnyb4I1g:Af87JzWmpzU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/iWYnnyb4I1g" height="1" width="1"/&gt;</description>
	<pubDate>30 Apr 2009 15:52:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/iWYnnyb4I1g/btt090430.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090430.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090430.html</feedburner:origLink></item>
	<item>
	<title>Take Iterative Steps: Start Small, Empower Team Via Vision, Value</title>
	<description>Berglove, Dan; van Tyn, Jeroen | E-Mail Advisors | 29 April 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;The iterative and incremental approach to software development has become a well-established best practice, as evidenced by its centrality to any number of software development methodologies, including agile and variations on the Unified Process.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090429.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kVoiWZu3IuM:xYX77hpt15c:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kVoiWZu3IuM:xYX77hpt15c:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kVoiWZu3IuM:xYX77hpt15c:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kVoiWZu3IuM:xYX77hpt15c:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kVoiWZu3IuM:xYX77hpt15c:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kVoiWZu3IuM:xYX77hpt15c:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kVoiWZu3IuM:xYX77hpt15c:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/kVoiWZu3IuM" height="1" width="1"/&gt;</description>
	<pubDate>29 Apr 2009 15:50:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/kVoiWZu3IuM/ea090429.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090429.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090429.html</feedburner:origLink></item>
	<item>
	<title>The Myth of Software Reuse</title>
	<description>Rooney, David | Executive Updates | 24 April 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I've been developing software professionally since 1988, long enough to have encountered multiple fads and movements within the software industry. A goal that has endured from my first few months as a developer to the present day: software should be reusable. Object orientation promised it. Component-based software promised it. Now, Web services and service-oriented architecture (SOA) promise that holy grail of substantially reduced costs through the reuse of code.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0908.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xvJrDtw7wbs:g-e_elCpEVE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xvJrDtw7wbs:g-e_elCpEVE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xvJrDtw7wbs:g-e_elCpEVE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xvJrDtw7wbs:g-e_elCpEVE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xvJrDtw7wbs:g-e_elCpEVE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xvJrDtw7wbs:g-e_elCpEVE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xvJrDtw7wbs:g-e_elCpEVE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/xvJrDtw7wbs" height="1" width="1"/&gt;</description>
	<pubDate>24 Apr 2009 15:45:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/xvJrDtw7wbs/eau0908.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0908.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0908.html</feedburner:origLink></item>
	<item>
	<title>Getting to the Root of Corporate Change -- Motivation</title>
	<description>Rosen, Mike | E-Mail Advisors | 22 April 2009 | Enterprise Architecture; Business-IT Strategies; Agile Project Management &lt;BR&gt;&lt;BR&gt;As an architect, I'm constantly challenged to help organizations come up with better ways to do things. Unfortunately, in IT, we don't usually bring in architecture before there is some kind of mess to clean up. The typical scenarios include: complexity has gotten out of control, costs are too high, it takes too long to do anything, systems are brittle and can't be changed, a change in one place breaks something somewhere else, and on and on. You know the litany of problems.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090422.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kyh1cYj9E7Q:kJWzdQJrUTs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kyh1cYj9E7Q:kJWzdQJrUTs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kyh1cYj9E7Q:kJWzdQJrUTs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kyh1cYj9E7Q:kJWzdQJrUTs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kyh1cYj9E7Q:kJWzdQJrUTs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kyh1cYj9E7Q:kJWzdQJrUTs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kyh1cYj9E7Q:kJWzdQJrUTs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/kyh1cYj9E7Q" height="1" width="1"/&gt;</description>
	<pubDate>22 Apr 2009 15:37:03 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/kyh1cYj9E7Q/ea090422.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090422.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090422.html</feedburner:origLink></item>
	<item>
	<title>A Capability Trilogy, Part II: The Nine Dimensions of Capability</title>
	<description>Allen, Paul | E-Mail Advisors | 15 April 2009 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;As discussed in the first Advisor in this series (see "A Capability Trilogy, Part I: The Politics of Capability," 25 March 2009), capability-oriented thinking is becoming increasingly influential in methodologies, enterprise architecture frameworks, and business strategy. A business capability (capability for short) is a combination of capacity and ability to perform a coherent family of functions in terms of what must be done to achieve stated outcomes (see my Business-IT Strategies Executive Report, "Business Capabilities: Realizing the Potential" Vol. 12, No. 2).&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090415.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RGFmegRDFFY:x3ToBIcJOrY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RGFmegRDFFY:x3ToBIcJOrY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RGFmegRDFFY:x3ToBIcJOrY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RGFmegRDFFY:x3ToBIcJOrY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RGFmegRDFFY:x3ToBIcJOrY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RGFmegRDFFY:x3ToBIcJOrY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RGFmegRDFFY:x3ToBIcJOrY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RGFmegRDFFY" height="1" width="1"/&gt;</description>
	<pubDate>15 Apr 2009 15:00:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RGFmegRDFFY/ea090415.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090415.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090415.html</feedburner:origLink></item>
	<item>
	<title>Don't Blame It All on Release Management</title>
	<description>Konkol, Sebastian | Executive Updates | 14 April 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;After the publication of Part I of my two-part Executive Report series1, 2 on release management, I received some comments. Some of the issues mentioned could be seen as symptomatic of each organization that deals with release management. In light of these comments and from a recent consulting project at a mobile operator struggling with release issues related to its IT and VAS platforms environments, I decided to revisit release management and provide another perspective in this Executive Update: how release management helps uncover problems that can directly be attributed to software development, architecture, and collaboration.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0907.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gP02I5SFsJQ:CqayNxGRklg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gP02I5SFsJQ:CqayNxGRklg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gP02I5SFsJQ:CqayNxGRklg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gP02I5SFsJQ:CqayNxGRklg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gP02I5SFsJQ:CqayNxGRklg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gP02I5SFsJQ:CqayNxGRklg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gP02I5SFsJQ:CqayNxGRklg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/gP02I5SFsJQ" height="1" width="1"/&gt;</description>
	<pubDate>14 Apr 2009 14:57:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/gP02I5SFsJQ/eau0907.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0907.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0907.html</feedburner:origLink></item>
	<item>
	<title>What Doesn't Kill You ... And Other Lessons About Support</title>
	<description>Rosen, Mike | E-Mail Advisors | 08 April 2009 | Enterprise Architecture; Enterprise Risk Management &amp;amp; Governance &lt;BR&gt;&lt;BR&gt;They say "What doesn't kill you makes you stronger," and perhaps this is true for architects as well. I recently went through an experience that all architects and IT professionals should go through occasionally, but not too often. An insipid virus infected my computer, having evaded the defenses of my firewall/security product and, slowly but surely, rendered my laptop useless. Since I had also fallen prey to application bloat over the years and laptop performance had slowed to the speed of a pig stuck in molasses in January without a paddle, there was really nothing to do but rebuild the OS.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090408.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zBefezOfYBg:4Gb-oFfoUys:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zBefezOfYBg:4Gb-oFfoUys:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zBefezOfYBg:4Gb-oFfoUys:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zBefezOfYBg:4Gb-oFfoUys:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zBefezOfYBg:4Gb-oFfoUys:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zBefezOfYBg:4Gb-oFfoUys:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zBefezOfYBg:4Gb-oFfoUys:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/zBefezOfYBg" height="1" width="1"/&gt;</description>
	<pubDate>8 Apr 2009 13:17:36 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/zBefezOfYBg/ea090408.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090408.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090408.html</feedburner:origLink></item>
	<item>
	<title>Making SOA Work by Shedding IT's Anorak</title>
	<description>Allen, Paul | Executive Updates | 07 April 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Service-oriented architecture (SOA) is often approached as very much a technology-centric initiative. However, while SOA infrastructure and technical design both have vital parts to play, they must be judged at the end of the day as enablers of business improvement. A good SOA is only as good as the business knowledge that goes into its construction. Eliciting this business knowledge depends on developing and sustaining a good business case, which requires significant raising of the business-IT communication bar. This Executive Update considers the results of a recent Cutter Consortium survey showing that we remain well short of this bar. We present some short, sharp guidelines for improving this situation. The bottom line is that IT must shed its anorak1 and operate within the context of organizational change management. This Update offers guidance for you to apply on this difficult journey, with particular reference to the impact of SOA on the business case for IT projects.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0906.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nxfVYslhM3c:c0EBKvAEe6k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nxfVYslhM3c:c0EBKvAEe6k:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nxfVYslhM3c:c0EBKvAEe6k:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nxfVYslhM3c:c0EBKvAEe6k:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nxfVYslhM3c:c0EBKvAEe6k:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nxfVYslhM3c:c0EBKvAEe6k:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nxfVYslhM3c:c0EBKvAEe6k:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nxfVYslhM3c" height="1" width="1"/&gt;</description>
	<pubDate>7 Apr 2009 13:15:27 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nxfVYslhM3c/eau0906.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0906.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0906.html</feedburner:origLink></item>
	<item>
	<title>Review: TOGAF 9 Takes Key Steps Forward</title>
	<description>Rosen, Mike | E-Mail Advisors | 01 April 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;It's been five years in the making, and perhaps a few years later than promised, but TOGAF 9 was finally released to the public in mid-February 2009. You can download a 744-page, PDF evaluation copy, subject to license restrictions, from The Open Group's Web site (www.opengroup.org/togaf), purchase a downloadable version for US $40 (free to Open Group members), or spring for the nicely bound hard-copy version for &amp;euro;75.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090401.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xRttYYQWWts:hvXy0QPCN2Y:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xRttYYQWWts:hvXy0QPCN2Y:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xRttYYQWWts:hvXy0QPCN2Y:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xRttYYQWWts:hvXy0QPCN2Y:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xRttYYQWWts:hvXy0QPCN2Y:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xRttYYQWWts:hvXy0QPCN2Y:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xRttYYQWWts:hvXy0QPCN2Y:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/xRttYYQWWts" height="1" width="1"/&gt;</description>
	<pubDate>1 Apr 2009 13:10:32 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/xRttYYQWWts/ea090401.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090401.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090401.html</feedburner:origLink></item>
	<item>
	<title>Service-Oriented Architecture: Foundational Elements</title>
	<description>Maitra, Amit K. | Executive Reports | 01 March 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;"Service-oriented architecture" (SOA) is a powerful term regularly abused by its constant reference to developmental technologies rather than its architectural approach. This Executive Report by Dr. Amit K. Maitra discusses SOA in the context of "services" as the term applies to architecture and to "architecture" as it applies to exposing the services. The new service concept is revolutionizing and accelerating the way enterprises accomplish business integration by providing a foundation for business agility with minimal cost and full potential for application reusability. This report first defines the foundational elements of SOA then argues that just as the Enterprise Service Bus connects applications to services in an SOA, a similar approach with the potential benefits of architecting a messaging foundation for the functionality of "information as a service" could and should be undertaken.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/architecture/fulltext/reports/2009/03/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1VKQ1emCPDA:JKkfFR5t-48:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1VKQ1emCPDA:JKkfFR5t-48:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1VKQ1emCPDA:JKkfFR5t-48:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1VKQ1emCPDA:JKkfFR5t-48:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1VKQ1emCPDA:JKkfFR5t-48:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1VKQ1emCPDA:JKkfFR5t-48:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1VKQ1emCPDA:JKkfFR5t-48:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/1VKQ1emCPDA" height="1" width="1"/&gt;</description>
	<pubDate>1 Mar 2009 14:35:26 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/1VKQ1emCPDA/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture/fulltext/reports/2009/03/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture/fulltext/reports/2009/03/index.html</feedburner:origLink></item>
	<item>
	<title>A Capability Trilogy, Part I: The Politics of Capability</title>
	<description>Allen, Paul | E-Mail Advisors | 25 March 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Organizations continue to recalibrate their business models in order to cut costs in challenging economic circumstances. At the same time, cuts that are spread evenly across business units and departments may seem democratic but can be a very shortsighted strategy. Breaking an organization down into component capabilities can allow an organization to focus its investment where it has the greatest benefit.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090325.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nUwS9jPKPmc:nODnXERjfpM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nUwS9jPKPmc:nODnXERjfpM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nUwS9jPKPmc:nODnXERjfpM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nUwS9jPKPmc:nODnXERjfpM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nUwS9jPKPmc:nODnXERjfpM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nUwS9jPKPmc:nODnXERjfpM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nUwS9jPKPmc:nODnXERjfpM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nUwS9jPKPmc" height="1" width="1"/&gt;</description>
	<pubDate>25 Mar 2009 14:26:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nUwS9jPKPmc/ea090325.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090325.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090325.html</feedburner:origLink></item>
	<item>
	<title>Bold CIO -- It Is SOA Time!</title>
	<description>Cohen, Pini | E-Mail Advisors | 25 March 2009 | Enterprise Architecture; Cutter IT Journal &lt;BR&gt;&lt;BR&gt;A lot has been said lately about service-oriented architecture (SOA). Still, I would like to take a look at another angle of SOA adoption in the light of the current economic turmoil.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/itjournal/fulltext/advisor/2009/itj090325.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vsMaa2kMsH4:h-omgdzE0bg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vsMaa2kMsH4:h-omgdzE0bg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vsMaa2kMsH4:h-omgdzE0bg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vsMaa2kMsH4:h-omgdzE0bg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vsMaa2kMsH4:h-omgdzE0bg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vsMaa2kMsH4:h-omgdzE0bg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vsMaa2kMsH4:h-omgdzE0bg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/vsMaa2kMsH4" height="1" width="1"/&gt;</description>
	<pubDate>25 Mar 2009 14:25:55 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/vsMaa2kMsH4/itj090325.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/advisor/2009/itj090325.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/advisor/2009/itj090325.html</feedburner:origLink></item>
	<item>
	<title>Semantics Is Hot; Data and Objects Are Not, Part I: The Emergence of the Semantic Web</title>
	<description>Orr, Ken | E-Mail Advisors | 19 March 2009 | Business Technology Trends &amp;amp; Impacts; Business Intelligence; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;(This is the first in a series of Trends Advisors that will deal with the complex landscape of content, unstructured and structured, that confront organizations and individuals as we move from Web 2.0 to Web 3.0 and beyond. Future Advisors will deal with the growing schism between developers and database experts.)&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090319.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QX4ZFVqAES8:4iYhUYw4Kz4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QX4ZFVqAES8:4iYhUYw4Kz4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QX4ZFVqAES8:4iYhUYw4Kz4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QX4ZFVqAES8:4iYhUYw4Kz4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QX4ZFVqAES8:4iYhUYw4Kz4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QX4ZFVqAES8:4iYhUYw4Kz4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QX4ZFVqAES8:4iYhUYw4Kz4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/QX4ZFVqAES8" height="1" width="1"/&gt;</description>
	<pubDate>19 Mar 2009 14:13:32 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/QX4ZFVqAES8/btt090319.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090319.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090319.html</feedburner:origLink></item>
	<item>
	<title>Six Key Capabilities on Road to EA Success</title>
	<description>Berglove, Dan; van Tyn, Jeroen | E-Mail Advisors | 18 March 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;A key objective of enterprise architecture (EA) is to deliver to business strategies and imperatives. This is also the basis for measuring the success of EA investment. While architectural models, specifications, standards, and so on are, of course, important; they will not, in and of themselves, enable this on their own. A foundational set of organizational capabilities must be in place that enables businesses to realize architecture-based solutions on a sustained basis.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090318.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9woG_-OfAa0:xmQ1l42Zka0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9woG_-OfAa0:xmQ1l42Zka0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9woG_-OfAa0:xmQ1l42Zka0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9woG_-OfAa0:xmQ1l42Zka0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9woG_-OfAa0:xmQ1l42Zka0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9woG_-OfAa0:xmQ1l42Zka0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9woG_-OfAa0:xmQ1l42Zka0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9woG_-OfAa0" height="1" width="1"/&gt;</description>
	<pubDate>18 Mar 2009 14:11:27 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9woG_-OfAa0/ea090318.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090318.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090318.html</feedburner:origLink></item>
	<item>
	<title>Desktops in the Cloud? They're on the Horizon</title>
	<description>Hall, Curt | E-Mail Advisors | 11 March 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;We are beginning to hear more serious thought given to the concept of third-party providers managing desktop environments via the cloud. For example, as reported in a recent Computerworld article,1 at the recent VMWorld Europe 2009 conference in Cannes, France, Jocelyn Goldfein, general manager of VMWare's desktop business unit, said she believes the desktop is an area that's ripe for moving to the cloud. Having spent about one and one-half years dealing with Microsoft's Vista operating system, I'm beginning to think that she may be onto something. But is widespread use of cloud-based desktops really on the horizon?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090311.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=V1Ty6QOHuJU:1avvT8YNa9w:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=V1Ty6QOHuJU:1avvT8YNa9w:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=V1Ty6QOHuJU:1avvT8YNa9w:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=V1Ty6QOHuJU:1avvT8YNa9w:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=V1Ty6QOHuJU:1avvT8YNa9w:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=V1Ty6QOHuJU:1avvT8YNa9w:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=V1Ty6QOHuJU:1avvT8YNa9w:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/V1Ty6QOHuJU" height="1" width="1"/&gt;</description>
	<pubDate>11 Mar 2009 19:51:47 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/V1Ty6QOHuJU/ea090311.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090311.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090311.html</feedburner:origLink></item>
	<item>
	<title>Value from the Intersection of Business and Technology Architecture: Part II</title>
	<description>Bess, Charles E.; Mullis, Philip S. | Executive Updates | 08 March 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In Part I of this two-part Executive Update series, we explored the value of architecture and the function of the architect.1 Here, we discuss the various stages and domains of architecture and why enterprise architecture (EA) is good business.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0905.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7_tWU8QxwpQ:cBXy-XNwkjI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7_tWU8QxwpQ:cBXy-XNwkjI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7_tWU8QxwpQ:cBXy-XNwkjI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7_tWU8QxwpQ:cBXy-XNwkjI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7_tWU8QxwpQ:cBXy-XNwkjI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7_tWU8QxwpQ:cBXy-XNwkjI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7_tWU8QxwpQ:cBXy-XNwkjI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/7_tWU8QxwpQ" height="1" width="1"/&gt;</description>
	<pubDate>8 Mar 2009 19:47:49 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/7_tWU8QxwpQ/eau0905.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0905.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0905.html</feedburner:origLink></item>
	<item>
	<title>Taking a Step Toward Radical Delivery with Enterprise Architecture</title>
	<description>Andriole, Stephen J. | E-Mail Advisors | 04 March 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Pretend that you are either starting a new company or -- with the help of a magic wand -- completely reengineering the technology delivery model at your current company. What do you do? One of the steps that you should take involves enterprise architecture.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090304.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6u-WubVfeJo:74ZmIUK0n0o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6u-WubVfeJo:74ZmIUK0n0o:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6u-WubVfeJo:74ZmIUK0n0o:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6u-WubVfeJo:74ZmIUK0n0o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6u-WubVfeJo:74ZmIUK0n0o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6u-WubVfeJo:74ZmIUK0n0o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6u-WubVfeJo:74ZmIUK0n0o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/6u-WubVfeJo" height="1" width="1"/&gt;</description>
	<pubDate>4 Mar 2009 19:40:22 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/6u-WubVfeJo/ea090304.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090304.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090304.html</feedburner:origLink></item>
	<item>
	<title>Release Management Framework: Part II</title>
	<description>Konkol, Sebastian | Executive Reports | 01 February 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;This Executive Report by Sebastian Konkol is the second in a two-part series focusing on the practice of release management. Release management is a method of coordinated introduction of various software modifications to the production systems environment. While the first report looked at the methodological aspects of release management implementation, this report offers a pragmatic view on the various issues directly related to release management. It provides examples of concepts employed and presents two real-world case studies.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/architecture/fulltext/reports/2009/02/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DS3opgMv-_o:farpE4PTgmM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DS3opgMv-_o:farpE4PTgmM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DS3opgMv-_o:farpE4PTgmM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DS3opgMv-_o:farpE4PTgmM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DS3opgMv-_o:farpE4PTgmM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DS3opgMv-_o:farpE4PTgmM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DS3opgMv-_o:farpE4PTgmM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/DS3opgMv-_o" height="1" width="1"/&gt;</description>
	<pubDate>1 Feb 2009 14:17:24 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/DS3opgMv-_o/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture/fulltext/reports/2009/02/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture/fulltext/reports/2009/02/index.html</feedburner:origLink></item>
	<item>
	<title>Open Source Java Frameworks: Adoption</title>
	<description>Welsh, Tom | Executive Updates | 27 February 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Here in Part III, I shall examine how far OSJFs have penetrated the market as well as which types are currently most popular. I shall also present some ways in which responding organizations "give back" to the open source organizations that develop and maintain the software they use, and in what ways they do so.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0904.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=deKy5nBf7hs:nL4pwvaduc4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=deKy5nBf7hs:nL4pwvaduc4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=deKy5nBf7hs:nL4pwvaduc4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=deKy5nBf7hs:nL4pwvaduc4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=deKy5nBf7hs:nL4pwvaduc4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=deKy5nBf7hs:nL4pwvaduc4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=deKy5nBf7hs:nL4pwvaduc4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/deKy5nBf7hs" height="1" width="1"/&gt;</description>
	<pubDate>27 Feb 2009 14:11:08 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/deKy5nBf7hs/eau0904.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0904.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0904.html</feedburner:origLink></item>
	<item>
	<title>The Trojan Horse for IT</title>
	<description>Allen, Paul | E-Mail Advisors | 25 February 2009 | Business-IT Strategies; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Like me, you may already be all too well aware of the Trojan horse as a security threat and use regular virus checks to avoid the problem. Yet, the same idea -- smuggling through content under a label that refers to something else -- can be used with a much more positive effect.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090225.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nI9t6q4i4bM:Wa0IrmIE6ak:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nI9t6q4i4bM:Wa0IrmIE6ak:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nI9t6q4i4bM:Wa0IrmIE6ak:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nI9t6q4i4bM:Wa0IrmIE6ak:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nI9t6q4i4bM:Wa0IrmIE6ak:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nI9t6q4i4bM:Wa0IrmIE6ak:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nI9t6q4i4bM:Wa0IrmIE6ak:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nI9t6q4i4bM" height="1" width="1"/&gt;</description>
	<pubDate>25 Feb 2009 14:03:09 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nI9t6q4i4bM/bit090225.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090225.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090225.html</feedburner:origLink></item>
	<item>
	<title>Death by Architecture</title>
	<description>Rosen, Mike | E-Mail Advisors | 25 February 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I recently received a large architecture document to review. After poring through a few hundred pages of text and drawings, I was impressed by how much work and thought had gone into it yet how utterly useless it was. Now, don't get me wrong: it's not that architecture is unimportant; quite the opposite. The classic, big architecture document is just the wrong way to deliver it. I had hoped that the industry had gotten past these kinds of deliverables; apparently I was wrong.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090225.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7OjTU2dRvrc:VqBNJO1yAfo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7OjTU2dRvrc:VqBNJO1yAfo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7OjTU2dRvrc:VqBNJO1yAfo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7OjTU2dRvrc:VqBNJO1yAfo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7OjTU2dRvrc:VqBNJO1yAfo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7OjTU2dRvrc:VqBNJO1yAfo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7OjTU2dRvrc:VqBNJO1yAfo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/7OjTU2dRvrc" height="1" width="1"/&gt;</description>
	<pubDate>3 Mar 2009 14:02:15 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/7OjTU2dRvrc/ea090225.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090225.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090225.html</feedburner:origLink></item>
	<item>
	<title>Value from the Intersection of Business and Technology Architecture: Part I</title>
	<description>Bess, Charles E.; Mullis, Philip S. | Executive Updates | 20 February 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;The buildup of application strata is a side effect of the success of various projects in isolation. Addressing this issue is exactly where architecture adds to and enables business value to be maximized. In this two-part Executive Update series, we consider the stages and functions of architecture, as well as architects themselves and describe why architecture maximizes business value.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0903.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZVfhMjxWMC0:ZX6iNRNQyqY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZVfhMjxWMC0:ZX6iNRNQyqY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZVfhMjxWMC0:ZX6iNRNQyqY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZVfhMjxWMC0:ZX6iNRNQyqY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZVfhMjxWMC0:ZX6iNRNQyqY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZVfhMjxWMC0:ZX6iNRNQyqY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZVfhMjxWMC0:ZX6iNRNQyqY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ZVfhMjxWMC0" height="1" width="1"/&gt;</description>
	<pubDate>20 Feb 2009 13:55:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ZVfhMjxWMC0/eau0903.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0903.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0903.html</feedburner:origLink></item>
	<item>
	<title>All Aboard the SOA Governance Train: Laying down the Track</title>
	<description>Allen, Paul | E-Mail Advisors | 18 February 2009 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;Despite the promises of service-oriented architecture (SOA), many organizations are increasingly encountering difficult governance issues as they start to ramp up their early SOA efforts. For example, if a service is to be widely used, then who owns the service, who funds it, who is allowed to provide it, who is allowed to use it, and how is it specified in a way that consumers can readily understand?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090218.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=S8843q72"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=BY86TfB3"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=BY86TfB3" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=MDWudLJz"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=MDWudLJz" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=QwL2HIzs"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=QwL2HIzs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/8tuTwzALyHU" height="1" width="1"/&gt;</description>
	<pubDate>19 Feb 2009 22:19:00 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/8tuTwzALyHU/ea090218.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090218.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090218.html</feedburner:origLink></item>
	<item>
	<title>Good Timing: Conducting Architecture in Tune with the Mood</title>
	<description>Allen, Paul | E-Mail Advisors | 11 February 2009 | Business-IT Strategies; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Gaining momentum for any type of IT architectural effort partly depends on the organization's level of architecture adoption maturity. Push too soon, and the necessary infrastructure won't have had time to mature, and your solutions won't scale. Time it too late, and your architecture effort will be forever playing technology catch-up, squeezed off the front page of the business and IT agenda by other initiatives with more pressing cases for action. Architecture maturity, however, is only part of the story.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090211.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=nUVQxaVD"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=wqM6Ujke"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=wqM6Ujke" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=lny4zpL1"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=lny4zpL1" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=9DMx47xq"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=9DMx47xq" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/N4M8kDr8TGc" height="1" width="1"/&gt;</description>
	<pubDate>11 Feb 2009 22:01:37 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/N4M8kDr8TGc/bit090211.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090211.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090211.html</feedburner:origLink></item>
	<item>
	<title>Taking the Long View Means Thinking Like an Enterprise Architect</title>
	<description>Orr, Ken | E-Mail Advisors | 11 February 2009 | Enterprise Architecture; Business Intelligence &lt;BR&gt;&lt;BR&gt;Here is a question: "What will the computing environment of a midsize enterprise be in 2020?" That is, it seems to me, a fair question. The year 2020 is just about 11 years away (10 years if you're in government), and a decade is just a blink of the eye. What programming language will you be developing systems in: Java, .NET, Python, Ruby -- something else? What database management system will you be using? What computing platform will your organization be using: centralized, decentralized, on the cloud?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090211.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=9z8Uqj4O"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=VrkNn6a9"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=VrkNn6a9" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=X5yvPivG"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=X5yvPivG" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=7R0XCRy7"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=7R0XCRy7" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/NV3sylSkWN4" height="1" width="1"/&gt;</description>
	<pubDate>11 Feb 2009 22:00:12 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/NV3sylSkWN4/ea090211.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090211.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090211.html</feedburner:origLink></item>
	<item>
	<title>Producing Agile Applications</title>
	<description>Sims, Oliver | Executive Reports | 01 January 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Application developers need to handle a surprising amount of software technology. Platform suppliers cater to many architectural styles, thereby leaving a gap between their platforms and an application's business function. Filling this gap takes time and effort and reduces the "agility" -- simplicity and resilience -- of the application code. This Executive Report by Oliver Sims first identifies how software technology can be clearly separated from business function and then proposes simplifying approaches that can make the business function more "agile." Together, these elements can significantly reduce the time needed to develop distributed enterprise applications.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/reports/2009/01/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=604Cqp3m"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Jvf7yOzL"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Jvf7yOzL" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=v1lhIX14"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=v1lhIX14" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=l3RooMFO"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=l3RooMFO" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/6EwvaVYVc2I" height="1" width="1"/&gt;</description>
	<pubDate>1 Jan 2009 14:24:58 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/6EwvaVYVc2I/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2009/01/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2009/01/index.html</feedburner:origLink></item>
	<item>
	<title>Managing Risk with SOA</title>
	<description>Allen, Paul | Executive Updates | 09 February 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;There has rightly been much focus of late on service-oriented architecture (SOA) governance and managing the risks of SOA.1 In this Executive Update, we explain how SOA -- properly done -- is in fact a powerful mechanism for managing both IT and business risks.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0902.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=wRyYFSyW"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=GrJswwxa"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=GrJswwxa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=GTJPIcvl"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=GTJPIcvl" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=iu1eF4nV"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=iu1eF4nV" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/tIqfBkJUAr0" height="1" width="1"/&gt;</description>
	<pubDate>9 Feb 2009 13:39:32 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/tIqfBkJUAr0/eau0902.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0902.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0902.html</feedburner:origLink></item>
	<item>
	<title>Book Review: A Fresh Look at Building the Agile Enterprise</title>
	<description>Rosen, Mike | E-Mail Advisors | 04 February 2009 | Enterprise Architecture; Business-IT Strategies&lt;BR&gt;&lt;BR&gt;Are you ready for a fresh perspective on agility, architecture, and SOA? Then check out Building the Agile Enterprise with SOA, BPM and MBM, a book by Fred Cummins (Morgan Kaufmann, 2008). Don't let the title scare you away. While it does cover service-oriented architecture (SOA), business process management (BPM), and model-based management (MBM), and gives you a good overview of these technologies, this is more a book about structuring the agile enterprise from a business perspective.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090204.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=NCvN3Sib"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=jpW1GF8D"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=jpW1GF8D" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=TlIJs5NV"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=TlIJs5NV" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Y30AI5qR"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Y30AI5qR" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_hWzGvpHMck" height="1" width="1"/&gt;</description>
	<pubDate>4 Feb 2009 13:33:10 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_hWzGvpHMck/ea090204.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090204.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090204.html</feedburner:origLink></item>
	<item>
	<title>Open Source Java Frameworks: Strengths and Weaknesses</title>
	<description>Welsh, Tom | Executive Updates | 04 February 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;This is the second in a series of Executive Updates examining the results of a recent Cutter Consortium survey on the subject of open source Java frameworks (OSJFs). Part I looked at the conventional Java EE model, with particular focus on its strengths and weaknesses.1 It turns out that respondents see Java EE's platform neutrality as its greatest asset, followed by tool support, scalability, maturity, and robustness. On the other hand, there is widespread feeling that Java EE suffers from excessive complexity and its consequences. These include a formidably steep learning curve, difficulty in finding suitably experienced developers, and delays in adopting the latest technical improvements.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0901.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=dodY4Mhr"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=eGRRtJeY"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=eGRRtJeY" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=jbxVjmcl"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=jbxVjmcl" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=lqrO9bzL"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=lqrO9bzL" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/okaAEL6qi80" height="1" width="1"/&gt;</description>
	<pubDate>4 Feb 2009 13:31:58 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/okaAEL6qi80/eau0901.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0901.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0901.html</feedburner:origLink></item>
	<item>
	<title>The King (SOA) Is Dead; Long Live the King</title>
	<description>Allen, Paul | E-Mail Advisors | 28 January 2009 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;A recent blog post from the Burton Group on the alleged "Death of SOA" has been causing quite a stir.1 The contention is that the bad economic situation has finally finished the "SOAsaurus" off and that we must now concentrate on services, along with mashups, cloud computing, and software as a service (SaaS) -- and not service-oriented architecture (SOA).&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090128.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=dErAVkxv"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=ef7sN6vR"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=ef7sN6vR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=20ycYAkC"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=20ycYAkC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=eq572mOs"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=eq572mOs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/G-FVr8bR5mQ" height="1" width="1"/&gt;</description>
	<pubDate>28 Jan 2009 19:05:40 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/G-FVr8bR5mQ/ea090128.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090128.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090128.html</feedburner:origLink></item>
	<item>
	<title>EA Resolutions for '09: Roadmap, 2.0, Good Books, Value</title>
	<description>Rosen, Mike | E-Mail Advisors | 21 January 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;As 2009 brings dramatic change to the economy, politics, and IT, some consistency might be in order. So, as I have in the past, I've devoted my first Advisor of the year to suggestions for New Year's resolutions.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090121.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=h6dxqEBS"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=8vW5uFzD"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=8vW5uFzD" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=8VjiRFm1"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=8VjiRFm1" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=iMlCNj7v"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=iMlCNj7v" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/M-a7OGNyz40" height="1" width="1"/&gt;</description>
	<pubDate>21 Jan 2009 18:54:53 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/M-a7OGNyz40/ea090121.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090121.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090121.html</feedburner:origLink></item>
	<item>
	<title>SOA Enables Agile Methods</title>
	<description>Cummins, Fred A. | Executive Updates | 16 January 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Service-oriented architecture (SOA) provides the basis for structuring the business and supporting applications as a composition of relatively autonomous services that interact through well-defined interfaces. An otherwise large, monolithic project comes to comprise multiple small projects, each defined to support the adaptation or development of a distinct business capability. These small projects are amenable to agile methods.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0824.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=7fB5F7BW"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=3YRwfvwh"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=3YRwfvwh" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=UbCO9eQY"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=UbCO9eQY" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=tIavn4JX"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=tIavn4JX" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/tdpMitxUQNU" height="1" width="1"/&gt;</description>
	<pubDate>16 Jan 2009 18:48:55 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/tdpMitxUQNU/eau0824.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0824.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0824.html</feedburner:origLink></item>
	<item>
	<title>The 31-Square-Foot Architecture</title>
	<description>Coldewey, Jens | E-Mail Advisors | 15 January 2009 | Agile Project Management; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;How much architecture does an agile team need up front? Most agile methods are surprisingly silent when it comes to this question. Scrum regards architecture as an issue the team has to deal with on its own discretion -- and thus does not include any advice. In Crystal Clear: A Human-Powered Methodology for Small Teams, Cutter Senior Consultant Alistair Cockburn suggests having a lead designer who is responsible for creating the system architecture description -- "usually fairly early in the first iteration" -- but also emphasizes that "the architecture will probably evolve" and gives two strategies to help evolving: Walking Skeleton and Incremental Rearchitecture. XP finally suggests using a metaphor to keep up the technical vision of the system; unfortunately, one of the most neglected practices of XP. XP also relies heavily on refactoring to evolve the architecture in addition to unit tests to scaffold it. In the second edition of his book Extreme Programming Explained, Cutter Senior Consultant Kent Beck finally introduced the architect as a role in the XP team, emphasizing that, "Architects sign up for programming tasks just like any programmer."&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/project/fulltext/advisor/2009/apm090115.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=jj7EYYD7"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=EiuCAK0m"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=EiuCAK0m" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=sU7aevEa"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=sU7aevEa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=x0IdrZoE"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=x0IdrZoE" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/w79Vk9a7W3I" height="1" width="1"/&gt;</description>
	<pubDate>15 Jan 2009 16:16:53 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/w79Vk9a7W3I/apm090115.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2009/apm090115.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2009/apm090115.html</feedburner:origLink></item>
	<item>
	<title>Enabling Your Solution Projects with SOA</title>
	<description>Allen, Paul | E-Mail Advisors | 14 January 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Despite the reality of service-oriented business -- as evidenced by partnering, collaboration, outsourcing, core competency focus, and the like -- many software solution projects aimed at solving business problems do not yet use service-oriented architecture (SOA) as a key enabler. I hear a variety of reasons from project managers for this, including the following:&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090114.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=J6Ga70tX"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=wn141sfx"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=wn141sfx" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=GZQtN7NF"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=GZQtN7NF" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=co2WHByK"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=co2WHByK" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/JcjHBbfv65c" height="1" width="1"/&gt;</description>
	<pubDate>14 Jan 2009 16:10:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/JcjHBbfv65c/ea090114.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090114.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090114.html</feedburner:origLink></item>
	<item>
	<title>Bailing Out IT's Infrastructure</title>
	<description>Orr, Ken | E-Mail Advisors | 07 January 2009 | Enterprise Architecture; Business-IT Strategies; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;This is the time of year when everyone makes resolutions and projects what they'd like to see in the new year. As I thought about what CIOs could wish for, it occurred to me that they might wish for inclusion of US President Elect Barack Obama's Infrastructure Investment Program for 2009. Clearly, we need to "invest" in roads, bridges, and electrical and telecommunications networks; why not some investment in one of the most significant portions of the economy: business enterprise architecture infrastructures and knowledge management.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090107.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=mXCWCXSL"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=PVm5Q4sR"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=PVm5Q4sR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=uasOLuyI"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=uasOLuyI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=kJ2Q37e5"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=kJ2Q37e5" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/PDNpDAVkwqo" height="1" width="1"/&gt;</description>
	<pubDate>7 Jan 2009 15:53:33 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/PDNpDAVkwqo/ea090107.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090107.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090107.html</feedburner:origLink></item>
	<item>
	<title>Open Source Java Frameworks: Strengths and Weaknesses of Java EE Provide Motivation for OSJF</title>
	<description>Welsh, Tom | Executive Updates | 07 January 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;This is the first of a series of Executive Updates that examines the results of a recent Cutter Consortium survey on the subject of open source Java frameworks (OSJF). Here in Part I, I look at the reasons behind the recent surge in popularity of OSJF, which mostly arise from dissatisfaction with enterprise Java.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0823.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=MsMUnRqN"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=apRrFEN7"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=apRrFEN7" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=oGh7W3Yw"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=oGh7W3Yw" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=qZHZCYU5"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=qZHZCYU5" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/96oHWw3pVoU" height="1" width="1"/&gt;</description>
	<pubDate>7 Jan 2009 15:52:18 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/96oHWw3pVoU/eau0823.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0823.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0823.html</feedburner:origLink></item>
	<item>
	<title>SoaML: A Fresh Modeling Language for SOA</title>
	<description>Rosen, Mike | E-Mail Advisors | 31 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;So, for the domain of services and SOA, it should be no surprise that a domain-specific, UML profile has been developed by the OMG. Under development for the past two years, SoaML, the UML profile for services, has just been approved by the OMG Architecture Board and is well on its way through the lengthy path of standardization.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081231.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=2x41jOkk"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=fBIZuYzq"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=fBIZuYzq" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=TwYkdIjU"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=TwYkdIjU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=otKLtrW5"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=otKLtrW5" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Nfh4YqU33R4" height="1" width="1"/&gt;</description>
	<pubDate>31 Dec 2008 15:38:33 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Nfh4YqU33R4/ea081231.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081231.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081231.html</feedburner:origLink></item>
	<item>
	<title>Joined-Up Service Sourcing and Usage</title>
	<description>Allen, Paul | Executive Reports | 01 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;While effective service sourcing strategies are absolutely critical for effective outsourcing, they are commonly misunderstood and ill defined. Worse still, the execution of these approaches tends to be somewhat isolated, both from the domain of software architecture and development and the world of business decision making. In this Executive Report by Paul Allen, we take an inclusive approach to service sourcing, explaining in particular how SOA can be used to facilitate decisions on outsourcing and how an SOA center of excellence can work as a unit to join up what are often disparate functions. We take the lid off the service sourcing can and explain how best to organize it in terms of processes, policies, roles, and artifacts.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/reports/2008/12/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=CPOPt4D6"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Rkuk9mNK"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Rkuk9mNK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=8MOqCmc8"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=8MOqCmc8" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=xA7aOPNn"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=xA7aOPNn" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9osGDD1lNBc" height="1" width="1"/&gt;</description>
	<pubDate>1 Dec 2008 19:54:11 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9osGDD1lNBc/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2008/12/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2008/12/index.html</feedburner:origLink></item>
	<item>
	<title>A Good Example of Business Rules in Action</title>
	<description>Hall, Curt | E-Mail Advisors | 24 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I've been covering business rules management systems (BRMS) for years now. However, I occasionally get the feeling that some still consider BRMS to be some sort of far-out technology. That's "far out" in the way of being too advanced or too out of reach for more mainstream end-user organizations to employ. This is understandable, because many of the BRMS applications cited tend to focus on advanced systems developed by high-tech companies. So, for this week's Advisor, I thought I'd give an example of how an end-user company outside of the high-tech, financial services, or insurance industries is benefiting from business rules technology.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081224.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=SJynw6eg"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=xbjUQwpy"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=xbjUQwpy" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=sWWcHZwx"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=sWWcHZwx" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=c8WwnOFP"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=c8WwnOFP" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9tuSFFjEMRA" height="1" width="1"/&gt;</description>
	<pubDate>24 Dec 2008 19:47:10 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9tuSFFjEMRA/ea081224.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081224.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081224.html</feedburner:origLink></item>
	<item>
	<title>Recently Added</title>
	<description>&lt;ul&gt;
&lt;LI&gt;&lt;A title="Executive Update" 
href="http://www.cutter.com/alignment/fulltext/updates/2008/bitu0817.html"&gt;The 
Technology Five-Step: Why You Need to Do the Strategy, Architecture, Delivery, 
Organization, and Efficiency Dance -- Now&lt;/A&gt; by Stephen J. Andriole&lt;/LI&gt;
&lt;LI&gt;&lt;A title="Executive Update" 
href="http://www.cutter.com/alignment/fulltext/updates/2008/bitu0819.html"&gt;Radical 
Delivery: How the Extreme Gets to Normal in 10 Steps&lt;/A&gt; by Stephen J. 
Andriole&lt;/LI&gt;
&lt;LI&gt;&lt;A title="Executive Report" 
href="http://www.cutter.com/risk/fulltext/reports/2008/03/index.html"&gt;Quality 
of Service: You Can't Measure What You Don't Specify!&lt;/A&gt; by Paul Allen&lt;/LI&gt;
&lt;LI&gt;&lt;A title="Council Opinion" 
href="http://www.cutter.com/trends/fulltext/reports/2008/09/index.html"&gt;Turning 
Stuff Off: The New Productivity Booster&lt;/A&gt; by Tim Lister and the Cutter 
Business Technology Council&lt;/LI&gt;
&lt;/ul&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=WWvGdzun"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=GRNeNyNz"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=GRNeNyNz" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=fJWG7YDk"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=fJWG7YDk" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=MYa4lswc"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=MYa4lswc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/BeCfW7HhLKk" height="1" width="1"/&gt;</description>
	<pubDate>29 Dec 2008 19:26:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/BeCfW7HhLKk/alignment.html</link>
	<feedburner:origLink>http://www.cutter.com/alignment.html</feedburner:origLink></item>
	<item>
	<title>Focusing on Components Means Missing the Big Picture</title>
	<description>Orr, Ken | E-Mail Advisors | 18 December 2008 | Business Technology Trends &amp;amp; Impacts; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I am always surprised to find myself in discussions with people who have architect titles and who have little feeling about the key concepts of architecture. Too many members of the current generation of technical experts have very little comprehension of what differentiates systems from programs or services. As a consequence, they and the companies that they counsel are doomed to a very limited set of options: 1) purchase and install packages, 2) hire outsourcers to develop systems that they are incapable of maintaining, or 3) make cosmetic changes to ever older core systems.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081218.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=wuj9fKzK"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=zeP1gx4s"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=zeP1gx4s" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Ld8shdqr"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Ld8shdqr" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=SHvhjpl2"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=SHvhjpl2" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/F1zvsMb4bzU" height="1" width="1"/&gt;</description>
	<pubDate>18 Dec 2008 19:19:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/F1zvsMb4bzU/btt081218.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081218.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081218.html</feedburner:origLink></item>
	<item>
	<title>For Architectural Fundamentals, Look to the Romans</title>
	<description>Rosen, Mike | E-Mail Advisors | 17 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;When we think about IT architecture, or talk about it, the desire to draw parallels with building architecture is often irresistible. Since I have just returned from a visit to Italy, I'm drawn to make some observations along these lines.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081217.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=r9yG0q9h"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=6CNqQBbT"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=6CNqQBbT" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=hqx1MJQG"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=hqx1MJQG" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=kqPurDPF"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=kqPurDPF" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/a3E2r55J80M" height="1" width="1"/&gt;</description>
	<pubDate>17 Dec 2008 19:10:01 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/a3E2r55J80M/ea081217.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081217.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081217.html</feedburner:origLink></item>
	<item>
	<title>Agile SOA Governance: Illusion or Reality?</title>
	<description>Allen, Paul | Executive Updates | 15 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Many service-oriented architecture (SOA) governance initiatives become bogged down in a bureaucracy that militates against the very agility that SOA promises in the first place. Is there a way to achieve agile SOA governance, or is this simply an illusion? Fortunately, our experiences show that there are responsive and practical approaches to SOA governance. As with most things in life, balance is the key. In this Executive Update, we consider how to introduce SOA governance in a planned yet incremental fashion, in small chunks, with respect to prioritized business outcomes and risks.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0822.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=LskKNqX2"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=kCkTX6VM"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=kCkTX6VM" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=v2PP3geK"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=v2PP3geK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=GcoMwRaR"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=GcoMwRaR" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/oTk1FT_bmes" height="1" width="1"/&gt;</description>
	<pubDate>15 Dec 2008 19:03:49 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/oTk1FT_bmes/eau0822.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0822.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0822.html</feedburner:origLink></item>
	<item>
	<title>Trends and Anti-Trends for 2009</title>
	<description>Kellen, Vince | E-Mail Advisors | 11 December 2008 | Business Technology Trends &amp;amp; Impacts; Business Intelligence; Enterprise Architecture; Sourcing &amp;amp; Vendor Relationships; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;With 2009 looming large, ugly, and just around the corner, it's time for the obligatory prognostications. Boy, is this difficult.... Hmmm. What will next year bring? Any wild guesses?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081211.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=f0fGCHmJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Cpp261cO"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Cpp261cO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Hi2qQ6zi"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=Hi2qQ6zi" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=PDmuaCCa"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=PDmuaCCa" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/h9uP8e_kmpI" height="1" width="1"/&gt;</description>
	<pubDate>11 Dec 2008 14:45:42 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/h9uP8e_kmpI/btt081211.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081211.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2008/btt081211.html</feedburner:origLink></item>
	<item>
	<title>The Universal Nature of Enterprise Architecture</title>
	<description>van Tyn, Jeroen | E-Mail Advisors | 10 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I've recently been observing a group of people attempting to develop a local food system for their community. What strikes me is that the principles of enterprise architecture (EA) that I've learned and used over the years are entirely relevant to this endeavor, despite the fact that IT has no role in it whatsoever.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081210.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=Mm6weMLr"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=JW2DlaNU"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=JW2DlaNU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=t6E9bfhR"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=t6E9bfhR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=qgBaIkcd"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=qgBaIkcd" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RMUNhvhzOYE" height="1" width="1"/&gt;</description>
	<pubDate>10 Dec 2008 14:41:37 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RMUNhvhzOYE/ea081210.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081210.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2008/ea081210.html</feedburner:origLink></item>
	<item>
	<title>Release Management Framework: Part I</title>
	<description>Konkol, Sebastian | Executive Reports | 01 November 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;This Executive Report by Sebastian Konkol focuses on the release management framework, which is a method involving the coordinated introduction of various software modifications to the production systems environment. The method aims at global optimization by building business value through the delivery of software modifications. The framework consists of a release implementation process, which provides a skeleton for work organization and progress assessment; strict definition of the release contents able to be altered throughout the process run; a set of environments giving means of iterative release contents validation; and interrelations with other processes related to technology management, such as configuration management, problem handling, or project management. The report also discusses a means of risk management, which is embedded in the method, as well as how the method relates to business value delivery processes.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/architecture/fulltext/reports/2008/11/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=9nnOEv6H"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=OMZSzPEI"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=OMZSzPEI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=XGif0sk1"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=XGif0sk1" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=q8oC4xYl"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=q8oC4xYl" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/jscSJEQNuvw" height="1" width="1"/&gt;</description>
	<pubDate>1 Nov 2008 17:11:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/jscSJEQNuvw/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture/fulltext/reports/2008/11/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture/fulltext/reports/2008/11/index.html</feedburner:origLink></item>
	<item>
	<title>EA to AE: Enterprise Architecture to Assets for the Enterprise</title>
	<description>Peterson, Mark | Executive Updates | 05 December 2008 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Many corporations and public-sector organizations are struggling with the increasingly rapid changes in the business and political environment. Market conditions, cost constraints, and technology implementations often bring stress to an IT organization. One of the most significant stress points is the lack of IT management's ability to effectively gain support for an enterprise architecture (EA) and provide a roadmap to generate asset value from IT investments.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0821.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=lS0UtvZK"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?d=41" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=VvXA6hAQ"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=VvXA6hAQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=OEMgAsaE"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=OEMgAsaE" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?a=3nZ3RYNy"&gt;&lt;img src="http://feeds.feedburner.com/~f/CutterConsortiumEnterpriseArchitecture?i=3nZ3RYNy" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/x8AM_96PNqw" height="1" width="1"/&gt;</description>
	<pubDate>5 Dec 2008 17:08:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/x8AM_96PNqw/eau0821.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0821.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2008/eau0821.html</feedburner:origLink></item>
	</channel></rss>
