<?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>How to Win at Punkin Chunkin and Architecture</title>
	<description>Rosen, Mike | E-Mail Advisors | 21 October 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I live in the state of New Hampshire, in the Northeast corner of the US. It's a major pumpkin-growing region of the country, and October is harvest season. Truckloads of pumpkins head south and west, and local farm stands are bursting with the orange globes. But what do you do with all the misshaped or leftover pumpkins? Chuck 'em, what else? A local farmer has turned this into an art with his World Champion 'Yankee Siege' Trebuchet (www.yankeesiege.com). This is something you really must see to comprehend. The top of the mast rises to more than 60 feet, and when the 12,000 pounds of weight are let loose, pumpkins fly for about 2,000 feet.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091021.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LZH8uwuVlGw:ORf2Dl2_2n4: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=LZH8uwuVlGw:ORf2Dl2_2n4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LZH8uwuVlGw:ORf2Dl2_2n4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LZH8uwuVlGw:ORf2Dl2_2n4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LZH8uwuVlGw:ORf2Dl2_2n4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LZH8uwuVlGw:ORf2Dl2_2n4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LZH8uwuVlGw:ORf2Dl2_2n4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/LZH8uwuVlGw" height="1" width="1"/&gt;</description>
	<pubDate>21 Oct 2009 22:47:31 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/LZH8uwuVlGw/ea091021.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091021.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091021.html</feedburner:origLink></item>
	<item>
	<title>Service Orienting Your Business Processes, Part IV: Multichannel Capability</title>
	<description>Allen, Paul | E-Mail Advisors | 14 October 2009 | Business-IT Strategies; Enterprise Architecture; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;Increasingly, we find business processes that are offered in alternative ways using different channels. For example, purchasing vehicle highway tax in the UK over the counter or online over the Internet. At the same time, as well as offering a process in its entirety over one channel, the same process can be supported by different channels at different points in the process.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit091014.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y9EGobT4dsA:YWYnuULp3ao: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=Y9EGobT4dsA:YWYnuULp3ao:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y9EGobT4dsA:YWYnuULp3ao:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y9EGobT4dsA:YWYnuULp3ao:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y9EGobT4dsA:YWYnuULp3ao:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y9EGobT4dsA:YWYnuULp3ao:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y9EGobT4dsA:YWYnuULp3ao:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Y9EGobT4dsA" height="1" width="1"/&gt;</description>
	<pubDate>14 Oct 2009 22:36:13 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Y9EGobT4dsA/bit091014.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit091014.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit091014.html</feedburner:origLink></item>
	<item>
	<title>Economics of Cloud Computing: 5 Operational Steps</title>
	<description>Orr, Ken; Maher, Andrew | E-Mail Advisors | 14 October 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In a recent interview, Mike Culver, the cloud computing evangelist for Amazon.com, clearly stated the cloud computing value statement for his company: "Amazon's goal is to take the fixed cost out of computing!" That's pretty simple. There has been a great deal of discussion of the TCO of one thing or another over the years, but rarely is the entirety of the operational overhead really factored in. We can learn what the TCO is for a desktop or a server or an Oracle product, for instance, but nobody goes to the trouble to include all of the factors involved.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091014.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=pXYqsPUAr4M:fIOoEUmU-74: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=pXYqsPUAr4M:fIOoEUmU-74:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=pXYqsPUAr4M:fIOoEUmU-74:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=pXYqsPUAr4M:fIOoEUmU-74:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=pXYqsPUAr4M:fIOoEUmU-74:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=pXYqsPUAr4M:fIOoEUmU-74:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=pXYqsPUAr4M:fIOoEUmU-74:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/pXYqsPUAr4M" height="1" width="1"/&gt;</description>
	<pubDate>14 Oct 2009 22:35:15 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/pXYqsPUAr4M/ea091014.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091014.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091014.html</feedburner:origLink></item>
	<item>
	<title>Webinar: BEAM 4.0</title>
	<description>Orr, Ken | Events | 20 October 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In 2005, Cutter Fellow Ken Orr introduced Business Enterprise Architecture Modeling (BEAM), a state-of-the-art methodology that uses a business-driven strategy as the key to the long-term success of your enterprise architecture program. In these 5 years since it was announced, BEAM, which is based on real-world applications, has been successfully used by organizations to create a long-view of their current and future business architecture needs. In this webinar, Ken Orr will talk about what’s been learned on these projects that used BEAM, how it’s been updated to make it an even more robust tool, and how you can use it to guide business-IT alignment, support business initiatives, enhance IT strategic planning, manage IT projects more effectively, and understand your organization’s total set of IT assets and their context. Ken will be joined by Enterprise Architecture Practice Director Mike Rosen, and Senior Consultant Mitchell Ummel, with whom he recently completed an award-winning project using the BEAM methodology. Register now to join Ken Orr for this webinar on Tuesday, October 20, 12:00 EDT (see your local time here).&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/events/multimedia/beam4.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wv0AAMn1eV4:cOch59M2qn0: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=wv0AAMn1eV4:cOch59M2qn0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wv0AAMn1eV4:cOch59M2qn0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wv0AAMn1eV4:cOch59M2qn0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wv0AAMn1eV4:cOch59M2qn0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wv0AAMn1eV4:cOch59M2qn0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wv0AAMn1eV4:cOch59M2qn0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/wv0AAMn1eV4" height="1" width="1"/&gt;</description>
	<pubDate>14 Oct 2009 00:58:00 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/wv0AAMn1eV4/beam4.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/beam4.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/beam4.html</feedburner:origLink></item>
	<item>
	<title>How EA Shapes Urban/Transportation Planning</title>
	<description>Orr, Ken | E-Mail Advisors | 07 October 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Enterprise architects often ask me why the Business Enterprise Architecture Modeling (BEAM) EA approach is based on an "urban/transportation model" rather than the "building architecture model" favored by many organizations and groups. The short answer has to do with the similarity of the model to actual enterprise architecture in both change and complexity. By and large, buildings don't change1 as much as urban areas; nor do they change for the same reasons. Urban areas, on the other hand, are constantly changing: new buildings replace old ones, whole areas are torn down in order to make way for new shopping centers or expressways.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091007.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dX1JZrmhzB0:3nr-oJ01PgU: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=dX1JZrmhzB0:3nr-oJ01PgU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dX1JZrmhzB0:3nr-oJ01PgU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dX1JZrmhzB0:3nr-oJ01PgU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dX1JZrmhzB0:3nr-oJ01PgU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dX1JZrmhzB0:3nr-oJ01PgU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dX1JZrmhzB0:3nr-oJ01PgU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/dX1JZrmhzB0" height="1" width="1"/&gt;</description>
	<pubDate>8 Oct 2009 00:52:26 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/dX1JZrmhzB0/ea091007.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091007.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea091007.html</feedburner:origLink></item>
	<item>
	<title>Defining Architectures for the Cloud, Part II</title>
	<description>Rosen, Mike | E-Mail Advisors | 30 September 2009 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;In my previous Advisor ("Defining Architectures for the Cloud, Part I," 23 September 2009), I looked at the enterprise architecture domains of business, information, and application and how cloud computing would affect those areas. This week, I'll finish the series on the cloud with the additional architectural considerations of technology, operations, security, and implementation.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090930.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YrfppIE3swY:eV7Qwi_CbGU: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=YrfppIE3swY:eV7Qwi_CbGU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YrfppIE3swY:eV7Qwi_CbGU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YrfppIE3swY:eV7Qwi_CbGU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YrfppIE3swY:eV7Qwi_CbGU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YrfppIE3swY:eV7Qwi_CbGU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YrfppIE3swY:eV7Qwi_CbGU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/YrfppIE3swY" height="1" width="1"/&gt;</description>
	<pubDate>30 Sep 2009 19:23:05 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/YrfppIE3swY/ea090930.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090930.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090930.html</feedburner:origLink></item>
	<item>
	<title>Why a Top-Down Approach Leads to Death by Dogma</title>
	<description>Kellen, Vince | E-Mail Advisors | 24 September 2009 | Business Technology Trends &amp;amp; Impacts; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Recently, a well-known IT advisory group brashly announced a "new" approach to enterprise architecture that it described as "emergent" and "nondeterministic," with central IT and its architects ceding some control and choice to constituents rather than trying to design and control everything. Wow. When I read the release, I had to pinch myself and ask, "What decade am I in? This news is so 1999." I double-checked the date on the release. Sure enough, it was this year. Why is this news in 2009?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090924.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afdsrlZsPL8:r7mwIrLrAtg: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=afdsrlZsPL8:r7mwIrLrAtg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afdsrlZsPL8:r7mwIrLrAtg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afdsrlZsPL8:r7mwIrLrAtg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afdsrlZsPL8:r7mwIrLrAtg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=afdsrlZsPL8:r7mwIrLrAtg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=afdsrlZsPL8:r7mwIrLrAtg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/afdsrlZsPL8" height="1" width="1"/&gt;</description>
	<pubDate>25 Sep 2009 01:46:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/afdsrlZsPL8/btt090924.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090924.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090924.html</feedburner:origLink></item>
	<item>
	<title>Service Orienting Your Business Processes, Part III: Adaptation</title>
	<description>Allen, Paul | E-Mail Advisors | 23 September 2009 | Business-IT Strategies; Enterprise Architecture; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;Many of our business processes -- operating over the Internet or otherwise -- remain wedded to a production-line mindset that is stuck in the world of the 1980s. A well-planned business process managemenht (BPM) and service-oriented architecture (SOA) strategy needs to encourage the use of services as a tool to improve processes and solve specific business problems. At the same time, organizational politics and the investments in BPM and SOA already made mean that we need to tread carefully.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090923.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=g0MiAhXH5fU:o7uwZB8bfPs: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=g0MiAhXH5fU:o7uwZB8bfPs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=g0MiAhXH5fU:o7uwZB8bfPs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=g0MiAhXH5fU:o7uwZB8bfPs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=g0MiAhXH5fU:o7uwZB8bfPs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=g0MiAhXH5fU:o7uwZB8bfPs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=g0MiAhXH5fU:o7uwZB8bfPs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/g0MiAhXH5fU" height="1" width="1"/&gt;</description>
	<pubDate>24 Sep 2009 01:43:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/g0MiAhXH5fU/bit090923.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090923.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090923.html</feedburner:origLink></item>
	<item>
	<title>Defining Architectures for the Cloud, Part I</title>
	<description>Rosen, Mike | E-Mail Advisors | 23 September 2009 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;In my previous two Advisors ("Selected Innovations in Cloud Products," 9 September 2009, and "SOA and the Cloud: Getting Past the Hype," 19 August 2009), I talked about the different styles of the cloud (infrastructure as a service [IaaS], platform as a service [PaaS], software as a service [SaaS], public, and private) and some of the products that are now available in those areas. This week, I look at the cloud from an enterprise architecture perspective. To do that, I start with the typical breakdown of EA into domains of business, information, application, and technology. For each domain, I look at some of the typical questions that are answered by that architecture and that will be affected by the cloud. I also list new questions that will need to be addressed.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090923.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0wJzlZtajn0:rRNaptltf6s: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=0wJzlZtajn0:rRNaptltf6s:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0wJzlZtajn0:rRNaptltf6s:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0wJzlZtajn0:rRNaptltf6s:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0wJzlZtajn0:rRNaptltf6s:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0wJzlZtajn0:rRNaptltf6s:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0wJzlZtajn0:rRNaptltf6s:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0wJzlZtajn0" height="1" width="1"/&gt;</description>
	<pubDate>29 Sep 2009 01:41:52 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0wJzlZtajn0/ea090923.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090923.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090923.html</feedburner:origLink></item>
	<item>
	<title>Getting Lean with the Line of Commoditization</title>
	<description>Allen, Paul | Executive Updates | 21 September 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;The idea of separating an organization's core functionality from its contextual functionality, with the view of concentrating its own resources on what it does best -- the "core" -- and outsourcing what others can do faster, cheaper, and better -- the "context" -- is highly prevalent and well known. Difficult economic times have served only to fuel the core/context strategy in one form (e.g., business process outsourcing) or another (e.g., cloud computing), making it highly influential in boardrooms keen to cut costs.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0918.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4pzIovfmZ9I:Hqlle6MrQvg: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=4pzIovfmZ9I:Hqlle6MrQvg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4pzIovfmZ9I:Hqlle6MrQvg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4pzIovfmZ9I:Hqlle6MrQvg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4pzIovfmZ9I:Hqlle6MrQvg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4pzIovfmZ9I:Hqlle6MrQvg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4pzIovfmZ9I:Hqlle6MrQvg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/4pzIovfmZ9I" height="1" width="1"/&gt;</description>
	<pubDate>22 Sep 2009 01:36:02 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/4pzIovfmZ9I/eau0918.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0918.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0918.html</feedburner:origLink></item>
	<item>
	<title>Visiting the Oracle</title>
	<description>Orr, Ken | E-Mail Advisors | 16 September 2009 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;In ancient times, the Oracle (the person, not the database) was someone to whom you addressed important questions. The answers that the Oracle gave were always true, but were often given in an elaborate code. I imagined recently that I took some of my clients' questions to a modern version of the Oracle for enlightenment. I imagined further that this modern Oracle allowed me three questions.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090916.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JOzJdorDME0:snle3u_WeJQ: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=JOzJdorDME0:snle3u_WeJQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JOzJdorDME0:snle3u_WeJQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JOzJdorDME0:snle3u_WeJQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JOzJdorDME0:snle3u_WeJQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JOzJdorDME0:snle3u_WeJQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JOzJdorDME0:snle3u_WeJQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/JOzJdorDME0" height="1" width="1"/&gt;</description>
	<pubDate>17 Sep 2009 01:28:50 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/JOzJdorDME0/ea090916.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090916.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090916.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Architects and Organizational Change: A Requirement or an Option?</title>
	<description>Teeuwen, Paul | Executive Updates | 10 September 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;As a CIO or enterprise architecture (EA) manager, you will have experienced that some of your enterprise architects seem to get along just fine with the user community, but others seem to run into arguments with their customers time and time again. These are problems that you have to solve, committing time and prestige to fix things while you do not understand why things got out of control in the first place. The first time I got this cry for help from the corporate EA manager of a large bank, I realized that it is not the quality of the architectural deliverables that makes the difference -- so what is it?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0917.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9nRKdObpXm8:MIysrwBnmGY: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=9nRKdObpXm8:MIysrwBnmGY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9nRKdObpXm8:MIysrwBnmGY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9nRKdObpXm8:MIysrwBnmGY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9nRKdObpXm8:MIysrwBnmGY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9nRKdObpXm8:MIysrwBnmGY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9nRKdObpXm8:MIysrwBnmGY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9nRKdObpXm8" height="1" width="1"/&gt;</description>
	<pubDate>10 Sep 2009 19:50:28 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9nRKdObpXm8/eau0917.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0917.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0917.html</feedburner:origLink></item>
	<item>
	<title>Selected Innovations in Cloud Products</title>
	<description>Rosen, Mike | E-Mail Advisors | 09 September 2009 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;In my last Advisor, "SOA and the Cloud: Getting Past the Hype" (19 August 2009), I introduced the main categories of cloud computing. This week, I'll cover some of the product innovations taking place in those categories. Of course, I can't begin to cover everything, so this is just a selection of things that I found interesting. I apologize in advance if I left out your favorite item.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090909.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rYdDkrqwDP0:lHTMY2VKB4k: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=rYdDkrqwDP0:lHTMY2VKB4k:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rYdDkrqwDP0:lHTMY2VKB4k:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rYdDkrqwDP0:lHTMY2VKB4k:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rYdDkrqwDP0:lHTMY2VKB4k:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rYdDkrqwDP0:lHTMY2VKB4k:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rYdDkrqwDP0:lHTMY2VKB4k:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/rYdDkrqwDP0" height="1" width="1"/&gt;</description>
	<pubDate>9 Sep 2009 19:46:26 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/rYdDkrqwDP0/ea090909.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090909.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090909.html</feedburner:origLink></item>
	<item>
	<title>Complex Event Processing: The Vendors</title>
	<description>Hall, Curt | E-Mail Advisors | 02 September 2009 | Enterprise Architecture; Business Intelligence &lt;BR&gt;&lt;BR&gt;As I pointed out in last week's Advisor (see "Complex Event Processing," 26 August 2009), complex event processing (CEP) remains an emerging technology that holds the promise of enabling companies to increase operational efficiency by providing a means to identify and interpret the effect of seemingly unrelated events taking place across the organization and then notifying the appropriate stakeholders with near zero latency.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090902.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1jWSgyWajQU:TX--bvhz1Rs: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=1jWSgyWajQU:TX--bvhz1Rs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1jWSgyWajQU:TX--bvhz1Rs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1jWSgyWajQU:TX--bvhz1Rs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1jWSgyWajQU:TX--bvhz1Rs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1jWSgyWajQU:TX--bvhz1Rs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1jWSgyWajQU:TX--bvhz1Rs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/1jWSgyWajQU" height="1" width="1"/&gt;</description>
	<pubDate>2 Aug 2009 19:37:03 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/1jWSgyWajQU/ea090902.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090902.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090902.html</feedburner:origLink></item>
	<item>
	<title>How to Measure Software Agility</title>
	<description>Allen, Paul | Executive Updates | 31 August 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Too often, the term "agility" is bandied about, especially in relation to SOA, without real meaning. For example, we are used to measuring the various quality attributes of a piece of software. Performance comes in the form of response time; capacity is expressed, among other things, in terms of bytes of storage; security is expressed in terms of freedom from denial-of-service attacks, and so forth. But what about agility? Is it just a good thing, as many seem to assume, like happiness or moral goodness? Or can we define it and measure it, as with performance, capacity, and security? Due to its importance in addressing ever-demanding and more complex business requirements, it is imperative to define and measure agility.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0916.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c3P5OZpIzkg:MjTf8zBnklU: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=c3P5OZpIzkg:MjTf8zBnklU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c3P5OZpIzkg:MjTf8zBnklU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c3P5OZpIzkg:MjTf8zBnklU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c3P5OZpIzkg:MjTf8zBnklU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c3P5OZpIzkg:MjTf8zBnklU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c3P5OZpIzkg:MjTf8zBnklU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/c3P5OZpIzkg" height="1" width="1"/&gt;</description>
	<pubDate>31 Aug 2009 19:31:31 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/c3P5OZpIzkg/eau0916.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0916.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0916.html</feedburner:origLink></item>
	<item>
	<title>New Additions to the Enterprise Architecture Resource Center</title>
	<description>&lt;LI&gt;&lt;A title=http://www.cutter.com/alignment/fulltext/updates/2009/bitu0909.html href="http://www.cutter.com/alignment/fulltext/updates/2009/bitu0909.html"&gt;Systems Breakdown Case Study: A Square Peg and a Round Hole&lt;/A&gt; by Phil Simon 
&lt;LI&gt;&lt;A title=http://www.cutter.com/sourcing/fulltext/updates/2009/srcu0907.html href="http://www.cutter.com/sourcing/fulltext/updates/2009/srcu0907.html"&gt;Holistic Service-Oriented Management&lt;/A&gt; by Paul Allen 
&lt;LI&gt;&lt;A title=http://www.cutter.com/benchmark/fulltext/2009/06/index.html href="http://www.cutter.com/benchmark/fulltext/2009/06/index.html"&gt;Life Is Service: Even for the IT Shop&lt;/A&gt; by Gabriele Piccoli 
&lt;LI&gt;&lt;A title=http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906a.html href="http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906a.html"&gt;IT Service Management: Improving Customer Service Through Better Relationships&lt;/A&gt; by Geneviève Bassellier and Ron Cenfetelli 
&lt;LI&gt;&lt;A title=http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906b.html href="http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906b.html"&gt;IT Service Management: Culture as a Solution?&lt;/A&gt; by Bob Furniss 
&lt;LI&gt;&lt;A title=http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906c.html href="http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906c.html"&gt;IT Service: It Begins with Business Knowledge&lt;/A&gt; by Gabriele Piccoli 
&lt;LI&gt;&lt;A title=http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906d.html href="http://www.cutter.com/benchmark/fulltext/2009/06/cbr0906d.html"&gt;IT Service Management Survey Data&lt;/A&gt;&lt;/LI&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:yhEYg9X3ork: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=vOA-u4rXe0w:yhEYg9X3ork:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:yhEYg9X3ork:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:yhEYg9X3ork:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:yhEYg9X3ork:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:yhEYg9X3ork:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:yhEYg9X3ork:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/vOA-u4rXe0w" height="1" width="1"/&gt;</description>
	<pubDate>31 Aug 2009 16:00:18 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/vOA-u4rXe0w/architecture.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture.html</feedburner:origLink></item>
	<item>
	<title>Agile Service Orientation: Avoiding the "Ivory Tower"</title>
	<description>Allen, Paul | Executive Reports | 01 August 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;A harsh economic recession calling for renewed cost reduction with an emphasis on tactical solution-delivery projects causes concern over the effectiveness of enterprise service-oriented architecture (SOA) and puts agile back in the limelight. SOA and agile methodologies are commonly seen as opposites, but opposites that don't attract. On the one hand, agile methodologies emphasize the short game, human interplay, and exploration, while SOA is inherently a long game that is about discipline and formality. Each approach is not without success. At the same time, agile projects have often struggled with delivering the long-term quality and scalability that SOA promises. Conversely, SOA efforts are often plagued with difficulties in delivering rapid business value. Is it really possible to have the best of both worlds? Or is "agile SOA" a contradiction in terms? In this Executive Report, Paul Allen argues that, yes, there are many ways in which agile and SOA can work effectively together and provide guidelines for achieving a balanced approach.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/reports/2009/08/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6y7wBtQ4KP4:HOEUrcIqwGM: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=6y7wBtQ4KP4:HOEUrcIqwGM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6y7wBtQ4KP4:HOEUrcIqwGM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6y7wBtQ4KP4:HOEUrcIqwGM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6y7wBtQ4KP4:HOEUrcIqwGM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6y7wBtQ4KP4:HOEUrcIqwGM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6y7wBtQ4KP4:HOEUrcIqwGM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/6y7wBtQ4KP4" height="1" width="1"/&gt;</description>
	<pubDate>1 Aug 2009 15:55:48 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/6y7wBtQ4KP4/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2009/08/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2009/08/index.html</feedburner:origLink></item>
	<item>
	<title>Service-Orienting Agile: Enhancing the Process</title>
	<description>Allen, Paul | E-Mail Advisors | 27 August 2009 | Agile Project Management; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In this Advisor, we'll consider some tactics for employing service-oriented architecture (SOA) techniques to improve your agile projects -- in other words, at service-orienting agile. While our focus is very much on enhancing the process of agile, the intent here is to stay in tune with agile principles and avoid the stifling bureaucracy that has plagued traditional software processes.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/project/fulltext/advisor/2009/apm090827.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wqgCIytBz-s:YYoowjd3z8A: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=wqgCIytBz-s:YYoowjd3z8A:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wqgCIytBz-s:YYoowjd3z8A:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wqgCIytBz-s:YYoowjd3z8A:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wqgCIytBz-s:YYoowjd3z8A:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wqgCIytBz-s:YYoowjd3z8A:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wqgCIytBz-s:YYoowjd3z8A:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/wqgCIytBz-s" height="1" width="1"/&gt;</description>
	<pubDate>27 Aug 2009 15:45:10 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/wqgCIytBz-s/apm090827.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2009/apm090827.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2009/apm090827.html</feedburner:origLink></item>
	<item>
	<title>Service Orienting Your Business Processes, Part II: Partner Connectivity</title>
	<description>Allen, Paul | E-Mail Advisors | 26 August 2009 | Business-IT Strategies; Enterprise Architecture; Sourcing &amp;amp; Vendor Relationships &lt;BR&gt;&lt;BR&gt;Service-oriented viewpoints are a way of gaining early measurable business value through reuse of existing services, including external cloud services as well as internal legacy services. Think of each viewpoint as a different pair of spectacles through which the analyst views the process. There are eight viewpoints; in the previous Advisor (see "Service Orienting Your Business Processes, Part I: Customer Fit and Transparence," 12 August 2009), I described the transparency and customer-fit viewpoints. In this Advisor, I'm going to concentrate on the partner-connectivity viewpoint.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090826.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=keVHTBR5z0Q:Rz9bNH5Kcj4: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=keVHTBR5z0Q:Rz9bNH5Kcj4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=keVHTBR5z0Q:Rz9bNH5Kcj4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=keVHTBR5z0Q:Rz9bNH5Kcj4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=keVHTBR5z0Q:Rz9bNH5Kcj4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=keVHTBR5z0Q:Rz9bNH5Kcj4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=keVHTBR5z0Q:Rz9bNH5Kcj4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/keVHTBR5z0Q" height="1" width="1"/&gt;</description>
	<pubDate>26 Aug 2009 15:39:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/keVHTBR5z0Q/bit090826.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090826.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090826.html</feedburner:origLink></item>
	<item>
	<title>Complex Event Processing</title>
	<description>Hall, Curt | E-Mail Advisors | 26 August 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Complex event processing (CEP) generated a lot of hype in 2007 and 2008. By 2009, however, the hype has died down. With the recent "Community Technology Preview" release of Microsoft SQL Server StreamInsight, I expect the hype meter to begin revving up once again. No doubt about it, StreamInsight is an important development because it heralds Microsoft's eventual entry into the CEP market, which although currently small, is expected to grow considerably over the next few years. And, although pioneers hate to hear this, Microsoft's entry will also help to "legitimize" CEP as an enterprise application by focusing attention on what the technology has to offer.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090826.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Hvp3cQnfv9k:LgwyVkkA5TM: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=Hvp3cQnfv9k:LgwyVkkA5TM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Hvp3cQnfv9k:LgwyVkkA5TM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Hvp3cQnfv9k:LgwyVkkA5TM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Hvp3cQnfv9k:LgwyVkkA5TM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Hvp3cQnfv9k:LgwyVkkA5TM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Hvp3cQnfv9k:LgwyVkkA5TM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Hvp3cQnfv9k" height="1" width="1"/&gt;</description>
	<pubDate>26 Aug 2009 15:22:52 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Hvp3cQnfv9k/ea090826.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090826.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090826.html</feedburner:origLink></item>
	<item>
	<title>Feature vs. Component Teams, Part II: Separate Teams</title>
	<description>Highsmith, Jim | E-Mail Advisors | 20 August 2009 | Agile Project Management; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Recently, looking at scaling issues for a couple of multinational organizations, the issue of feature teams (customer-oriented) versus component teams (technically oriented) arose again. In an earlier Advisor (see "Feature vs. Component Teams," 6 August 2009), I proposed a three-tiered solution: projects with a single-feature team and specialists, projects with multiple feature teams and virtual component teams, and projects with multiple feature and component teams. This Advisor addresses the separate feature team tier.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/project/fulltext/advisor/2009/apm090820.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=z1G2yR_jKn8:dJXiBMuWgcc: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=z1G2yR_jKn8:dJXiBMuWgcc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=z1G2yR_jKn8:dJXiBMuWgcc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=z1G2yR_jKn8:dJXiBMuWgcc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=z1G2yR_jKn8:dJXiBMuWgcc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=z1G2yR_jKn8:dJXiBMuWgcc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=z1G2yR_jKn8:dJXiBMuWgcc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/z1G2yR_jKn8" height="1" width="1"/&gt;</description>
	<pubDate>20 Aug 2009 15:15:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/z1G2yR_jKn8/apm090820.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2009/apm090820.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2009/apm090820.html</feedburner:origLink></item>
	<item>
	<title>SOA and the Cloud: Getting Past the Hype</title>
	<description>Rosen, Mike | E-Mail Advisors | 19 August 2009 | Enterprise Architecture; Sourcing &amp;amp; Vendor Relationships; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;I suppose I ought to know better, and I do, but the marketing hype still never ceases to impress me. The latest victim: "the cloud." It is reported by our friends in the hype-cycle department that cloud computing is at the pinnacle of being overblown. This is characterized by vagueness in the marketplace, many different definitions of what it means, everyone and their brother jumping on the bandwagon, and of course the pathetic marketing literature with claims of being "in the cloud, cloud friendly, cloud based," and more. Note to marketers: here’s a dollar; buy yourself a clue!&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090819.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-7WhQ2N8Tgo:k2ZAE2AnYPM: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=-7WhQ2N8Tgo:k2ZAE2AnYPM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-7WhQ2N8Tgo:k2ZAE2AnYPM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-7WhQ2N8Tgo:k2ZAE2AnYPM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-7WhQ2N8Tgo:k2ZAE2AnYPM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-7WhQ2N8Tgo:k2ZAE2AnYPM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-7WhQ2N8Tgo:k2ZAE2AnYPM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/-7WhQ2N8Tgo" height="1" width="1"/&gt;</description>
	<pubDate>19 Aug 2009 15:11:52 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/-7WhQ2N8Tgo/ea090819.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090819.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090819.html</feedburner:origLink></item>
	<item>
	<title>Service Orienting Your Business Processes, Part I: Customer Fit and Transparence</title>
	<description>Allen, Paul | E-Mail Advisors | 12 August 2009 | Business-IT Strategies; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Service-oriented viewpoints, which I outlined in an earlier Update (see "Service-Oriented Viewpoints," Vol. 12, No. 1.), provide a useful, low-risk approach that can help leverage your investment in existing process models and services as part of a well-planned business-IT alignment strategy. There are eight viewpoints -- transparency, customer fit, partner connectivity, adaptation, multichannel capability, optimization, one-stop experience, and governance -- that can be applied in various ways to improve an existing business process design (typically in the form of a swim-lane diagram) using services. Think of each viewpoint as a different pair of spectacles through which the analyst views the process. In this Advisor, I'll home in on the transparence and customer-fit viewpoints.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090812.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cQyIjejZCO8:czS1KSjSG-8: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=cQyIjejZCO8:czS1KSjSG-8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cQyIjejZCO8:czS1KSjSG-8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cQyIjejZCO8:czS1KSjSG-8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cQyIjejZCO8:czS1KSjSG-8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cQyIjejZCO8:czS1KSjSG-8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cQyIjejZCO8:czS1KSjSG-8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/cQyIjejZCO8" height="1" width="1"/&gt;</description>
	<pubDate>12 Aug 2009 15:01:28 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/cQyIjejZCO8/bit090812.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090812.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2009/bit090812.html</feedburner:origLink></item>
	<item>
	<title>Clouds Roll In: The Changing Face of IT</title>
	<description>Davis, Christine | E-Mail Advisors | 12 August 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Utility IT support and systems development for small, medium-sized, and large companies have been and will continue to be transitioned to a service that is supported and managed by external IT service providers. This transition is continuing for many reasons, and the two most significant are reduced cost and the fact that utility IT does not provide differentiation that leads to competitive advantage.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090812.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ot8DSzGs1fA:wPbdXNCQ9oM: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=ot8DSzGs1fA:wPbdXNCQ9oM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ot8DSzGs1fA:wPbdXNCQ9oM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ot8DSzGs1fA:wPbdXNCQ9oM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ot8DSzGs1fA:wPbdXNCQ9oM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ot8DSzGs1fA:wPbdXNCQ9oM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ot8DSzGs1fA:wPbdXNCQ9oM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ot8DSzGs1fA" height="1" width="1"/&gt;</description>
	<pubDate>12 Aug 2009 14:55:07 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ot8DSzGs1fA/ea090812.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090812.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090812.html</feedburner:origLink></item>
	<item>
	<title>A Forensic Approach to Information Systems Development: Part II -- Ways to Fix the Problem</title>
	<description>Bailey, Ian | Executive Updates | 11 August 2009 | Enterprise Architecture In the first of this two-part Executive Update series,1 I took a swipe at the currently accepted approach to systems development. My argument was that if a system is to adequately support a business, the information it handles must be rigorously derived from the business itself. By producing a process model, then an information model, then a data model, and then handing it all over to an implementation team, we can end up somewhat removed from the reality of the business. The people responsible for each of these steps in the chain usually don't have a good understanding of each other's specialities, and the result can be "Chinese whispers."http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0915.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=VKPArmwav8c:VvINT9yL128: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=VKPArmwav8c:VvINT9yL128:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=VKPArmwav8c:VvINT9yL128:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=VKPArmwav8c:VvINT9yL128:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=VKPArmwav8c:VvINT9yL128:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=VKPArmwav8c:VvINT9yL128:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=VKPArmwav8c:VvINT9yL128:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/VKPArmwav8c" height="1" width="1"/&gt;</description>
	<pubDate>10 Aug 2009 14:48:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/VKPArmwav8c/eau0915.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0915.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0915.html</feedburner:origLink></item>
	<item>
	<title>Love of Coffee, and What's Agile Got to Do With It?</title>
	<description>Rosen, Mike | E-Mail Advisors | 05 August 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;A few weeks ago, I had a little electrical incident at my house. After the fire department left and the mess was cleaned up, we took stock of the damage. Except for the offending surge "protector" that caught fire, our UPCs pretty much did their job. No computers were damaged -- just a dead scanner, a zapped paper shredder, fried cordless phone, and, most frustrating of all, an ex-coffee maker.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090805.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gj8oZ0wMAGg:94iL4WdpHDU: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=Gj8oZ0wMAGg:94iL4WdpHDU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gj8oZ0wMAGg:94iL4WdpHDU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gj8oZ0wMAGg:94iL4WdpHDU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gj8oZ0wMAGg:94iL4WdpHDU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gj8oZ0wMAGg:94iL4WdpHDU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gj8oZ0wMAGg:94iL4WdpHDU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Gj8oZ0wMAGg" height="1" width="1"/&gt;</description>
	<pubDate>5 Aug 2009 14:40:12 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Gj8oZ0wMAGg/ea090805.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090805.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090805.html</feedburner:origLink></item>
	<item>
	<title>Understanding the Trend Toward BPM and SOA Convergence in Cultural Terms</title>
	<description>Allen, Paul | E-Mail Advisors | 30 July 2009 | Business Technology Trends &amp;amp; Impacts; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;We read much these days about business process management (BPM) and service-oriented architecture (SOA) converging. Is that just hype, or does it really make sense? And if it does make sense, just what might that mean for our organization -- not just in terms of technology, but also in terms of that subtler, softer kind of thing we call "culture" -- the unwritten rules of the game?&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090730.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IJ8dHHnlhdg:Q92eQPbjiKs: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=IJ8dHHnlhdg:Q92eQPbjiKs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IJ8dHHnlhdg:Q92eQPbjiKs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IJ8dHHnlhdg:Q92eQPbjiKs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IJ8dHHnlhdg:Q92eQPbjiKs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IJ8dHHnlhdg:Q92eQPbjiKs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IJ8dHHnlhdg:Q92eQPbjiKs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/IJ8dHHnlhdg" height="1" width="1"/&gt;</description>
	<pubDate>30 Jul 2009 16:43:03 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/IJ8dHHnlhdg/btt090730.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090730.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2009/btt090730.html</feedburner:origLink></item>
	<item>
	<title>Avoid the Static: Think of Nodes, Not Cells</title>
	<description>Orr, Ken | E-Mail Advisors | 29 July 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;I was startled a few weeks ago while talking to someone about enterprise architecture, when a question about data architecture came up. One of the EA folks in the group said, "3,3" -- as if that was the conclusive answer to a question, and a number of people nodded knowingly.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090729.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nyefAKwXCA4:jNmlPZAVg4A: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=nyefAKwXCA4:jNmlPZAVg4A:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nyefAKwXCA4:jNmlPZAVg4A:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nyefAKwXCA4:jNmlPZAVg4A:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nyefAKwXCA4:jNmlPZAVg4A:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nyefAKwXCA4:jNmlPZAVg4A:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nyefAKwXCA4:jNmlPZAVg4A:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nyefAKwXCA4" height="1" width="1"/&gt;</description>
	<pubDate>29 Jul 2009 16:40:12 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nyefAKwXCA4/ea090729.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090729.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090729.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Mashups in the IT Environment</title>
	<description>Dooley, Brian J. | Executive Updates | 28 July 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Mashups are lightweight integrations of one or more Web applications used to create a synergistic result, with the outcome often delivered through the Web. Although use of data from Web sources has been going on for some time, mashups represent a new level of functionality characterized by ease of use, programmatic access to data (e.g., through APIs), combination of data from multiple sources, and sharing of results. Many of the earliest mashups involved charting data -- including apartment advertisements, real estate, and even Flickr photos -- to Google Maps. Since about the year 2000, the possibilities have been growing steadily, in presentation-oriented and data aggregation applications, as well as in more sophisticated process-oriented applications. The use of mashups has since grown quickly within the consumer sector, and it is now heading into the enterprise space.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0914.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3pdiLziSr_A:NUQzkhu41To: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=3pdiLziSr_A:NUQzkhu41To:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3pdiLziSr_A:NUQzkhu41To:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3pdiLziSr_A:NUQzkhu41To:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3pdiLziSr_A:NUQzkhu41To:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3pdiLziSr_A:NUQzkhu41To:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3pdiLziSr_A:NUQzkhu41To:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3pdiLziSr_A" height="1" width="1"/&gt;</description>
	<pubDate>28 Jul 2009 16:34:54 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3pdiLziSr_A/eau0914.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0914.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0914.html</feedburner:origLink></item>
	<item>
	<title>What Does It Mean to Be Green?</title>
	<description>Rosen, Mike | E-Mail Advisors | 22 July 2009 | Enterprise Architecture; Business-IT Strategies; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;What do we mean by green computing or sustainability? Does it mean a focus on energy efficiency in the data center through less heat-producing and lower power-consumption server blades? Is it virtualization and shifting computing into the cloud to reduce carbon footprint or reducing paper consumption through new paperless processes? What about recycling and reduction in the manufacturing process? Or is it all of the above? Your guess is probably as good as mine.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090722.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QVVeS6PEKcc:yHp1oaRR324: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=QVVeS6PEKcc:yHp1oaRR324:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QVVeS6PEKcc:yHp1oaRR324:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QVVeS6PEKcc:yHp1oaRR324:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QVVeS6PEKcc:yHp1oaRR324:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QVVeS6PEKcc:yHp1oaRR324:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QVVeS6PEKcc:yHp1oaRR324:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/QVVeS6PEKcc" height="1" width="1"/&gt;</description>
	<pubDate>22 Jul 2009 16:26:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/QVVeS6PEKcc/ea090722.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090722.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090722.html</feedburner:origLink></item>
	<item>
	<title>EA Meets SOA in a Challenged Global Economy</title>
	<description>Allen, Paul | Executive Reports | 01 June 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Many approaches to enterprise architecture (EA) are based upon ideas that are rooted in the 1970-1980s world of internal IT shops, which puts the focus on the framework as an instrument for keeping internal IT assets in order. These approaches tend to neglect both the "soft" people-related factors that are central to successful EA and the fact that business is increasingly conducted in a collaborative fashion, using distributed Internet technologies. In this Executive Report by Paul Allen, we provide guidance that addresses the needs of organizations operating in a continually challenged global economy by harnessing ideas from service-oriented architecture (SOA) in an EA context.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/reports/2009/06/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qslGISYBzqA:KYJYYBt2lko: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=qslGISYBzqA:KYJYYBt2lko:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qslGISYBzqA:KYJYYBt2lko:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qslGISYBzqA:KYJYYBt2lko:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qslGISYBzqA:KYJYYBt2lko:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qslGISYBzqA:KYJYYBt2lko:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qslGISYBzqA:KYJYYBt2lko:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/qslGISYBzqA" height="1" width="1"/&gt;</description>
	<pubDate>1 Jun 2009 14:32:24 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/qslGISYBzqA/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2009/06/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2009/06/index.html</feedburner:origLink></item>
	<item>
	<title>A Forensic Approach to Information Systems Development: Part I -- Describing the Problem</title>
	<description>Bailey, Ian | Executive Updates | 17 July 2009 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;The gap between what the business requires and what IT delivers is well recognized. The premise of this two-part Executive Update series is that although approaches such as enterprise architecture go some way toward closing this gap, a fundamental problem remains with the way systems are specified and delivered. That problem lies in the information analysis and modeling that takes place early in the development of systems. The process of information modeling is opaque to most end users, and most IT professionals consider it a "black art." As a result, it gets little scrutiny, and only the data modeler can have any kind of certainty that the model accurately reflects business requirements.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0913.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9oKEQvujF6I:S0UV1zhmqL0: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=9oKEQvujF6I:S0UV1zhmqL0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9oKEQvujF6I:S0UV1zhmqL0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9oKEQvujF6I:S0UV1zhmqL0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9oKEQvujF6I:S0UV1zhmqL0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9oKEQvujF6I:S0UV1zhmqL0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9oKEQvujF6I:S0UV1zhmqL0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9oKEQvujF6I" height="1" width="1"/&gt;</description>
	<pubDate>17 Jul 2009 14:28:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9oKEQvujF6I/eau0913.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0913.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2009/eau0913.html</feedburner:origLink></item>
	<item>
	<title>Agile and SOA -- Two Dimensions of a Corporate IT Strategy</title>
	<description>Coldewey, Jens | E-Mail Advisors | 16 July 2009 | Agile Project Management; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In his recent Advisor "Achieving Agile Software: Fail to Scale -- Prepare to Fail" (25 June 2009), Cutter Senior Consultant Paul Allen had raised the issue of the connection between agile and SOA. In conclusion, Paul states, "What I am suggesting is that SOA has a key role in coming to [agile addressing its shortcomings on large projects], and conversely that agile has a key role in improving SOA-related work." I tend to agree with Paul, but would like to add a slightly different perspective on the connection between SOA and agile.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/project/fulltext/advisor/2009/apm090716.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0qnd9arHax4:mM64NtFFNjw: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=0qnd9arHax4:mM64NtFFNjw:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0qnd9arHax4:mM64NtFFNjw:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0qnd9arHax4:mM64NtFFNjw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0qnd9arHax4:mM64NtFFNjw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0qnd9arHax4:mM64NtFFNjw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0qnd9arHax4:mM64NtFFNjw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0qnd9arHax4" height="1" width="1"/&gt;</description>
	<pubDate>16 Jul 2009 14:27:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0qnd9arHax4/apm090716.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2009/apm090716.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2009/apm090716.html</feedburner:origLink></item>
	<item>
	<title>If You Have to Justify IT ... Look Carefully</title>
	<description>Rosen, Mike | E-Mail Advisors | 15 July 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Like you, I try to keep up with what's going on in the industry by reading magazines, articles, and so on. Perhaps it's the economy, or just coincidence, but in the past few months, there seem to have been more than enough articles about the impotence of IT.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090715.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0VdPrVCqq3A:hMSW3I-pSB0: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=0VdPrVCqq3A:hMSW3I-pSB0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0VdPrVCqq3A:hMSW3I-pSB0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0VdPrVCqq3A:hMSW3I-pSB0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0VdPrVCqq3A:hMSW3I-pSB0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0VdPrVCqq3A:hMSW3I-pSB0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0VdPrVCqq3A:hMSW3I-pSB0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0VdPrVCqq3A" height="1" width="1"/&gt;</description>
	<pubDate>15 Jul 2009 14:19:01 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0VdPrVCqq3A/ea090715.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090715.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090715.html</feedburner:origLink></item>
	<item>
	<title>New Additions</title>
	<description>&lt;UL&gt;
&lt;LI&gt;&lt;A title=http://www.cutter.com/trends/fulltext/updates/2009/bttu0906.html href="http://www.cutter.com/trends/fulltext/updates/2009/bttu0906.html"&gt;"The Web as Platform": What Does It Mean? -- Part III&lt;/A&gt; by Joseph Feller 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2009/03/itj0903b.html href="http://www.cutter.com/itjournal/fulltext/2009/03/itj0903b.html"&gt;Metrics Show Architectural Impact on IT&lt;/A&gt; by Michael Rosen 
&lt;LI&gt;&lt;A title=http://www.cutter.com/trends/fulltext/reports/2009/03/index.html href="http://www.cutter.com/trends/fulltext/reports/2009/03/index.html"&gt;Potemkin Architecture&lt;/A&gt; by Lou Mazzucchelli and the Cutter Business Technology Council 
&lt;LI&gt;&lt;A title=http://www.cutter.com/risk/fulltext/reports/2009/02/index.html href="http://www.cutter.com/risk/fulltext/reports/2009/02/index.html"&gt;An Integrated Approach to SOA Governance&lt;/A&gt; by Paul Allen 
&lt;LI&gt;&lt;A title=http://www.cutter.com/alignment/fulltext/reports/2009/05/index.html href="http://www.cutter.com/alignment/fulltext/reports/2009/05/index.html"&gt;Frames: How to Treat Software Components as Capital Assets -- and Why You Should&lt;/A&gt; by Paul G. Bassett&lt;/LI&gt;
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/index.html href="http://www.cutter.com/itjournal/fulltext/2008/12/index.html"&gt;Negotiating the Path to Business Architecture/IT Architecture Alignment&lt;/A&gt; by William M. Ulrich 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912a.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912a.html"&gt;Finding -- and Filling -- the Real Business Gap&lt;/A&gt; by Greg Suddreth and Whynde Melaragno 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912b.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912b.html"&gt;Seven Rules of Business Alignment&lt;/A&gt; by Alan Inglis 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912c.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912c.html"&gt;Vision and Values: A Model for Business/IT Architecture Alignment&lt;/A&gt; by J.M. Sampath 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912d.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912d.html"&gt;Aligning Business and IT Architectures: A Seven-Step Approach&lt;/A&gt; by Tushar K. Hazra 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912e.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912e.html"&gt;The Role of the Value Flow in Business-IT Alignment&lt;/A&gt; by Neal McWhorter 
&lt;LI&gt;&lt;A title=http://www.cutter.com/itjournal/fulltext/2008/12/itj0912f.html href="http://www.cutter.com/itjournal/fulltext/2008/12/itj0912f.html"&gt;A Requirements Approach to Enterprise Technology Architecture&lt;/A&gt; by Dan Berglove and Jeroen van Tyn&lt;/LI&gt;&lt;/UL&gt;http://www.cutter.com/architecture.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:WcCXxcXBLWU: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=vOA-u4rXe0w:WcCXxcXBLWU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:WcCXxcXBLWU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:WcCXxcXBLWU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:WcCXxcXBLWU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vOA-u4rXe0w:WcCXxcXBLWU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vOA-u4rXe0w:WcCXxcXBLWU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/vOA-u4rXe0w" height="1" width="1"/&gt;</description>
	<pubDate>21 Jul 2009 14:40:49 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/vOA-u4rXe0w/architecture.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture.html</feedburner:origLink></item>
	<item>
	<title>Key Steps to Ensuring Successful EA</title>
	<description>Berglove, Dan; van Tyn, Jeroen | E-Mail Advisors | 08 July 2009 | Enterprise Architecture&lt;BR&gt;&lt;BR&gt;Recently, we've written about some core strategies that help ensure the success of enterprise architecture, such as developing key EA capabilities (see "Six Key Capabilities on Road to EA Success," 18 March 2009) and employing an iterative and incremental approach to EA programs (see "Take Iterative Steps: Start Small, Empower Team Via Vision, Value," 29 April 2009). In this Advisor, we provide an overview of several other pervasive themes that provide broad but powerful guidance to EA efforts.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090708.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=tPw_00cjU2k:Fun5U-Z0HVo: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=tPw_00cjU2k:Fun5U-Z0HVo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=tPw_00cjU2k:Fun5U-Z0HVo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=tPw_00cjU2k:Fun5U-Z0HVo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=tPw_00cjU2k:Fun5U-Z0HVo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=tPw_00cjU2k:Fun5U-Z0HVo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=tPw_00cjU2k:Fun5U-Z0HVo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/tPw_00cjU2k" height="1" width="1"/&gt;</description>
	<pubDate>8 Jul 2009 14:09:38 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/tPw_00cjU2k/ea090708.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090708.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2009/ea090708.html</feedburner:origLink></item>
	<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>
	</channel></rss>
