<?xml version="1.0" encoding="windows-1252"?>
<?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>9 Jan 2012 17:09:55 GMT</pubDate>
	<title>Cutter Consortium: Enterprise Suite</title>
	<description>Welcome to your research. Get immediate electronic access to best practices and practical lessons from over a hundred of the world's IT experts, leading consultants who are formulating and implementing leading-edge practices in the real world.</description>
	<link>http://www.cutter.com/welcome.html</link>
	<language>en</language>
	<skipDays><day>Sunday</day></skipDays>
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CutterConsortiumEnterpriseArchitecture" /><feedburner:info uri="cutterconsortiumenterprisearchitecture" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><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><item>
	<title>Webinar: Risk and Risk Language</title>
	<description>Pritchard, Carl | Events | 
&lt;br/&gt;&lt;br/&gt;
Cutter Senior Consultant Carl Pritchard will take participants on a dynamic excursion through the language of risk, demystifying the practice. Participants will learn the four simple ways to improve their risk management practice without changing the way the organization does business.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-language.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DsbIOHs-Ch8:XPFKCmuW1RQ: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=DsbIOHs-Ch8:XPFKCmuW1RQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DsbIOHs-Ch8:XPFKCmuW1RQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DsbIOHs-Ch8:XPFKCmuW1RQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DsbIOHs-Ch8:XPFKCmuW1RQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=DsbIOHs-Ch8:XPFKCmuW1RQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=DsbIOHs-Ch8:XPFKCmuW1RQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/DsbIOHs-Ch8" height="1" width="1"/&gt;</description>
	<pubDate>27 Jun 2012 17:13:51 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/DsbIOHs-Ch8/risk-language.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-language.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-language.html</feedburner:origLink></item>
	<item>
	<title>Webinar: EA Programs that Work</title>
	<description>Rosen, Mike | Events | 
&lt;br/&gt;&lt;br/&gt;
Architecture programs make it possible for enterprises to be flexible and agile; that is, to be truly competitive. Whether your organization is just getting started with Enterprise or Business Architecture, or you have an established program, during this webinar, Senior Consultant Mike Rosen will help you envision the best ways to organize the architecture function in your organization so that it can deliver maximum value.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/ea-programs-that-work.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hmI4ombYbaM:k7Bw-VAvpR0: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=hmI4ombYbaM:k7Bw-VAvpR0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hmI4ombYbaM:k7Bw-VAvpR0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hmI4ombYbaM:k7Bw-VAvpR0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hmI4ombYbaM:k7Bw-VAvpR0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hmI4ombYbaM:k7Bw-VAvpR0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hmI4ombYbaM:k7Bw-VAvpR0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/hmI4ombYbaM" height="1" width="1"/&gt;</description>
	<pubDate>13 Jun 2012 17:12:09 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/hmI4ombYbaM/ea-programs-that-work.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/ea-programs-that-work.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/ea-programs-that-work.html</feedburner:origLink></item>
	<item>
	<title>Improve Your Architectural Skills with Critical Thinking</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
One of the most important skills of an architect (be it a business architect, IT architect, or enterprise architect) is that of &amp;ldquo;critical thinking.” It has been defined by the National Council for Excellence in Critical Thinking as: "the intellectually disciplined process of actively and skillfully conceptualizing, applying, analyzing, synthesizing, and/or evaluating information gathered from, or generated by, observation, experience, reflection, reasoning, or communication, as a guide to belief and action."
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120411.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qCm_xeQ1gLk:ReY4Z5MnYr4: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=qCm_xeQ1gLk:ReY4Z5MnYr4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qCm_xeQ1gLk:ReY4Z5MnYr4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qCm_xeQ1gLk:ReY4Z5MnYr4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qCm_xeQ1gLk:ReY4Z5MnYr4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qCm_xeQ1gLk:ReY4Z5MnYr4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qCm_xeQ1gLk:ReY4Z5MnYr4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/qCm_xeQ1gLk" height="1" width="1"/&gt;</description>
	<pubDate>11 Apr 2012 16:54:38 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/qCm_xeQ1gLk/ea120411.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120411.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120411.html</feedburner:origLink></item>
	<item>
	<title>Press Release: Stat of the Week -- When your organization develops smartphone apps, how is development done?</title>
	<description>Cutter Consortium | 
&lt;br/&gt;&lt;br/&gt;
The data from our smartphone data research suggest that that IT organizations are poised to play a leading role in implementing an effective mobile strategy, according to author Maria Lee. She goes on to assert that IT groups enabling a mobile strategy should consider applying the following four lessons learned.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/press/120410.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bkHg4y0pc90:28KFtaFQs20: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=bkHg4y0pc90:28KFtaFQs20:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bkHg4y0pc90:28KFtaFQs20:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bkHg4y0pc90:28KFtaFQs20:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bkHg4y0pc90:28KFtaFQs20:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=bkHg4y0pc90:28KFtaFQs20:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=bkHg4y0pc90:28KFtaFQs20:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/bkHg4y0pc90" height="1" width="1"/&gt;</description>
	<pubDate>10 Apr 2012 16:46:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/bkHg4y0pc90/120410.html</link>
	<guid isPermaLink="false">http://www.cutter.com/press/120410.html</guid>
	<feedburner:origLink>http://www.cutter.com/press/120410.html</feedburner:origLink></item>
	<item>
	<title>(Finding) Genuine Sponsors: Processes Are Not Their Problem</title>
	<description>Glazer, Hillel | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Common wisdom in process improvement efforts includes the notion of a "sponsor." The sponsor is a person (sometimes a small group of people) within an organization who buys into -- often literally as much as figuratively -- the improvement effort. This "buying into" essentially allows the improvements to happen. It is said, and widely believed, that having a properly positioned sponsor (i.e., "sponsorship") within the organization is the single most critical enabler of an improvement effort. This is actually true. But, as I'll explain, it's much easier said than done and, what's more, it's a slightly incomplete belief. The sponsor needs to be more than properly positioned; the sponsor must be effectively engaged. A well-positioned but not engaged sponsor is as good as no sponsor. It often feels, to improvement experts, that this is the norm. A truly engaged sponsor is surprisingly rare.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/project/fulltext/advisor/2012/apm120405.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Kf-VYSAsSp4:7uqAAt7vXDk: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=Kf-VYSAsSp4:7uqAAt7vXDk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Kf-VYSAsSp4:7uqAAt7vXDk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Kf-VYSAsSp4:7uqAAt7vXDk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Kf-VYSAsSp4:7uqAAt7vXDk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Kf-VYSAsSp4:7uqAAt7vXDk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Kf-VYSAsSp4:7uqAAt7vXDk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Kf-VYSAsSp4" height="1" width="1"/&gt;</description>
	<pubDate>5 Apr 2012 16:28:38 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Kf-VYSAsSp4/apm120405.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2012/apm120405.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2012/apm120405.html</feedburner:origLink></item>
	<item>
	<title>Inflection Points for Decisions and Profit, Part II</title>
	<description>Charette, Robert N. | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my previous Advisor ("Inflection Points for Decisions and Profit, Part I"), I pointed out that all exchanges of goods and services are exchanges of risk and opportunity between the parties of the exchange, and that profit is the payment a supplier of a good or service receives for taking away its customers’ risks or problems (or, viewed another way, creating an opportunity for the customer). In this Advisor, I wish to explore the linkage between decisions and profit, and the possibility that we are at the inflection point of a new industry that may potentially and profoundly disrupt both our corporate and our personal lives. Two recent events serve to make the point.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120405.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c0zWFdn2O3U:b3dB4CoMuqo: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=c0zWFdn2O3U:b3dB4CoMuqo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c0zWFdn2O3U:b3dB4CoMuqo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c0zWFdn2O3U:b3dB4CoMuqo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c0zWFdn2O3U:b3dB4CoMuqo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c0zWFdn2O3U:b3dB4CoMuqo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c0zWFdn2O3U:b3dB4CoMuqo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/c0zWFdn2O3U" height="1" width="1"/&gt;</description>
	<pubDate>5 Apr 2012 16:23:58 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/c0zWFdn2O3U/bit120405.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120405.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120405.html</feedburner:origLink></item>
	<item>
	<title>The Value Proposition</title>
	<description>Hazra, Tushar; Kumar, Sanjiv | E-Mail Advisors |
&lt;br/&gt;&lt;br/&gt;
As business architecture becomes more mainstream, many large and complex enterprises across the private and public sectors are embracing its primary concepts. For most of these organizations, BA plays a significant role in defining the primary value proposition for the enterprise architecture. As such, a BA practice instills the foundation for building a mature and robust enterprise, since it constitutes a set of processes, principles, and expertise at the enterprise level. Collectively, the processes and principles pave the way for creating a comprehensive, business-centric blueprint or "big picture" model of the enterprise. In this Advisor, we focus on various aspects of these processes and principles -- and the steps to build them. However, we are not undermining the role business architects and other associates involved with the BA practice play (see Table 1 for a representative profile of a business architect). On the contrary, they are responsible for leveraging the processes and principles effectively to develop and establish a business-centric blueprint of the business architecture as a practice.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120404.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=khwhRj0ErI8:VdIh0srHBOM: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=khwhRj0ErI8:VdIh0srHBOM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=khwhRj0ErI8:VdIh0srHBOM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=khwhRj0ErI8:VdIh0srHBOM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=khwhRj0ErI8:VdIh0srHBOM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=khwhRj0ErI8:VdIh0srHBOM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=khwhRj0ErI8:VdIh0srHBOM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/khwhRj0ErI8" height="1" width="1"/&gt;</description>
	<pubDate>4 Apr 2012 15:24:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/khwhRj0ErI8/ea120404.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120404.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120404.html</feedburner:origLink></item>
	<item>
	<title>Product Vision: The First Agile Planning Activity for Large-Scale Software Delivery</title>
	<description>Smits, Hubert | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
As every golfer knows, getting on the golf course early on Saturday morning doesn't improve your golf game by itself. Improving your game is about thinking ahead, having an idea about what will reduce your handicap the most, and, after determining that it's your swing, working alone and with your trainer to improve your swing. You practice that swing, play a game, and you soon learn that the swing isn't the whole problem; a better grip would lower your handicap even more. So you change your training plan without losing sight of the goal: a handicap below four in the next 12 months.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/project/fulltext/advisor/2012/apm120329.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CRd7D7yInyk:wB-TuiNV1Zg: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=CRd7D7yInyk:wB-TuiNV1Zg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CRd7D7yInyk:wB-TuiNV1Zg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CRd7D7yInyk:wB-TuiNV1Zg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CRd7D7yInyk:wB-TuiNV1Zg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CRd7D7yInyk:wB-TuiNV1Zg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CRd7D7yInyk:wB-TuiNV1Zg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/CRd7D7yInyk" height="1" width="1"/&gt;</description>
	<pubDate>29 Mar 2012 15:05:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/CRd7D7yInyk/apm120329.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2012/apm120329.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2012/apm120329.html</feedburner:origLink></item>
	<item>
	<title>Putting Enterprise Architecture and Portfolio Management Together, Part II</title>
	<description>Benson, Bob | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my previous Advisor we described enterprise architecture (EA) and portfolio management (PM) ("Putting Enterprise Architecture and Portfolio Management Together, Part I"). We concluded by saying that the challenge is how to put these two together, and that there's always been a tendency for practitioners, depending on their orientation, to separate enterprise architecture and business-driven strategic IT planning exercises. While EA has recently strongly moved into the business domain (e.g., business architecture, business capability), EA-driven planning efforts still tend to be technology focused. At the same time, business-based practitioners tend to look at the strategic business requirements represented by business strategy, and establish investment requirements, initiatives, and programs without considering the architecture aspects.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120329.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZzpLx9nypIc:1P3QRN94j4Q: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=ZzpLx9nypIc:1P3QRN94j4Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZzpLx9nypIc:1P3QRN94j4Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZzpLx9nypIc:1P3QRN94j4Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZzpLx9nypIc:1P3QRN94j4Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZzpLx9nypIc:1P3QRN94j4Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZzpLx9nypIc:1P3QRN94j4Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ZzpLx9nypIc" height="1" width="1"/&gt;</description>
	<pubDate>29 Mar 2012 15:02:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ZzpLx9nypIc/bit120329.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120329.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120329.html</feedburner:origLink></item>
	<item>
	<title>Use Architecture to Support Portfolio Management</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
As an architect, I find that what architects do is not well understood, and we are frequently challenged to justify the value that we add to the enterprise. So I am always looking for opportunities to add value. One such opportunity exists when we apply architecture to help with portfolio management. Cutter Fellow Bob Benson recently wrote an Advisor on this topic ("Putting Enterprise Architecture and Portfolio Management Together, Part I") as a result of a joint workshop that he and I gave at the Cutter Business &amp; Enterprise Architecture Summit 2012. This Advisor provides a complementary, architectural perspective to his series of Advisors.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120328.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rwNw9ltGqvg:sn2N4EdWH4U: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=rwNw9ltGqvg:sn2N4EdWH4U:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rwNw9ltGqvg:sn2N4EdWH4U:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rwNw9ltGqvg:sn2N4EdWH4U:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rwNw9ltGqvg:sn2N4EdWH4U:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rwNw9ltGqvg:sn2N4EdWH4U:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rwNw9ltGqvg:sn2N4EdWH4U:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/rwNw9ltGqvg" height="1" width="1"/&gt;</description>
	<pubDate>28 Mar 2012 19:46:23 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/rwNw9ltGqvg/ea120328.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120328.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120328.html</feedburner:origLink></item>
	<item>
	<title>Putting Enterprise Architecture and Portfolio Management Together, Part I</title>
	<description>Benson, Bob | E-Mail Advisors |
&lt;br/&gt;&lt;br/&gt;
Cutter Business &amp; Enterprise Architecture Practice Director Mike Rosen and I recently presented a one-day workshop on enterprise architecture (EA) and portfolio management (PM), and how they work together. Part of Mike's contribution was about technical debt and how it fits into both EA and PM. Planning the workshop created a new awareness of how important both EA and PM are and how, together, they can produce superior insight into delivering value to business and government organizations.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120322.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Usj1sm0JDs0:twpp-m_fzOY: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=Usj1sm0JDs0:twpp-m_fzOY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Usj1sm0JDs0:twpp-m_fzOY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Usj1sm0JDs0:twpp-m_fzOY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Usj1sm0JDs0:twpp-m_fzOY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Usj1sm0JDs0:twpp-m_fzOY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Usj1sm0JDs0:twpp-m_fzOY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Usj1sm0JDs0" height="1" width="1"/&gt;</description>
	<pubDate>22 Mar 2012 19:31:48 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Usj1sm0JDs0/bit120322.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120322.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2012/bit120322.html</feedburner:origLink></item>
	<item>
	<title>Tablets for the Enterprise</title>
	<description>Hall, Curt | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Selecting tablets for enterprise computing currently comes down to three choices: the Apple iPad, Android-based devices from various vendors, and Research In Motion's BlackBerry Playbook. Many would argue that the first two are the only real choices, given that they currently make up the bulk of tablet purchases by end-user organizations -- with the Apple iPad overwhelmingly owning the lion's share of the market. However, sometime this fall, you can expect to start seeing tablets appear running Windows 8 OS. Lately, I've been researching the application of tablets and their role in enterprise computing. Here's where I see the current crop standing in this regard.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120321.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fNtAKS1wD0w:RBvlrPXJUg8: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=fNtAKS1wD0w:RBvlrPXJUg8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fNtAKS1wD0w:RBvlrPXJUg8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fNtAKS1wD0w:RBvlrPXJUg8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fNtAKS1wD0w:RBvlrPXJUg8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fNtAKS1wD0w:RBvlrPXJUg8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fNtAKS1wD0w:RBvlrPXJUg8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/fNtAKS1wD0w" height="1" width="1"/&gt;</description>
	<pubDate>21 Mar 2012 19:18:59 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/fNtAKS1wD0w/ea120321.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120321.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120321.html</feedburner:origLink></item>
	<item>
	<title>Mind the Gap: Avoiding the Abyss Between Leadership and Management</title>
	<description>Charette, Robert N.; Gentry, Kerry F. | Journals | 
&lt;br/&gt;&lt;br/&gt;
Cutter Fellow Robert Charette and coauthor Kerry Gentry take on the differences between management and leadership and tell us some depressing tales of modern leadership failures in business and government. They assert that the failures signal a dearth of leadership and an excess of management. In the end they provide us with a useful model -- the Leadership Wheel -- for assessing leadership traits and emphatically argue that leadership is a science!
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2012/03/itj1203b.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NYZ_DOXpsbo:NuF35zxmis8: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=NYZ_DOXpsbo:NuF35zxmis8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NYZ_DOXpsbo:NuF35zxmis8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NYZ_DOXpsbo:NuF35zxmis8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NYZ_DOXpsbo:NuF35zxmis8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NYZ_DOXpsbo:NuF35zxmis8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NYZ_DOXpsbo:NuF35zxmis8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/NYZ_DOXpsbo" height="1" width="1"/&gt;</description>
	<pubDate>20 Mar 2012 18:54:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/NYZ_DOXpsbo/itj1203b.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2012/03/itj1203b.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2012/03/itj1203b.html</feedburner:origLink></item>
	<item>
	<title>Evaluating the BPM Hype Cycle</title>
	<description>Teti, Frank | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
With "galactic computing" still off in the distance, there continues to be a significant amount of hype regarding business process management (BPM) and service-oriented architecture (SOA). While these things are not necessarily orthogonal, they are not inextricably, interrelated technologies as some analysts would have you believe. Nevertheless, in the seemingly inexorable world of the technology business, we often witness writers, analysts, and marketers perpetually create demand for new products and services by embellishing the synergies and underlying dependencies, either real or imaginary, in an effort to educate, sell, and promote the general welfare, so to speak.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1203.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=N5xlK4CosD0:QmwvTgvG_1M: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=N5xlK4CosD0:QmwvTgvG_1M:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=N5xlK4CosD0:QmwvTgvG_1M:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=N5xlK4CosD0:QmwvTgvG_1M:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=N5xlK4CosD0:QmwvTgvG_1M:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=N5xlK4CosD0:QmwvTgvG_1M:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=N5xlK4CosD0:QmwvTgvG_1M:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/N5xlK4CosD0" height="1" width="1"/&gt;</description>
	<pubDate>14 Mar 2012 15:10:50 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/N5xlK4CosD0/eau1203.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1203.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1203.html</feedburner:origLink></item>
	<item>
	<title>Put Big Data in Perspective -- Part II</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my last Advisor ("Put Big Data in Perspective -- Part I"), I discussed the basics of Big Data, what it is, where it comes from, what's it good for, and so on. In this Advisor, I want to put Big Data into the perspective of enterprise information architecture.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120314.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zn4EGP6iZDA:DhmaJSKq_qg: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=zn4EGP6iZDA:DhmaJSKq_qg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zn4EGP6iZDA:DhmaJSKq_qg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zn4EGP6iZDA:DhmaJSKq_qg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zn4EGP6iZDA:DhmaJSKq_qg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zn4EGP6iZDA:DhmaJSKq_qg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zn4EGP6iZDA:DhmaJSKq_qg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/zn4EGP6iZDA" height="1" width="1"/&gt;</description>
	<pubDate>14 Mar 2012 15:01:06 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/zn4EGP6iZDA/ea120314.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120314.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120314.html</feedburner:origLink></item>
	<item>
	<title>Capabilities, Functions, Value Chains, and Big Business Processes</title>
	<description>Orr, Ken | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
There is a lot of discussion these days about business capabilities and their role in business architecture. While any discussion of "what business(es) our business is in" is worthwhile, it is perhaps useful to step back in time and consider an analysis technique that resembles capability modeling (CM): functional decomposition (FD). Back in the 1970s and 1980s, FD, which was part of some form of "structured analysis," was all the vogue. One of the advantages of FD then, like CM now, was that it mirrored the organization chart. Functions like capabilities fit in nicely to the way businesses structured themselves. Moreover, FD (again, like CM) fit a hierarchical analysis model, which is easy to fit into modern automated tools.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120307.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lSk2GJfocb4:UHF0nZXL94g: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=lSk2GJfocb4:UHF0nZXL94g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lSk2GJfocb4:UHF0nZXL94g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lSk2GJfocb4:UHF0nZXL94g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lSk2GJfocb4:UHF0nZXL94g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lSk2GJfocb4:UHF0nZXL94g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lSk2GJfocb4:UHF0nZXL94g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/lSk2GJfocb4" height="1" width="1"/&gt;</description>
	<pubDate>7 Mar 2012 14:38:05 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/lSk2GJfocb4/ea120307.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120307.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120307.html</feedburner:origLink></item>
	<item>
	<title>Using Cloud to Rethink the Enterprise IT Portfolio</title>
	<description>Cohen, Beth | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
No matter how disciplined a company is about its IT governance, the average enterprise has many years of legacy applications in its portfolio that need to be rationalized. Over time, even the best-run company will acquire what a coworker affectionately refers to as "glops and legacy linguini." We all know the recipe: start with a couple of semisuccessful enterprise application implementations (where the company is continuing to use both the old and the new systems), throw in a few mergers and acquisitions (include a handful of management regime changes and reorganizations to add spice), then stir in thousands of undocumented patches and temporary fixes that turn permanent. Bake until solidified into an impenetrable morass of siloed functions and tangled application interdependencies. These are the nightmares that keep IT executives awake at night. Enterprise clouds offer a solution that allows IT to take governance control back to where it belongs in the company without stifling business innovation or blocking the organization's ability to meet its objectives.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/advisor/2012/itj120222.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JBRrEcxn50c:3EyAHsMXm7I: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=JBRrEcxn50c:3EyAHsMXm7I:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JBRrEcxn50c:3EyAHsMXm7I:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JBRrEcxn50c:3EyAHsMXm7I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JBRrEcxn50c:3EyAHsMXm7I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JBRrEcxn50c:3EyAHsMXm7I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JBRrEcxn50c:3EyAHsMXm7I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/JBRrEcxn50c" height="1" width="1"/&gt;</description>
	<pubDate>22 Feb 2012 14:29:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/JBRrEcxn50c/itj120222.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/advisor/2012/itj120222.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/advisor/2012/itj120222.html</feedburner:origLink></item>
	<item>
	<title>Establishing the Business Architecture Practice: A Case Study -- Best Practices, Revisited</title>
	<description>Hazra, Tushar K. | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Since publication of the Cutter Business Enterprise Architecture Executive Report "Establishing the Business Architecture Practice: A Case Study" (Vol. 15, No. 1) in January, several readers have commented on the stages that Sanjiv Kumar and I presented in the Report regarding the lifecycle of the business architecture (BA) practice. Some readers have experienced similar challenges and issues in building the BA practice. However, most readers who contacted us in response to the Report asked us to elaborate on the best practices cultivated during the case study.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120222.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zvB6bcqwgq4:qVo57hhR_rE: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=zvB6bcqwgq4:qVo57hhR_rE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zvB6bcqwgq4:qVo57hhR_rE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zvB6bcqwgq4:qVo57hhR_rE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zvB6bcqwgq4:qVo57hhR_rE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zvB6bcqwgq4:qVo57hhR_rE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zvB6bcqwgq4:qVo57hhR_rE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/zvB6bcqwgq4" height="1" width="1"/&gt;</description>
	<pubDate>22 Feb 2012 14:27:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/zvB6bcqwgq4/ea120222.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120222.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120222.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture Body of Knowledge</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Readers are probably familiar with the concept of a body of knowledge (BOK). BOK (or BoK) is a term used to represent the set of concepts, terms, and activities that make up a professional domain, as defined by the relevant professional association. The BoK is more than just a document or a collection of terms in that it describes the ontology of a specific domain. Among the BoKs you may be familiar with are Software Engineering BoK (SWEBOK), Project Management BoK (PMBOK), and Data Management BoK (DMBOK).
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc: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=RtDKY22AUjE:NzVhFE6cUDc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RtDKY22AUjE" height="1" width="1"/&gt;</description>
	<pubDate>15 Feb 2012 14:11:36 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RtDKY22AUjE/ea120215.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture Body of Knowledge</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Readers are probably familiar with the concept of a body of knowledge (BOK). BOK (or BoK) is a term used to represent the set of concepts, terms, and activities that make up a professional domain, as defined by the relevant professional association. The BoK is more than just a document or a collection of terms in that it describes the ontology of a specific domain. Among the BoKs you may be familiar with are Software Engineering BoK (SWEBOK), Project Management BoK (PMBOK), and Data Management BoK (DMBOK).
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc: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=RtDKY22AUjE:NzVhFE6cUDc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RtDKY22AUjE:NzVhFE6cUDc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RtDKY22AUjE:NzVhFE6cUDc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RtDKY22AUjE" height="1" width="1"/&gt;</description>
	<pubDate>15 Feb 2012 14:11:36 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RtDKY22AUjE/ea120215.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120215.html</feedburner:origLink></item>
	<item>
	<title>Two Types of Contra Goals in Architecture</title>
	<description>Mohandoss, Ramaswami | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In technology architecture, it's easy to spot a wrong solution but almost impossible to design the perfect system. The primary reason for this ever-changing nature of the solution is its evolution toward staying relevant to the changing business use case. A seasoned architect soon realizes that a sound architecture or design is actually a zero-sum game with "contra goals": pairs of two critical design goals (or priorities), where one priority can only exist by compromising (or even eliminating) the other.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120208.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=r-kNcM5vZsM:eqoEFueHSp8: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=r-kNcM5vZsM:eqoEFueHSp8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=r-kNcM5vZsM:eqoEFueHSp8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=r-kNcM5vZsM:eqoEFueHSp8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=r-kNcM5vZsM:eqoEFueHSp8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=r-kNcM5vZsM:eqoEFueHSp8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=r-kNcM5vZsM:eqoEFueHSp8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/r-kNcM5vZsM" height="1" width="1"/&gt;</description>
	<pubDate>8 Feb 2012 13:27:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/r-kNcM5vZsM/ea120208.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120208.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120208.html</feedburner:origLink></item>
	<item>
	<title>Contra Goals in Architecture</title>
	<description>Mohandoss, Ramaswami | 
&lt;br/&gt;&lt;br/&gt;
In technology architecture, it's easy to spot a wrong solution but almost impossible to design the perfect system. The primary reason for this ever-changing nature of the solution is its evolution toward staying relevant to the changing business use case. A seasoned architect soon realizes that a sound architecture or design is actually a zero-sum game with "contra goals": pairs of two critical design goals (or priorities), where one priority can only exist by compromising (or even eliminating) the other.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1201.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9d3vBrqdWQY:738N1sQMnus: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=9d3vBrqdWQY:738N1sQMnus:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9d3vBrqdWQY:738N1sQMnus:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9d3vBrqdWQY:738N1sQMnus:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9d3vBrqdWQY:738N1sQMnus:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9d3vBrqdWQY:738N1sQMnus:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9d3vBrqdWQY:738N1sQMnus:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9d3vBrqdWQY" height="1" width="1"/&gt;</description>
	<pubDate>3 Feb 2012 15:33:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9d3vBrqdWQY/eau1201.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1201.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2012/eau1201.html</feedburner:origLink></item>
	<item>
	<title>Defining Enterprise Performance Architecture</title>
	<description>Rosen, Mike | 
&lt;br/&gt;&lt;br/&gt;
Management guru Peter Drucker is famous for saying "You can't manage what you can't measure." From a different perspective and equally guru-like, W. Edward Deming once said, "The most important things cannot be measured." Deming clarified this by explaining that "the issues that are most important, long term, cannot be measured in advance. However, they might be among the factors that an organization is measuring, just not understood as most important at the time." Perhaps many organizations fall in between, where they are neither exactly sure what the most important things are nor how to measure them. Can you answer the question, "How is my enterprises business performance measured?" or the follow-on question, "How do my IT systems contribute to business outcomes?"
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120201.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ykpCXPQ07nQ:E2nzQSp3bZE: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=ykpCXPQ07nQ:E2nzQSp3bZE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ykpCXPQ07nQ:E2nzQSp3bZE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ykpCXPQ07nQ:E2nzQSp3bZE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ykpCXPQ07nQ:E2nzQSp3bZE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ykpCXPQ07nQ:E2nzQSp3bZE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ykpCXPQ07nQ:E2nzQSp3bZE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ykpCXPQ07nQ" height="1" width="1"/&gt;</description>
	<pubDate>6 Feb 2012 15:10:00 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ykpCXPQ07nQ/ea120201.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120201.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120201.html</feedburner:origLink></item>
	<item>
	<title>Establishing the Business Architecture Practice: A Case Study</title>
	<description>Hazra, Tushar K.; Kumar, Sanjiv | 
&lt;br/&gt;&lt;br/&gt;
Business and IT professionals are rapidly embracing business architecture (BA) as a mainstream concept to recognize their needs, goals, and vision for business transformation. However, establishing a comprehensive, pragmatic BA practice is still in its primitive stage. In today's adverse economical climate, where businesses try to do more for less, understanding business architecture -- and its related challenges, risks, issues, and concerns -- can go a long way toward successfully achieving business transformation. This Executive Report presents a real-world case study to highlight the realities of establishing a BA practice. Our lessons learned and cultivated best practices will add significant value to establishing your own BA practice.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2012/01/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zN0MUvW7pV0:3amnprM7tJM: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=zN0MUvW7pV0:3amnprM7tJM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zN0MUvW7pV0:3amnprM7tJM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zN0MUvW7pV0:3amnprM7tJM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zN0MUvW7pV0:3amnprM7tJM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zN0MUvW7pV0:3amnprM7tJM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zN0MUvW7pV0:3amnprM7tJM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/zN0MUvW7pV0" height="1" width="1"/&gt;</description>
	<pubDate>26 Jan 2012 14:36:25 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/zN0MUvW7pV0/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2012/01/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2012/01/index.html</feedburner:origLink></item>
	<item>
	<title>BYOD or Enterprise-Supplied Mobile Device?</title>
	<description>Hall, Curt | 
&lt;br/&gt;&lt;br/&gt;
Mobility is one of the top priorities for organizations in 2012. When it comes to utilizing mobile devices in the enterprise, organizations basically have two options for supporting employees with smartphones and tablets. One, which is becoming increasingly popular, is the "bring your own device" (BYOD) strategy, in which employees are permitted to use their own personal devices for work. The other is for the company to supply select employees with phones or tablets. Both options have their benefits and drawbacks.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120125.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MSoSvkuZook:B3aOWTr2N9I: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=MSoSvkuZook:B3aOWTr2N9I:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MSoSvkuZook:B3aOWTr2N9I:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MSoSvkuZook:B3aOWTr2N9I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MSoSvkuZook:B3aOWTr2N9I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MSoSvkuZook:B3aOWTr2N9I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MSoSvkuZook:B3aOWTr2N9I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/MSoSvkuZook" height="1" width="1"/&gt;</description>
	<pubDate>25 Jan 2012 14:28:38 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/MSoSvkuZook/ea120125.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120125.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120125.html</feedburner:origLink></item>
	<item>
	<title>Applying Architecture to Business Intelligence</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
As architects, we are constantly challenged to provide value to the business. Much of the value we provide comes from avoiding costs and problems before they occur and is difficult to demonstrate or quantify. But architecture can also deliver value by providing a better, broader, more flexible, and extensible solution to business requirements. I always look for opportunities or projects where an architectural approach will provide a better solution and try to seize these chances when I can.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120118.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lrZ1HfBhk4M:O5XKqoFppDs: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=lrZ1HfBhk4M:O5XKqoFppDs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lrZ1HfBhk4M:O5XKqoFppDs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lrZ1HfBhk4M:O5XKqoFppDs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lrZ1HfBhk4M:O5XKqoFppDs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lrZ1HfBhk4M:O5XKqoFppDs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lrZ1HfBhk4M:O5XKqoFppDs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/lrZ1HfBhk4M" height="1" width="1"/&gt;</description>
	<pubDate>18 Jan 2012 19:35:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/lrZ1HfBhk4M/ea120118.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120118.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120118.html</feedburner:origLink></item>
	<item>
	<title>Agile EA: Governance Introduction</title>
	<description>Watson, Jim | Executive Reports | 
&lt;br/&gt;&lt;br/&gt;
This Executive Report explores processes in enterprise architecture governance to achieve improved agility using technology advancements in Maven and virtualization. The report describes approaches for enterprise situational awareness, agile systems integration, and dependency management, along with technology variants and innovation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/09/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rq_rEr7Z_3Q:aUk4InFvqk8: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=rq_rEr7Z_3Q:aUk4InFvqk8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rq_rEr7Z_3Q:aUk4InFvqk8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rq_rEr7Z_3Q:aUk4InFvqk8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rq_rEr7Z_3Q:aUk4InFvqk8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rq_rEr7Z_3Q:aUk4InFvqk8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rq_rEr7Z_3Q:aUk4InFvqk8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/rq_rEr7Z_3Q" height="1" width="1"/&gt;</description>
	<pubDate>13 Jan 2012 19:10:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/rq_rEr7Z_3Q/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/09/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/09/index.html</feedburner:origLink></item>
	<item>
	<title>Cloud Strategy: Some Good Tactics to Implement</title>
	<description>Teti, Frank | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
It appears lately that all business consulting has something to do with cloud computing. For instance, an organization I am currently working with has a mandate in place requiring all forward-engineering projects to be developed using a virtualized cloud environment. This effort is, in this organization's "corporate mind's eye," a way to prepare it to move production applications into the cloud, which is something it has not previously done. The company believes that this tactic will ensure that cloud architects are competent at administering applications hosted in the cloud, since code development within the cloud is relatively transparent from a developer's perspective.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/alignment/fulltext/updates/2012/bitu1201.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=l-M1WZAcOTs:pqB_NGyY_ag: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=l-M1WZAcOTs:pqB_NGyY_ag:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=l-M1WZAcOTs:pqB_NGyY_ag:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=l-M1WZAcOTs:pqB_NGyY_ag:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=l-M1WZAcOTs:pqB_NGyY_ag:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=l-M1WZAcOTs:pqB_NGyY_ag:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=l-M1WZAcOTs:pqB_NGyY_ag:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/l-M1WZAcOTs" height="1" width="1"/&gt;</description>
	<pubDate>11 Jan 2012 18:53:51 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/l-M1WZAcOTs/bitu1201.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/updates/2012/bitu1201.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/updates/2012/bitu1201.html</feedburner:origLink></item>
	<item>
	<title>Growing Data Phenomenon and Shrinking Response Times</title>
	<description>Hate, Sudhanshu | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Today's unprecedented growth rate of data (structured and unstructured) necessitates faster and cost-effective processing for near-real-time decision making. Over the years, many have viewed high-performance computing (HPC) as a monster too complex and too unaffordable for processing large data. However, that viewpoint is changing rapidly due to open source innovations such as Apache Hadoop, the advent of the cloud, and simple and affordable platforms like Microsoft.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120111.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_3idibXKuH0:eJ-opblZTMA: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=_3idibXKuH0:eJ-opblZTMA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_3idibXKuH0:eJ-opblZTMA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_3idibXKuH0:eJ-opblZTMA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_3idibXKuH0:eJ-opblZTMA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_3idibXKuH0:eJ-opblZTMA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_3idibXKuH0:eJ-opblZTMA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_3idibXKuH0" height="1" width="1"/&gt;</description>
	<pubDate>10 Jan 2012 18:51:27 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_3idibXKuH0/ea120111.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120111.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120111.html</feedburner:origLink></item>
	<item>
	<title>HPC Steroid for Big Data</title>
	<description>Hate, Sudhanshu | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
Today's unprecedented growth rate of data (structured and unstructured) necessitates faster and cost-effective processing for near-real-time decision making. Over the years, many have viewed high-performance computing (HPC) as a monster too complex and too unaffordable for processing large data. However, that viewpoint is changing rapidly due to open source innovations such as Apache Hadoop, the advent of the cloud, and simple and affordable platforms like Microsoft. In this Executive Update, we examine how various HPC techniques, deployment patterns, and Microsoft technologies are emerging to solve various Big Data problems.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/bia/fulltext/updates/2012/biau1201.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IH4o6J6Pogo:SMBon0cvk-4: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=IH4o6J6Pogo:SMBon0cvk-4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IH4o6J6Pogo:SMBon0cvk-4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IH4o6J6Pogo:SMBon0cvk-4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IH4o6J6Pogo:SMBon0cvk-4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IH4o6J6Pogo:SMBon0cvk-4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IH4o6J6Pogo:SMBon0cvk-4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/IH4o6J6Pogo" height="1" width="1"/&gt;</description>
	<pubDate>9 Jan 2012 18:40:42 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/IH4o6J6Pogo/biau1201.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/bia/fulltext/updates/2012/biau1201.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/bia/fulltext/updates/2012/biau1201.html</feedburner:origLink></item>
	<item>
	<title>EA New Year's Resolutions, Seventh Edition</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Welcome to the seventh-anniversary edition of my enterprise architect's New Year's resolutions. I hope it will give you food for thought and some inspiration for architectural growth in 2012.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120104.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=yf9pMVgQk2A:0ZIHEjhAmOM: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=yf9pMVgQk2A:0ZIHEjhAmOM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=yf9pMVgQk2A:0ZIHEjhAmOM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=yf9pMVgQk2A:0ZIHEjhAmOM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=yf9pMVgQk2A:0ZIHEjhAmOM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=yf9pMVgQk2A:0ZIHEjhAmOM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=yf9pMVgQk2A:0ZIHEjhAmOM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/yf9pMVgQk2A" height="1" width="1"/&gt;</description>
	<pubDate>4 Jan 2012 18:41:53 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/yf9pMVgQk2A/ea120104.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120104.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2012/ea120104.html</feedburner:origLink></item>
	<item>
	<title>Top 5 Intriguing Business &amp; Enterprise Architecture Articles for 2011</title>
	<description>Coburn, Koren | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
This week, we're taking a look back at five of the most intriguing articles published in Cutter's Business &amp; Enterprise Architecture practice over this past year. As you might imagine, it was no small task to cull the list and pare it down to just five articles. Look for these lists from each of our four practice areas for a compilation of Cutter's 20 most-intriguing articles of the year. Stay tuned for the next issue of this Advisor on 4 January.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111228.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=q1AwZmPQKMY:Rh9hh_rs10Q: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=q1AwZmPQKMY:Rh9hh_rs10Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=q1AwZmPQKMY:Rh9hh_rs10Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=q1AwZmPQKMY:Rh9hh_rs10Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=q1AwZmPQKMY:Rh9hh_rs10Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=q1AwZmPQKMY:Rh9hh_rs10Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=q1AwZmPQKMY:Rh9hh_rs10Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/q1AwZmPQKMY" height="1" width="1"/&gt;</description>
	<pubDate>28 Dec 2011 18:31:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/q1AwZmPQKMY/ea111228.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111228.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111228.html</feedburner:origLink></item>
	<item>
	<title>A Contrarian View of Scalability</title>
	<description>Gat, Israel | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In just about every due diligence engagement I carry out, the VC and I spend a lot of time on scalabity of the software architecture. The company whose software architecture we are evaluating usually has a good track record of successfully scaling up on quite a few technology and business dimensions. If we extrapolate the historical growth rate a few years into the future, the company really looks attractive. The concern, however, is that the company might run into a hard barrier for growth. In particular, getting stuck on some rigid architectural constraints is always a concern.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/project/fulltext/advisor/2011/apm111222.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YcQ8y8QYuCI:xe7LlgTMhb0: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=YcQ8y8QYuCI:xe7LlgTMhb0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YcQ8y8QYuCI:xe7LlgTMhb0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YcQ8y8QYuCI:xe7LlgTMhb0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YcQ8y8QYuCI:xe7LlgTMhb0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YcQ8y8QYuCI:xe7LlgTMhb0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YcQ8y8QYuCI:xe7LlgTMhb0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/YcQ8y8QYuCI" height="1" width="1"/&gt;</description>
	<pubDate>22 Dec 2011 18:22:27 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/YcQ8y8QYuCI/apm111222.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2011/apm111222.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2011/apm111222.html</feedburner:origLink></item>
	<item>
	<title>Unified Portfolio Management: The Basics</title>
	<description>Dooley, Brian J. | E-Mail Advisors | 
&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;
Enterprise portfolio management has been evolving for the past several years toward a unified vision that incorporates the diverse areas of portfolio concepts, bringing them together through standardized measures and techniques backed by consolidated software solutions. As with other areas in IT, the elimination of silos of information and activity yields benefits in efficiency, reduced overhead, and new synergies. For portfolios, unification also provides the capability for immediate visibility into key areas of enterprise activity.
&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111221.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=BNt_XPbvpDg:mmJZf_4ubnE: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=BNt_XPbvpDg:mmJZf_4ubnE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=BNt_XPbvpDg:mmJZf_4ubnE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=BNt_XPbvpDg:mmJZf_4ubnE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=BNt_XPbvpDg:mmJZf_4ubnE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=BNt_XPbvpDg:mmJZf_4ubnE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=BNt_XPbvpDg:mmJZf_4ubnE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/BNt_XPbvpDg" height="1" width="1"/&gt;</description>
	<pubDate>9 Jan 2012 17:12:05 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/BNt_XPbvpDg/ea111221.html</link>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111221.html</feedburner:origLink></item>
	<item>
	<title>Securing the Client Side With Digital Tokens</title>
	<description>Finetti, Mario | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
This Executive Update describes two security challenges in the design of Web applications and how they can be addressed: the client-side equipment and the network used by users to connect to the Web server.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1117.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AD6Pk18SYDw:b_aUsxO_PoE: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=AD6Pk18SYDw:b_aUsxO_PoE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AD6Pk18SYDw:b_aUsxO_PoE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AD6Pk18SYDw:b_aUsxO_PoE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AD6Pk18SYDw:b_aUsxO_PoE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AD6Pk18SYDw:b_aUsxO_PoE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AD6Pk18SYDw:b_aUsxO_PoE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/AD6Pk18SYDw" height="1" width="1"/&gt;</description>
	<pubDate>20 Dec 2011 16:25:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/AD6Pk18SYDw/eau1117.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1117.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1117.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Patterns: The Key to Effective EA Application as Transformation</title>
	<description>Evernden, Roger | Executive Summaries | 
&lt;br/&gt;&lt;br/&gt;
Enterprise architecture is more than IT. It is more than the embodiment of strategy. When it comes to understanding and managing significant enterprise change, enterprise architecture is a crucial discipline; thus, it is now vital to also regard EA as transformation. Business architecture and business capabilities help plan and decide strategic initiatives and priorities. As we'll explore in this Executive Report, embedding new or improved enterprise patterns delivers strategic outcomes by binding them to architectural change.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/summaries/2011/08/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7WgB24J6Gck:EKDXy9l2-0g: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=7WgB24J6Gck:EKDXy9l2-0g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7WgB24J6Gck:EKDXy9l2-0g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7WgB24J6Gck:EKDXy9l2-0g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7WgB24J6Gck:EKDXy9l2-0g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=7WgB24J6Gck:EKDXy9l2-0g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=7WgB24J6Gck:EKDXy9l2-0g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/7WgB24J6Gck" height="1" width="1"/&gt;</description>
	<pubDate>19 Dec 2011 15:26:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/7WgB24J6Gck/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/summaries/2011/08/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/summaries/2011/08/index.html</feedburner:origLink></item>
	<item>
	<title>Enterprise BI Architecture Groups: The Key to Effective Agile Data Warehousing Programs</title>
	<description>Hughes, Ralph | Consulting | 
&lt;br/&gt;&lt;br/&gt;
Agile data warehousing delivers powerful BI applications in the shortest time frame possible, yet coordinating multiple fast-moving BI teams demands more than simple project management. Organizations need an enterprise business intelligence architecture (EBIA) function to coordinate high-level requirements, designs, and technologies in order to avoid ruinously expensive mistakes and redundancies.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/workshops/enterprise-bi-architecture-groups.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1M6c7Lvsot8:NL2afX6Khbk: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=1M6c7Lvsot8:NL2afX6Khbk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1M6c7Lvsot8:NL2afX6Khbk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1M6c7Lvsot8:NL2afX6Khbk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1M6c7Lvsot8:NL2afX6Khbk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=1M6c7Lvsot8:NL2afX6Khbk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=1M6c7Lvsot8:NL2afX6Khbk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/1M6c7Lvsot8" height="1" width="1"/&gt;</description>
	<pubDate>15 Dec 2011 15:55:00 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/1M6c7Lvsot8/enterprise-bi-architecture-groups.html</link>
	<guid isPermaLink="false">http://www.cutter.com/workshops/enterprise-bi-architecture-groups.html</guid>
	<feedburner:origLink>http://www.cutter.com/workshops/enterprise-bi-architecture-groups.html</feedburner:origLink></item>
	<item>
	<title>10 Neuroscience Facts for Architects</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my last Advisor (see "Take a SCARF to Architecture Reviews," 30 November 2011), I wrote about the SCARF model (status, certainty, autonomy, relatedness, and fairness) and the importance of understanding it to achieve better results in architecture reviews. Based on the positive feedback I received, this week I'm going to discuss some of the other lessons from neuroscience that architects can incorporate into their interaction with others and themselves.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111214.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MFEcpLgmx9U:Yr-MlF9wD4c: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=MFEcpLgmx9U:Yr-MlF9wD4c:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MFEcpLgmx9U:Yr-MlF9wD4c:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MFEcpLgmx9U:Yr-MlF9wD4c:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MFEcpLgmx9U:Yr-MlF9wD4c:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MFEcpLgmx9U:Yr-MlF9wD4c:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MFEcpLgmx9U:Yr-MlF9wD4c:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/MFEcpLgmx9U" height="1" width="1"/&gt;</description>
	<pubDate>14 Dec 2011 15:36:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/MFEcpLgmx9U/ea111214.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111214.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111214.html</feedburner:origLink></item>
	<item>
	<title>Repurposing the Business Analysis Practice for Greater Value</title>
	<description>McWhorter, Neal | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
The business analysis profession is in the midst of change. Work is underway within organizations and associations to formalize and standardize what it means to be a business analyst (BA). The role has had a long and tortuous existence. A child of necessity, the role evolved to bridge the gap between what those responsible for operating an organization wanted to do and what those responsible for implementing technology were able to deliver. Attempts to eliminate this divide and directly marry the two groups began with COBOL (the Common Business-Oriented Language) and have continued through the creation of new abstractions such as visual development environments. However, these attempts have met with very limited success.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111207.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lIsR-sQfBTg:24qk1k0Dcs8: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=lIsR-sQfBTg:24qk1k0Dcs8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lIsR-sQfBTg:24qk1k0Dcs8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lIsR-sQfBTg:24qk1k0Dcs8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lIsR-sQfBTg:24qk1k0Dcs8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lIsR-sQfBTg:24qk1k0Dcs8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lIsR-sQfBTg:24qk1k0Dcs8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/lIsR-sQfBTg" height="1" width="1"/&gt;</description>
	<pubDate>7 Dec 2011 18:55:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/lIsR-sQfBTg/ea111207.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111207.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111207.html</feedburner:origLink></item>
	<item>
	<title>Unified Portfolio Management</title>
	<description>Dooley, Brian J. | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
Enterprise portfolio management has been evolving for the past several years toward a unified vision that incorporates the diverse areas of portfolio concepts, bringing them together through standardized measures and techniques backed by consolidated software solutions. As with other areas in IT, the elimination of silos of information and activity yields benefits in efficiency, reduced overhead, and new synergies. For portfolios, unification also provides the capability for immediate visibility into key areas of enterprise activity, which we'll explore in this Executive Update.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1116.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0mdsE-Kvmv0:Mr9ha_SwXa8: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=0mdsE-Kvmv0:Mr9ha_SwXa8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0mdsE-Kvmv0:Mr9ha_SwXa8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0mdsE-Kvmv0:Mr9ha_SwXa8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0mdsE-Kvmv0:Mr9ha_SwXa8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0mdsE-Kvmv0:Mr9ha_SwXa8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0mdsE-Kvmv0:Mr9ha_SwXa8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0mdsE-Kvmv0" height="1" width="1"/&gt;</description>
	<pubDate>6 Dec 2011 18:36:50 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0mdsE-Kvmv0/eau1116.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1116.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1116.html</feedburner:origLink></item>
	<item>
	<title>Take a SCARF to Architecture Reviews</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
I've been doing architecture for close to 20 years now and have built my practices based on what I've read, studied, and researched, and also from my experience of what works with clients. Every once in a while, some new information comes along that validates that experience, such as the excellent presentation on neuroleadership that Cutter Fellow Lynne Ellyn delivered at the Cutter Consortium CIO Forum in Mexico City a few weeks ago.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111130.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CQDrYrUDXc:9hgdS9pxRw8: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=9CQDrYrUDXc:9hgdS9pxRw8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CQDrYrUDXc:9hgdS9pxRw8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CQDrYrUDXc:9hgdS9pxRw8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CQDrYrUDXc:9hgdS9pxRw8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CQDrYrUDXc:9hgdS9pxRw8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CQDrYrUDXc:9hgdS9pxRw8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CQDrYrUDXc" height="1" width="1"/&gt;</description>
	<pubDate>30 Nov 2011 14:02:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CQDrYrUDXc/ea111130.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111130.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111130.html</feedburner:origLink></item>
	<item>
	<title>Security Is the Name of the Game When It Comes to Mobile Device Management</title>
	<description>Hall, Curt | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Mobility is now one of the top strategic priorities for organizations. In fact, supporting mobility is seen as so important that some organizations are offering employees the option of using their own personal devices. This &amp;ldquo;bring your own device” concept is seen as a way for companies to reduce costs, but the proliferation of smartphones and tablets in the enterprise means that IT needs to somehow practically manage these devices. And, when most IT people talk about &amp;ldquo;managing mobile devices,” they primarily mean ensuring that they are used correctly (i.e., according to company polices regarding data access, storage, and transmission) and do not become a &amp;ldquo;black hole” of a security threat to the company.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111123.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WMkJi42IUWA:efIoFKOPCTo: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=WMkJi42IUWA:efIoFKOPCTo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WMkJi42IUWA:efIoFKOPCTo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WMkJi42IUWA:efIoFKOPCTo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WMkJi42IUWA:efIoFKOPCTo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WMkJi42IUWA:efIoFKOPCTo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WMkJi42IUWA:efIoFKOPCTo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/WMkJi42IUWA" height="1" width="1"/&gt;</description>
	<pubDate>23 Nov 2011 15:35:08 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/WMkJi42IUWA/ea111123.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111123.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111123.html</feedburner:origLink></item>
	<item>
	<title>The Town Planners of Enterprise Innovation</title>
	<description>McClure, Dan; Villela, Carlos | Journals | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111a.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CEDX4AwsWs8:l2m8aEOhbhQ: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=CEDX4AwsWs8:l2m8aEOhbhQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CEDX4AwsWs8:l2m8aEOhbhQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CEDX4AwsWs8:l2m8aEOhbhQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CEDX4AwsWs8:l2m8aEOhbhQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=CEDX4AwsWs8:l2m8aEOhbhQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=CEDX4AwsWs8:l2m8aEOhbhQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/CEDX4AwsWs8" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 15:04:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/CEDX4AwsWs8/itj1111a.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111a.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111a.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture in Practice: Lessons from the Trenches</title>
	<description>Ulrich, William | Journals | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rebI9U6LG6w:xs6yxMvdr3g: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=rebI9U6LG6w:xs6yxMvdr3g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rebI9U6LG6w:xs6yxMvdr3g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rebI9U6LG6w:xs6yxMvdr3g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rebI9U6LG6w:xs6yxMvdr3g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rebI9U6LG6w:xs6yxMvdr3g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rebI9U6LG6w:xs6yxMvdr3g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/rebI9U6LG6w" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 15:00:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/rebI9U6LG6w/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/index.html</feedburner:origLink></item>
	<item>
	<title>Effective Customer Requirements Definition Using Business Architecture</title>
	<description>Guitarte, Andrew | Journals | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111b.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ea8NDQSSQP4:sadnXFBTqTQ: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=Ea8NDQSSQP4:sadnXFBTqTQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ea8NDQSSQP4:sadnXFBTqTQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ea8NDQSSQP4:sadnXFBTqTQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ea8NDQSSQP4:sadnXFBTqTQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ea8NDQSSQP4:sadnXFBTqTQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ea8NDQSSQP4:sadnXFBTqTQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Ea8NDQSSQP4" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 14:54:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Ea8NDQSSQP4/itj1111b.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111b.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111b.html</feedburner:origLink></item>
	<item>
	<title>A Capability-Based Approach to Strategic Transformational Initiatives</title>
	<description>Krohn, Diana | Journals | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111d.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k7eCMuhfJtg:dbux0IyeyMM: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=k7eCMuhfJtg:dbux0IyeyMM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k7eCMuhfJtg:dbux0IyeyMM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k7eCMuhfJtg:dbux0IyeyMM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k7eCMuhfJtg:dbux0IyeyMM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k7eCMuhfJtg:dbux0IyeyMM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k7eCMuhfJtg:dbux0IyeyMM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/k7eCMuhfJtg" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 14:29:42 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/k7eCMuhfJtg/itj1111d.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111d.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111d.html</feedburner:origLink></item>
	<item>
	<title>The Tale of Two BAs: Why Business Architecture Is the Business Analysis Practice’s Best Friend</title>
	<description>McWhorter, Neal | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111c.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=HHQpZgfdjnw:HrbAEUZqCGQ: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=HHQpZgfdjnw:HrbAEUZqCGQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=HHQpZgfdjnw:HrbAEUZqCGQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=HHQpZgfdjnw:HrbAEUZqCGQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=HHQpZgfdjnw:HrbAEUZqCGQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=HHQpZgfdjnw:HrbAEUZqCGQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=HHQpZgfdjnw:HrbAEUZqCGQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/HHQpZgfdjnw" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 14:26:25 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/HHQpZgfdjnw/itj1111c.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111c.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111c.html</feedburner:origLink></item>
	<item>
	<title>Creating a New Multidisciplinary Cancer Center Using Business Architecture</title>
	<description>Libutti, Steven; Zahavi, Ron | 
&lt;br/&gt;&lt;br/&gt;
By allowing an organization to analyze and visualize the entire business and apply business blueprints to both strategic transformation initiatives and ongoing business challenges, business architecture becomes an enabler of critical business strategies. This issue of Cutter IT Journal brings these factors to light through five articles by business architecture practitioners. These articles discuss business architecture in the context of strategic planning, requirements analysis, holistic business analysis, strategic transformation, and organizational transformation.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111e.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LAkMuQbEzig:GIMb_qDUm2I: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=LAkMuQbEzig:GIMb_qDUm2I:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LAkMuQbEzig:GIMb_qDUm2I:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LAkMuQbEzig:GIMb_qDUm2I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LAkMuQbEzig:GIMb_qDUm2I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LAkMuQbEzig:GIMb_qDUm2I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LAkMuQbEzig:GIMb_qDUm2I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/LAkMuQbEzig" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 14:22:57 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/LAkMuQbEzig/itj1111e.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111e.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/11/itj1111e.html</feedburner:origLink></item>
	<item>
	<title>Considerations for Scalability</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
I was recently asked by a client to evaluate a product in terms of scalability. The client had invested in a custom case management system that had 100 users and wanted to know whether the current architecture would support scaling to 3,000 users. By today's standards, it's not breaking any new ground to support 3,000 users, but the question is, "What are all of the things that need to be considered to determine the scalability?" To examine this, let's take an example from my weekend's activities.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111116.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Q-XmKMKFt8g:WRhPRyxAa58: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=Q-XmKMKFt8g:WRhPRyxAa58:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Q-XmKMKFt8g:WRhPRyxAa58:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Q-XmKMKFt8g:WRhPRyxAa58:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Q-XmKMKFt8g:WRhPRyxAa58:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Q-XmKMKFt8g:WRhPRyxAa58:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Q-XmKMKFt8g:WRhPRyxAa58:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Q-XmKMKFt8g" height="1" width="1"/&gt;</description>
	<pubDate>16 Nov 2011 16:13:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Q-XmKMKFt8g/ea111116.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111116.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111116.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part VI -- Enabling Innovation and Business Model Transformation</title>
	<description>Ulrich, William | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
In Part II of this Executive Update series, we introduced the business-driven transformation roadmap.1 This roadmap differs from a typical project roadmap because it focuses on transforming how organizations deliver stakeholder value and improving underlying business capabilities from a business, versus IT, perspective. Here in Part VI, the final installment of the series, we discuss practice-based approaches to delivering innovative, actionable, and highly effective business solutions.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1115.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3_OF84FTWds:liI-wmifK6Q: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=3_OF84FTWds:liI-wmifK6Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3_OF84FTWds:liI-wmifK6Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3_OF84FTWds:liI-wmifK6Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3_OF84FTWds:liI-wmifK6Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3_OF84FTWds:liI-wmifK6Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3_OF84FTWds:liI-wmifK6Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3_OF84FTWds" height="1" width="1"/&gt;</description>
	<pubDate>15 Nov 2011 16:02:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3_OF84FTWds/eau1115.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1115.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1115.html</feedburner:origLink></item>
	<item>
	<title>Modeling Languages that Support BPM</title>
	<description>Dooley, Brian | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Business process modeling lies at the core of all attempts to visualize and manage business processes. Process modeling documents the state of current processes, highlights opportunities for improvement and inefficiencies, and serves as the basis for task automation. Increasingly, modeling is required for compliance and for gaining a deeper understanding into operations, as well as for providing visibility to ensure rapid change in operations in pursuit of enterprise agility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111109.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RteY1N4ANw0:WgB9vDl7Qic: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=RteY1N4ANw0:WgB9vDl7Qic:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RteY1N4ANw0:WgB9vDl7Qic:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RteY1N4ANw0:WgB9vDl7Qic:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RteY1N4ANw0:WgB9vDl7Qic:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=RteY1N4ANw0:WgB9vDl7Qic:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=RteY1N4ANw0:WgB9vDl7Qic:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/RteY1N4ANw0" height="1" width="1"/&gt;</description>
	<pubDate>9 Nov 2011 15:29:47 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/RteY1N4ANw0/ea111109.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111109.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111109.html</feedburner:origLink></item>
	<item>
	<title>Never Complain, Never Explain: Exception No. 2</title>
	<description>Orr, Ken | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
A few weeks back, I wrote an EA Advisor in which I suggested that IT architects and engineers ought to have differing roles: architects should deal with high-level design and engineers with the detail technology ("Architects and Engineers: A New Way to Think About Them," 7 September 2011). Further, I suggested that architects should try, as much as possible, to "hide" extraneous technology details when talking to business users.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111102.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QOcVrc8XesI:D8_JUYKZIyc: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=QOcVrc8XesI:D8_JUYKZIyc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QOcVrc8XesI:D8_JUYKZIyc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QOcVrc8XesI:D8_JUYKZIyc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QOcVrc8XesI:D8_JUYKZIyc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=QOcVrc8XesI:D8_JUYKZIyc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=QOcVrc8XesI:D8_JUYKZIyc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/QOcVrc8XesI" height="1" width="1"/&gt;</description>
	<pubDate>2 Nov 2011 18:06:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/QOcVrc8XesI/ea111102.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111102.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111102.html</feedburner:origLink></item>
	<item>
	<title>Making Architectural Principles Actionable</title>
	<description>Rosen, Michael | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
Architectural principles are a common part of most EA programs, but as with anything, some principles are better defined than others and some EA programs better understand the role of principles and how to use them.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111026.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oHOPiIRQCpg:PhtRyxIjm_I: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=oHOPiIRQCpg:PhtRyxIjm_I:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oHOPiIRQCpg:PhtRyxIjm_I:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oHOPiIRQCpg:PhtRyxIjm_I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oHOPiIRQCpg:PhtRyxIjm_I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oHOPiIRQCpg:PhtRyxIjm_I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oHOPiIRQCpg:PhtRyxIjm_I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/oHOPiIRQCpg" height="1" width="1"/&gt;</description>
	<pubDate>25 Oct 2011 17:41:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/oHOPiIRQCpg/ea111026.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111026.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111026.html</feedburner:origLink></item>
	<item>
	<title>Current Practices in Business Process Modeling</title>
	<description>Dooley, Brian | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
Business process modeling lies at the core of all attempts to visualize and manage business processes. Process modeling documents the state of current processes, highlights opportunities for improvement and inefficiencies, and serves as the basis for task automation. Increasingly, modeling is required for compliance and for gaining a deeper understanding into operations, as well as for providing visibility to ensure rapid change in operations in pursuit of enterprise agility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1114.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zfK6K6UVauQ:DNaOlxonUeE: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=zfK6K6UVauQ:DNaOlxonUeE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zfK6K6UVauQ:DNaOlxonUeE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zfK6K6UVauQ:DNaOlxonUeE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zfK6K6UVauQ:DNaOlxonUeE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=zfK6K6UVauQ:DNaOlxonUeE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=zfK6K6UVauQ:DNaOlxonUeE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/zfK6K6UVauQ" height="1" width="1"/&gt;</description>
	<pubDate>21 Oct 2011 17:03:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/zfK6K6UVauQ/eau1114.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1114.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1114.html</feedburner:origLink></item>
	<item>
	<title>Cloud Computing Marches On, But Issues Remain the Same</title>
	<description>Hall, Curt | 
&lt;br/&gt;&lt;br/&gt;
A reader asked me about the state of cloud computing. I responded by saying that advancements in cloud technology and product/service offerings have really taken off and that the number of organizations using cloud offerings also has increased considerably. Today, I think you'd be hard-pressed to find someone who would disagree that cloud computing should be considered a facilitating platform for supporting various on-demand (SaaS) platforms, applications, and services - ranging from operational applications for CRM, ERP, and HR to BI, data management, and analytic offerings. That said, I believe that many of the same key issues that plagued or hindered cloud computing from the start still remain, for the most part, unchanged.
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111019.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DPVkWzUy9c:vgBDIqj9Te0: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=2DPVkWzUy9c:vgBDIqj9Te0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DPVkWzUy9c:vgBDIqj9Te0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DPVkWzUy9c:vgBDIqj9Te0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DPVkWzUy9c:vgBDIqj9Te0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DPVkWzUy9c:vgBDIqj9Te0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DPVkWzUy9c:vgBDIqj9Te0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/2DPVkWzUy9c" height="1" width="1"/&gt;</description>
	<pubDate>18 Oct 2011 19:11:25 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/2DPVkWzUy9c/ea111019.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111019.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111019.html</feedburner:origLink></item>
	<item>
	<title>Zachman Framework V3</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In August, John Zachman unveiled the new Version 3.0 of his framework. Now officially called "The Zachman Framework for Enterprise Architecture: The Enterprise Ontology&amp;trade;" (see www.zachman.com), it represents a continual refinement from previous versions. And like previous refinements, it is a combination of new graphics (shown in Figure 1), improved naming, and other clarifications. To get to the heart of the changes, lets first review the basics of the framework.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111012.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uyR11XDWRac:dyzExy1LPKU: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=uyR11XDWRac:dyzExy1LPKU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uyR11XDWRac:dyzExy1LPKU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uyR11XDWRac:dyzExy1LPKU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uyR11XDWRac:dyzExy1LPKU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uyR11XDWRac:dyzExy1LPKU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uyR11XDWRac:dyzExy1LPKU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/uyR11XDWRac" height="1" width="1"/&gt;</description>
	<pubDate>11 Oct 2011 18:49:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/uyR11XDWRac/ea111012.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111012.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111012.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part V -- Team Building Through Development</title>
	<description>Ulrich, William | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
In Parts I-IV of this Executive Update series, we discussed how business architecture provides the means for shaping and communicating business strategy, transformation roadmaps, and funding models; how to use value streams as a basis for planning and deploying business initiatives; and how capabilities form the foundation for articulating a shared business vocabulary. 1 Here in Part V, we outline how to establish and socialize the business architecture, including introducing a rapid roadmap deployment approach that business architecture teams can use as a template for getting started.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1113.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ovvQB16tYJ8:wkdvT8UzIcA: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=ovvQB16tYJ8:wkdvT8UzIcA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ovvQB16tYJ8:wkdvT8UzIcA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ovvQB16tYJ8:wkdvT8UzIcA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ovvQB16tYJ8:wkdvT8UzIcA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ovvQB16tYJ8:wkdvT8UzIcA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ovvQB16tYJ8:wkdvT8UzIcA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ovvQB16tYJ8" height="1" width="1"/&gt;</description>
	<pubDate>11 Oct 2011 18:44:07 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ovvQB16tYJ8/eau1113.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1113.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1113.html</feedburner:origLink></item>
	<item>
	<title>Never Complain, Never Explain: Exception No. 1</title>
	<description>Orr, Ken | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my last Business &amp; Enterprise Architecture Advisor ("Architects and Engineers: A New Way to Think About Them" 7 September 2011), I made a number of comments about the somewhat promiscuous use of the term "architect" -- as in "solutions architect" and "technology architect." Some of my readers saw this as something of a cheap shot. Henry Ford famously said, "never complain, never explain," and, by and large, I try to adhere to this advice. There are times, however, when it is important to respond, especially when your readers seem to take something you've said seriously.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111005.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c53h9f06Cwo:qcshFBQr8XE: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=c53h9f06Cwo:qcshFBQr8XE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c53h9f06Cwo:qcshFBQr8XE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c53h9f06Cwo:qcshFBQr8XE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c53h9f06Cwo:qcshFBQr8XE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=c53h9f06Cwo:qcshFBQr8XE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=c53h9f06Cwo:qcshFBQr8XE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/c53h9f06Cwo" height="1" width="1"/&gt;</description>
	<pubDate>5 Oct 2011 18:35:40 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/c53h9f06Cwo/ea111005.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111005.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea111005.html</feedburner:origLink></item>
	<item>
	<title>Beyond SOA</title>
	<description>Dooley, Brian J. | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
SOA remains an important area for development and enterprise implementation but recent trends in social computing, mobility, user-developed applications, and the cloud have significantly upstaged SOA, as we explore in this Executive Update. Although its principles remain relevant, there is a growing consensus that SOA concepts, definitions, and procedures need to be updated to meet the needs of a new reality. This should hardly be surprising, since the initial concept of SOA fulfilled the purpose in defining a plateau of evolutionary development rather than a radically new technology. Such definitions are subject to change as capabilities, practices, and the surrounding environment move on.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1112.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=L4AYJ5T_HGg:N1t6sLa0ZlA: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=L4AYJ5T_HGg:N1t6sLa0ZlA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=L4AYJ5T_HGg:N1t6sLa0ZlA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=L4AYJ5T_HGg:N1t6sLa0ZlA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=L4AYJ5T_HGg:N1t6sLa0ZlA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=L4AYJ5T_HGg:N1t6sLa0ZlA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=L4AYJ5T_HGg:N1t6sLa0ZlA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/L4AYJ5T_HGg" height="1" width="1"/&gt;</description>
	<pubDate>29 Sep 2011 17:33:07 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/L4AYJ5T_HGg/eau1112.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1112.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1112.html</feedburner:origLink></item>
	<item>
	<title>Principles of Design: Part II</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
In my last Advisor ("Principles of Design: Part I" 14 September 2011), I introduced the design principles of Dieter Ram, the lead designer at appliance manufacturer Braun for 34 years. To review, Dieter says that good design:
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110928.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ex8DOEjXXkQ:LV_eGBmaRI4: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=Ex8DOEjXXkQ:LV_eGBmaRI4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ex8DOEjXXkQ:LV_eGBmaRI4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ex8DOEjXXkQ:LV_eGBmaRI4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ex8DOEjXXkQ:LV_eGBmaRI4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ex8DOEjXXkQ:LV_eGBmaRI4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ex8DOEjXXkQ:LV_eGBmaRI4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Ex8DOEjXXkQ" height="1" width="1"/&gt;</description>
	<pubDate>28 Sep 2011 17:22:01 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Ex8DOEjXXkQ/ea110928.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110928.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110928.html</feedburner:origLink></item>
	<item>
	<title>How 21st-Century Enterprises Grow</title>
	<description>Evernden, Roger | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
It's your first briefing from the CIO: First and foremost, we need to keep everything up and running. And we absolutely have to meet mandatory compliance and regulatory deadlines. Then we've got to complete the integration project that kicked off following a big acquisition a couple of years ago, and it had better deliver the planned cost reductions and efficiencies, and on time, because we can't go back on our promises to shareholders. In parallel, we desperately need to transform our business and systems -- cracks are showing and getting bigger, and we're falling far behind competitors in meeting even basic customer expectations.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1111.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4Gk4QhSqbnI:2cI8diBc1rE: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=4Gk4QhSqbnI:2cI8diBc1rE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4Gk4QhSqbnI:2cI8diBc1rE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4Gk4QhSqbnI:2cI8diBc1rE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4Gk4QhSqbnI:2cI8diBc1rE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=4Gk4QhSqbnI:2cI8diBc1rE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=4Gk4QhSqbnI:2cI8diBc1rE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/4Gk4QhSqbnI" height="1" width="1"/&gt;</description>
	<pubDate>22 Sep 2011 15:30:02 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/4Gk4QhSqbnI/eau1111.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1111.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1111.html</feedburner:origLink></item>
	<item>
	<title>Desktop Virtualization: How Three Companies Are Doing It</title>
	<description>Hall, Curt | E-Mail Advisors | 20 September 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Nearly a year ago, I reported that advancements in virtualization technology have made virtual desktop environments much more practical and that this will facilitate broader mainstream adoption of desktop virtualization by end-user organizations (see "Flex Your VMs: The Benefits of Desktop Virtualization" 14 October 2010).
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110921.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=5trHSgFELsI:kQTsQEl2-ks: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=5trHSgFELsI:kQTsQEl2-ks:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=5trHSgFELsI:kQTsQEl2-ks:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=5trHSgFELsI:kQTsQEl2-ks:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=5trHSgFELsI:kQTsQEl2-ks:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=5trHSgFELsI:kQTsQEl2-ks:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=5trHSgFELsI:kQTsQEl2-ks:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/5trHSgFELsI" height="1" width="1"/&gt;</description>
	<pubDate>19 Sep 2011 15:46:42 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/5trHSgFELsI/ea110921.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110921.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110921.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part IV — Building a Robust Foundation for the Future</title>
	<description>Ulrich, William | Executive Updates | 
&lt;br/&gt;&lt;br/&gt;
In Part I and Part II of this six-part Executive Update series, we discussed the importance of executive sponsorship and outlined how business architecture provides the means for shaping and communicating business strategy, transformation roadmaps, and funding models. 1 Part III explored using value streams as a basis for planning and deploying various business initiatives. 2 Here in Part IV, we examine how capabilities, introduced in Part I, form the foundation for fusing business and IT through a shared vocabulary, vision, and transformation strategy.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1110.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LzS166EaRp0:5Yf0rNgMdAM: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=LzS166EaRp0:5Yf0rNgMdAM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LzS166EaRp0:5Yf0rNgMdAM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LzS166EaRp0:5Yf0rNgMdAM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LzS166EaRp0:5Yf0rNgMdAM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LzS166EaRp0:5Yf0rNgMdAM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LzS166EaRp0:5Yf0rNgMdAM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/LzS166EaRp0" height="1" width="1"/&gt;</description>
	<pubDate>19 Sep 2011 15:41:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/LzS166EaRp0/eau1110.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1110.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1110.html</feedburner:origLink></item>
	<item>
	<title>Principles of Design: Part I</title>
	<description>Rosen, Mike | E-Mail Advisors | 
&lt;br/&gt;&lt;br/&gt;
I happened across a really interesting exhibit on industrial design at the San Francisco MOMA last week. The exhibit features the designs of Dieter Ram, who was the chief designer for the German appliance manufacturer Braun for 25 years, from 1961-1995. The exhibit features hundreds of sleek, innovative, and intuitive household products that set the standards for good design for decades. In fact, Jonathan Ive, the chief designer at Apple, credits Ram with inspiring him and setting a foundation of design principles that can be seen in Apple's products.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110913.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AQ8jldmnxWA:rGCfrEdM-cQ: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=AQ8jldmnxWA:rGCfrEdM-cQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AQ8jldmnxWA:rGCfrEdM-cQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AQ8jldmnxWA:rGCfrEdM-cQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AQ8jldmnxWA:rGCfrEdM-cQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=AQ8jldmnxWA:rGCfrEdM-cQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=AQ8jldmnxWA:rGCfrEdM-cQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/AQ8jldmnxWA" height="1" width="1"/&gt;</description>
	<pubDate>13 Sep 2011 14:54:52 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/AQ8jldmnxWA/ea110913.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110913.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110913.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Integration with the Business Architecture</title>
	<description>Whittle, Ralph | Executive Reports | 
&lt;br/&gt;&lt;br/&gt;
This Executive Report describes the business architecture (BA) as an element linked to other enterprise elements to collectively form a structure focused on the customer. Several figures illustrate the formal integration with the IT architectures, business processes, and strategy. Built, implemented, and governed as a "reusable asset," the BA enables the enterprise to achieve something new, different, or even great -- something that it cannot achieve in its current state. This is the power of architecture and a key reason for integrating the BA throughout the enterprise.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/07/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YE0J_nXINZA:KfqcED0-Y90: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=YE0J_nXINZA:KfqcED0-Y90:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YE0J_nXINZA:KfqcED0-Y90:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YE0J_nXINZA:KfqcED0-Y90:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YE0J_nXINZA:KfqcED0-Y90:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=YE0J_nXINZA:KfqcED0-Y90:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=YE0J_nXINZA:KfqcED0-Y90:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/YE0J_nXINZA" height="1" width="1"/&gt;</description>
	<pubDate>12 Sep 2011 14:51:40 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/YE0J_nXINZA/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/07/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/07/index.html</feedburner:origLink></item>
	<item>
	<title>Architects and Engineers: A New Way to Think About Them</title>
	<description>Orr, Ken | E-Mail Advisors ::
&lt;br/&gt;&lt;br/&gt;
For some time now, I've been looking for a word or a phrase or some way to distinguish among classes of architects. Over the last decade, I've largely worked as an enterprise architect, with an emphasis on "business architecture" -- especially "business process reengineering" and "data architecture." Every so often, I'm finding myself talking to "technical" or "solutions" architects or experts in "business process tools" or "business rule engines," and so on. As much as I'm interested in the higher-level tools that continue to be built and aggressively marketed, I find that there is often a large gap between what I think of as "enterprise architecture" and "technical architecture."
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110907.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ErF7jn5RO-U:27NgtF4yz3Y: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=ErF7jn5RO-U:27NgtF4yz3Y:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ErF7jn5RO-U:27NgtF4yz3Y:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ErF7jn5RO-U:27NgtF4yz3Y:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ErF7jn5RO-U:27NgtF4yz3Y:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ErF7jn5RO-U:27NgtF4yz3Y:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ErF7jn5RO-U:27NgtF4yz3Y:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ErF7jn5RO-U" height="1" width="1"/&gt;</description>
	<pubDate>7 Sep 2011 18:43:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ErF7jn5RO-U/ea110907.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110907.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110907.html</feedburner:origLink></item>
	<item>
	<title>Using Enterprise Architecture for Governance, Alignment, and SOX Compliance</title>
	<description>Finkelstein, Clive | Executive Reports :: 
&lt;br/&gt;&lt;br/&gt;
In this Executive Report, I describe a practical approach utilizing enterprise architecture (EA) for rapid compliance with business governance requirements such as the US Sarbanes-Oxley Act of 2002 (SOX). Throughout the report, I show how senior management can establish internal controls by using a governance analysis framework (GAF), which is used to align and document the relationships within an enterprise that support financial and other reporting requirements. The framework is based on a comprehensive organizing framework using the Zachman Framework as well as proven EA methods and tools for the documentation and management of a GAF. It also ensures that senior management is able to comply with the internal control reporting requirements of Section 404 of SOX.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/06/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=SwpYcJcxPLk:SpCXZpgbWqs: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=SwpYcJcxPLk:SpCXZpgbWqs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=SwpYcJcxPLk:SpCXZpgbWqs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=SwpYcJcxPLk:SpCXZpgbWqs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=SwpYcJcxPLk:SpCXZpgbWqs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=SwpYcJcxPLk:SpCXZpgbWqs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=SwpYcJcxPLk:SpCXZpgbWqs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/SwpYcJcxPLk" height="1" width="1"/&gt;</description>
	<pubDate>29 Aug 2011 17:45:59 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/SwpYcJcxPLk/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/06/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/06/index.html</feedburner:origLink></item>
	<item>
	<title>Devops at Advance Internet: How We Got in the Door</title>
	<description>Shamow, Eric | Journals | 25 August 2011 | Business-IT Strategies; Enterprise Architecture; Cutter IT Journal 
&lt;br/&gt;&lt;br/&gt;
Only by providing positive results to the business and management can IT reverse its bad reputation and become a reliable partner again. In order to do that, we need to break through blockers in our thought process, and devops invites us to challenge traditional organizational barriers. The days of top-down control are over -- devops is a grass-roots movement similar to other horizontal revolutions, such as Facebook. The role of management is changing: no longer just directive, it is taking a more supportive role, unleashing the power of the people on the floor to achieve awesome results. And that is the focus of this issue of Cutter IT Journal.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/itjournal/fulltext/2011/08/itj1108b.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rZrWzKqIaR8:a_qBH1gH7-Q: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=rZrWzKqIaR8:a_qBH1gH7-Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rZrWzKqIaR8:a_qBH1gH7-Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rZrWzKqIaR8:a_qBH1gH7-Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rZrWzKqIaR8:a_qBH1gH7-Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=rZrWzKqIaR8:a_qBH1gH7-Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=rZrWzKqIaR8:a_qBH1gH7-Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/rZrWzKqIaR8" height="1" width="1"/&gt;</description>
	<pubDate>25 Aug 2011 14:28:55 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/rZrWzKqIaR8/itj1108b.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/itjournal/fulltext/2011/08/itj1108b.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/itjournal/fulltext/2011/08/itj1108b.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture, Planning, Roadmap Creation, and Budgeting</title>
	<description>Ulrich, William | E-Mail Advisors | 24 August 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Business architecture provides a basis for transforming how business communicates and collaborates to achieve its goals across business units and product lines. One of the most fundamental benefits, however, is that business architecture enables a more business-focused investment strategy in major initiatives. Most noninfrastructure-focused IT spending is typically aligned to a given set of software applications. This approach limits the business vision to a siloed, technology-centric point of view and leaves critical capabilities not part of an IT solution today off the table, virtually ignoring horizontal views of how to deliver stakeholder value. Positioning investments in terms of business capabilities and value streams allows the business to focus on business value and not on IT centricities.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110824.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TGmPudStt98:CCF46eoArpc: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=TGmPudStt98:CCF46eoArpc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TGmPudStt98:CCF46eoArpc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TGmPudStt98:CCF46eoArpc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TGmPudStt98:CCF46eoArpc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TGmPudStt98:CCF46eoArpc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TGmPudStt98:CCF46eoArpc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/TGmPudStt98" height="1" width="1"/&gt;</description>
	<pubDate>24 Aug 2011 14:00:13 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/TGmPudStt98/ea110824.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110824.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110824.html</feedburner:origLink></item>
	<item>
	<title>Enterprise, Architecture, Technical Debt, and Technical Analysis</title>
	<description>Orr, Ken | E-Mail Advisors | 17 August 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Recently, Cutter's Business &amp; Enterprise Architecture Practice Director Mike Rosen published an Advisor entitled "Use Architecture to Reduce Technical Debt" (10 August 2011), which opened the door for a discussion on one of the major problems facing many very large organizations today: technical paralysis. Technical paralysis sets in when it becomes impossible for an organization's information systems to be modified in a timely manner to respond to business, technical, or legal changes. Let me give you a couple examples from my own recent experience.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110817.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uW_8BzjOSuo:WGT9uRPiNpQ: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=uW_8BzjOSuo:WGT9uRPiNpQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uW_8BzjOSuo:WGT9uRPiNpQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uW_8BzjOSuo:WGT9uRPiNpQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uW_8BzjOSuo:WGT9uRPiNpQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=uW_8BzjOSuo:WGT9uRPiNpQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=uW_8BzjOSuo:WGT9uRPiNpQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/uW_8BzjOSuo" height="1" width="1"/&gt;</description>
	<pubDate>17 Aug 2011 16:22:15 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/uW_8BzjOSuo/ea110817.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110817.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110817.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part III -- Leveraging Value Streams in Business Transformation</title>
	<description>Ulrich, William | Executive Updates | 15 August 2011 | Enterprise Architecture; Business-IT Strategies 
&lt;br/&gt;&lt;br/&gt;
In Part I of this six-part Executive Update series on business architecture, we discussed the importance of executive sponsorship and leadership. 1 In Part II, we outlined how business architecture provides the means for shaping and communicating business strategy, transformation roadmaps, and funding models. 2 Here in Part III, we explore how to use value streams as a basis for deploying various business initiatives ranging from large-scale transformation efforts to near-term, high-payback tactical deployments. We discuss the use of value streams in improving productivity and enhancing the customer experience. Before we get into various case study examples, let's recap the role of the value stream in analyzing business challenges and crafting strategies for addressing those challenges.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1109.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=o-5wmedwO6g:kGj3FUifcQY: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=o-5wmedwO6g:kGj3FUifcQY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=o-5wmedwO6g:kGj3FUifcQY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=o-5wmedwO6g:kGj3FUifcQY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=o-5wmedwO6g:kGj3FUifcQY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=o-5wmedwO6g:kGj3FUifcQY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=o-5wmedwO6g:kGj3FUifcQY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/o-5wmedwO6g" height="1" width="1"/&gt;</description>
	<pubDate>15 Aug 2011 16:16:51 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/o-5wmedwO6g/eau1109.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1109.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1109.html</feedburner:origLink></item>
	<item>
	<title>Use Architecture to Reduce Technical Debt</title>
	<description>Rosen, Michael | E-Mail Advisors :: All the talk in the press lately about the US national debt (and the political system's inability to deal with it) got me thinking about another kind of debt near and dear to an architect. That is the "technical debt" that we have in our IT systems.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110810.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0kw67Yg9E1k:0QzupiV6MZk: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=0kw67Yg9E1k:0QzupiV6MZk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0kw67Yg9E1k:0QzupiV6MZk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0kw67Yg9E1k:0QzupiV6MZk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0kw67Yg9E1k:0QzupiV6MZk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0kw67Yg9E1k:0QzupiV6MZk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0kw67Yg9E1k:0QzupiV6MZk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0kw67Yg9E1k" height="1" width="1"/&gt;</description>
	<pubDate>10 Aug 2011 17:25:39 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0kw67Yg9E1k/ea110810.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110810.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110810.html</feedburner:origLink></item>
	<item>
	<title>Migration Considerations</title>
	<description>Cohen, Beth | E-Mail Advisors :: The general thinking in the cloud provider community -- public or private -- has been to assume that anyone moving applications into the cloud is creating new servers and building new systems and applications, not migrating existing applications and systems. This scenario is only valid for the typical startup, small, or medium-sized business with little or no investment in IT applications. The migration path is often as simple as moving a small customer database into a new SaaS application, often with more features and functionality. This makes cloud services the obvious first choice for this market segment. The majority of public cloud growth has been driven by new companies with few legacy systems to worry about. 
&lt;br/&gt;&lt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110803.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wtK5QuBks04:xubFYBOx6N8: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=wtK5QuBks04:xubFYBOx6N8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wtK5QuBks04:xubFYBOx6N8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wtK5QuBks04:xubFYBOx6N8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wtK5QuBks04:xubFYBOx6N8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wtK5QuBks04:xubFYBOx6N8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wtK5QuBks04:xubFYBOx6N8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/wtK5QuBks04" height="1" width="1"/&gt;</description>
	<pubDate>3 Aug 2011 17:24:36 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/wtK5QuBks04/ea110803.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110803.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110803.html</feedburner:origLink></item>
	<item>
	<title>Lessons From Egypt</title>
	<description>Rosen, Mike | E-Mail Advisors | 27 July 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
I just returned from Cairo, Egypt, where I visited the Pyramids of Giza and other antiquities, as well as experienced some of the protests going on in Tahrir Square. As usual, I find it useful to draw parallels between things in the real world and EA. Here are three lessons that I took away from Egypt:
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110727.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xWr4SlrHL98:_rQlBRvd7Jg: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=xWr4SlrHL98:_rQlBRvd7Jg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xWr4SlrHL98:_rQlBRvd7Jg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xWr4SlrHL98:_rQlBRvd7Jg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xWr4SlrHL98:_rQlBRvd7Jg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=xWr4SlrHL98:_rQlBRvd7Jg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=xWr4SlrHL98:_rQlBRvd7Jg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/xWr4SlrHL98" height="1" width="1"/&gt;</description>
	<pubDate>27 Jul 2011 15:24:50 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/xWr4SlrHL98/ea110727.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110727.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110727.html</feedburner:origLink></item>
	<item>
	<title>A Structured Approach to IT Cloud Migration</title>
	<description>Cohen, Beth | Executive Reports | 20 July 2011 | Enterprise Architecture; Enterprise Risk Management &amp; Governance; Business Intelligence 
&lt;br/&gt;&lt;br/&gt;
Migrating IT systems and infrastructure to cloud ecosystems cuts costs and improves service delivery. However, moving complex IT infrastructures directly to cloud architectures is not simple or easy. As discussed in this Executive Report, an enterprise needs to look not only at the technical aspects but also at how migration will affect business operations. Taking a structured approach to cloud migration projects bypasses roadblocks and allows for intelligent decisions that will benefit the business.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/05/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b5jWfDNiOec:PNZce7gI3Tg: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=b5jWfDNiOec:PNZce7gI3Tg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b5jWfDNiOec:PNZce7gI3Tg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b5jWfDNiOec:PNZce7gI3Tg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b5jWfDNiOec:PNZce7gI3Tg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b5jWfDNiOec:PNZce7gI3Tg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b5jWfDNiOec:PNZce7gI3Tg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/b5jWfDNiOec" height="1" width="1"/&gt;</description>
	<pubDate>20 Jul 2011 14:08:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/b5jWfDNiOec/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/05/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/05/index.html</feedburner:origLink></item>
	<item>
	<title>Transforming Planning Approaches and Challenges</title>
	<description>Ulrich, William | E-Mail Advisors | 20 July 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
When discussing why executives should leverage business architecture to facilitate strategic planning and transformation, it is useful to examine the challenges facing organizations making large-scale, multiyear IT investments. Planning teams often find it difficult to operationalize high-level policy statements, strategic plans, and new business models across highly segregated businesses. Each division has its own goals and related funding models and generally lacks visibility into what's happening in other business units. As a result, executives often make large spending decisions with little knowledge of how those decisions may help or harm the enterprise as a whole. This in turn stymies best-laid plans and business transformation strategies.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110720.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hNkMujqbUHE:ZKVQJXx-cNY: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=hNkMujqbUHE:ZKVQJXx-cNY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hNkMujqbUHE:ZKVQJXx-cNY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hNkMujqbUHE:ZKVQJXx-cNY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hNkMujqbUHE:ZKVQJXx-cNY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hNkMujqbUHE:ZKVQJXx-cNY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hNkMujqbUHE:ZKVQJXx-cNY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/hNkMujqbUHE" height="1" width="1"/&gt;</description>
	<pubDate>1 Aug 2011 14:06:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/hNkMujqbUHE/ea110720.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110720.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110720.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part II -- Business-Driven Transformation Strategies, Roadmaps, and Funding Models</title>
	<description>Ulrich, William | Executive Updates | 15 July 2011 | Business-IT Strategies; Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In Part I of this six-part Executive Update series on business architecture, we took a look at why business executives must sponsor and enable business architecture for the business. 1 We discussed how business architecture supports a wide range of business initiatives, such as improving customer service and reducing customer attrition; enabling merger, acquisition, and divestiture activities; and deploying new business strategies across product lines and business units. The challenge facing many organizations today is that enterprise strategies and executive mandates rarely align to funded initiatives and project deployments. Fragmented, redundant, or even conflicting projects often take organizations in directions that fall far short of strategic goals and executive mandates, in spite of the millions of dollars spent on these efforts. Here in Part II, we'll discuss how organizations can craft business-driven transformation strategies that address these challenges.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1108.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UmSXltlNH6g:EFWapd9L03A: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=UmSXltlNH6g:EFWapd9L03A:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UmSXltlNH6g:EFWapd9L03A:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UmSXltlNH6g:EFWapd9L03A:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UmSXltlNH6g:EFWapd9L03A:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UmSXltlNH6g:EFWapd9L03A:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UmSXltlNH6g:EFWapd9L03A:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/UmSXltlNH6g" height="1" width="1"/&gt;</description>
	<pubDate>15 Jul 2011 15:53:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/UmSXltlNH6g/eau1108.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1108.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1108.html</feedburner:origLink></item>
	<item>
	<title>Are You Doing Architecture?</title>
	<description>Rosen, Mike | E-Mail Advisors | 13 July 2011 | Business-IT Strategies; Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
In yet another conversation with a client, I was reviewing the activities that its architects were performing. As you can imagine, those activities included following procedure, organizing meetings, investigating issues or technologies, performing reviews, writing documents, creating models, and so on. As I pointed out in my last Advisor (see "Define Roles and Responsibilities to Avoid Conflict," 29 June 2011), an architect has many different roles. But one question we don't often ask is: Should architects be performing those roles? Or, put another way: What roles should they be performing? This leads to another question: Are we doing architecture?
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110713.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iVZV8pBY1jA:kH19cro8q-0: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=iVZV8pBY1jA:kH19cro8q-0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iVZV8pBY1jA:kH19cro8q-0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iVZV8pBY1jA:kH19cro8q-0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iVZV8pBY1jA:kH19cro8q-0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=iVZV8pBY1jA:kH19cro8q-0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=iVZV8pBY1jA:kH19cro8q-0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/iVZV8pBY1jA" height="1" width="1"/&gt;</description>
	<pubDate>13 Jul 2011 15:16:00 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/iVZV8pBY1jA/ea110713.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110713.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110713.html</feedburner:origLink></item>
	<item>
	<title>Sharing Sensor Data on the Web</title>
	<description>Di Maio, Paola | E-Mail Advisors | 06 July 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Lately, interest has been shifting from the physical layer of the Internet of Things toward a more abstract layer of a Web of Things (WoT), reflecting a stronger emphasis on the knowledge representation aspect. Some interesting examples of sensor Web efforts are listed below:
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110706.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0YQkCf-M6zA:j6Ut40r04t0: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=0YQkCf-M6zA:j6Ut40r04t0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0YQkCf-M6zA:j6Ut40r04t0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0YQkCf-M6zA:j6Ut40r04t0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0YQkCf-M6zA:j6Ut40r04t0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=0YQkCf-M6zA:j6Ut40r04t0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=0YQkCf-M6zA:j6Ut40r04t0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/0YQkCf-M6zA" height="1" width="1"/&gt;</description>
	<pubDate>6 Jul 2011 16:29:01 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/0YQkCf-M6zA/ea110706.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110706.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110706.html</feedburner:origLink></item>
	<item>
	<title>Aligning Enterprise Architecture, Strategy, and Portfolio Management</title>
	<description>Finkelstein, Clive | Executive Reports | 05 July 2011 | Business-IT Strategies; Enterprise Architecture; Business Intelligence 
&lt;br/&gt;&lt;br/&gt;
Success with enterprise architecture depends on strategy, rather than on existing business processes. This leads to the development of a strategic model of the enterprise as a "picture of the business" for management, while also being a high-level enterprise model for IT. This strategic model is analyzed to derive a portfolio of systems based on management priorities. This Executive Report demonstrates methods you can use to derive project plans and project maps from data maps by inspection. These easy-to-apply methods have not previously been used in data modeling and promise to transform portfolio management.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/04/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6gBBLYRYSnc:hOt9yFILftU: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=6gBBLYRYSnc:hOt9yFILftU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6gBBLYRYSnc:hOt9yFILftU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6gBBLYRYSnc:hOt9yFILftU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6gBBLYRYSnc:hOt9yFILftU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=6gBBLYRYSnc:hOt9yFILftU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=6gBBLYRYSnc:hOt9yFILftU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/6gBBLYRYSnc" height="1" width="1"/&gt;</description>
	<pubDate>5 Jul 2011 15:50:21 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/6gBBLYRYSnc/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/04/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/04/index.html</feedburner:origLink></item>
	<item>
	<title>The Coming Tsunami: In-Memory Databases, Part II</title>
	<description>Kellen, Vince | E-Mail Advisors | 23 June 2011 | Enterprise Architecture; Business Intelligence; Business Technology Trends &amp; Impacts 
&lt;br/&gt;&lt;br/&gt;
In last week's Advisor, I began a discussion of SAP's new HANA architecture (see "The Coming Tsunami: In-Memory Databases, Part I," 16 June 2011). SAP's long-term strategy is to use this architecture also as a persistent store of data for its transactional system, hence the inclusion of a row-oriented database. This is a polite way of saying that sometime in the future you won't need another vendor's database system. The HANA architecture uses flash memory as the persistent store, so there will be no spinning disks. SAP's software will be able to replicate its transactions in real time to HANA, without needing nightly or batch-oriented ETL processes to load the system or maintain aggregates. The appliance is able to import data from other systems easily using conventional ODBC/JDBC methods. The architecture also has a real-time replication component that I assume will be used for making copies of the data inside for recovery and performance purposes.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110623.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kGvPxG2BokE:KmOwcT9pxcw: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=kGvPxG2BokE:KmOwcT9pxcw:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kGvPxG2BokE:KmOwcT9pxcw:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kGvPxG2BokE:KmOwcT9pxcw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kGvPxG2BokE:KmOwcT9pxcw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=kGvPxG2BokE:KmOwcT9pxcw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=kGvPxG2BokE:KmOwcT9pxcw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/kGvPxG2BokE" height="1" width="1"/&gt;</description>
	<pubDate>23 Jun 2011 13:52:18 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/kGvPxG2BokE/btt110623.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110623.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110623.html</feedburner:origLink></item>
	<item>
	<title>The Benefits of Business Architecture</title>
	<description>Ulrich, William | E-Mail Advisors | 22 June 2011 | Enterprise Architecture; Business-IT Strategies
&lt;br/&gt;&lt;br/&gt;
Business architecture is gaining recognition as a game-changing discipline that enables businesses to address major challenges in new and unique ways. Simply put, business architecture allows a business to establish a common vocabulary, shared vision, and a degree of transparency that facilitates initiatives ranging from M&amp;As to the reversal of customer attrition. But even as business architecture success stories emerge, the message has been slow to penetrate the executive suite.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110622.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=e6eYg1nKuYw:x8SQV1Ygn2Y: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=e6eYg1nKuYw:x8SQV1Ygn2Y:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=e6eYg1nKuYw:x8SQV1Ygn2Y:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=e6eYg1nKuYw:x8SQV1Ygn2Y:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=e6eYg1nKuYw:x8SQV1Ygn2Y:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=e6eYg1nKuYw:x8SQV1Ygn2Y:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=e6eYg1nKuYw:x8SQV1Ygn2Y:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/e6eYg1nKuYw" height="1" width="1"/&gt;</description>
	<pubDate>22 Jun 2011 13:33:37 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/e6eYg1nKuYw/ea110622.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110622.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110622.html</feedburner:origLink></item>
	<item>
	<title>The Coming Tsunami: In-Memory Databases, Part I</title>
	<description>Kellen, Vince | E-Mail Advisors | 16 June 2011 | Business-IT Strategies; Enterprise Architecture; Business Technology Trends &amp; Impacts 
&lt;br/&gt;&lt;br/&gt;
SAP may have dished up a fastball high and inside, just under the chin. The target: its database competitors.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110616.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wZn4b618zZo:G0s_YmqfKQQ: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=wZn4b618zZo:G0s_YmqfKQQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wZn4b618zZo:G0s_YmqfKQQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wZn4b618zZo:G0s_YmqfKQQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wZn4b618zZo:G0s_YmqfKQQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wZn4b618zZo:G0s_YmqfKQQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wZn4b618zZo:G0s_YmqfKQQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/wZn4b618zZo" height="1" width="1"/&gt;</description>
	<pubDate>16 Jun 2011 17:10:26 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/wZn4b618zZo/btt110616.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110616.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110616.html</feedburner:origLink></item>
	<item>
	<title>Classification, Understanding, and Frameworks</title>
	<description>Rosen, Mike | E-Mail Advisors | 15 June 2011 | Enterprise Architecture; Business-IT Strategies
&lt;br/&gt;&lt;br/&gt;
In other words, data is a collection of unorganized/uninterrupted facts. When we put those facts in the context of a schema or classification, then we have useful information. When we put that information into the context of experience, then we have knowledge. When we apply that knowledge to add value, then we have wisdom.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110615.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aBUe5WyfG4o:yAmNmjS39Mc: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=aBUe5WyfG4o:yAmNmjS39Mc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aBUe5WyfG4o:yAmNmjS39Mc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aBUe5WyfG4o:yAmNmjS39Mc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aBUe5WyfG4o:yAmNmjS39Mc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aBUe5WyfG4o:yAmNmjS39Mc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aBUe5WyfG4o:yAmNmjS39Mc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/aBUe5WyfG4o" height="1" width="1"/&gt;</description>
	<pubDate>15 Jun 2011 16:24:15 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/aBUe5WyfG4o/ea110615.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110615.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110615.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: Part I -- Why It Matters to Business Executives</title>
	<description>Ulrich, William | Executive Updates | 14 June 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Business architecture is gaining recognition as a game-changing discipline that enables businesses to address major challenges in new and unique ways. Simply put, business architecture allows a business to establish a common vocabulary, shared vision, and a degree of transparency that facilitates initiatives ranging from M&amp;As to the reversal of customer attrition. But even as business architecture success stories emerge, the message has been slow to penetrate the executive suite. This Executive Update, the first in a series, discusses why business leaders should embrace business architecture as a means of addressing complex business challenges in ways that senior leadership can no longer ignore.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1107.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qon1faECuQ4:qY487H0UQCY: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=qon1faECuQ4:qY487H0UQCY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qon1faECuQ4:qY487H0UQCY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qon1faECuQ4:qY487H0UQCY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qon1faECuQ4:qY487H0UQCY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=qon1faECuQ4:qY487H0UQCY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=qon1faECuQ4:qY487H0UQCY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/qon1faECuQ4" height="1" width="1"/&gt;</description>
	<pubDate>14 Jun 2011 16:14:40 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/qon1faECuQ4/eau1107.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1107.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1107.html</feedburner:origLink></item>
	<item>
	<title>Capability Mapping Quick Start</title>
	<description>Cutter Consortium | Consulting | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Business capabilities are the core of the business architecture. A business capability defines "what" a business does. This is different than "how" things are done or where they are done. Business capabilities provide a vocabulary for business leaders to communicate and collaborate with each other and with information technology planning and deployment teams. Communication and collaboration is enabled as a result of having a common language for terms and concepts that are often misinterpreted, poorly considered, and dangerously inconsistent. For example, most organizations have poorly defined definitions for simple terms such as customer, agent, product, account, policy, margin, and profit. The capabilities that they possess related to these and numerous other topics are equally ill-defined and misconstrued. Capability mapping sorts this out -- for once and for all for the business as a whole.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/consulting-and-training/capability-mapping-quick-start.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UMujmvoSubY:RXEMqTf9xmQ: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=UMujmvoSubY:RXEMqTf9xmQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UMujmvoSubY:RXEMqTf9xmQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UMujmvoSubY:RXEMqTf9xmQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UMujmvoSubY:RXEMqTf9xmQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=UMujmvoSubY:RXEMqTf9xmQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=UMujmvoSubY:RXEMqTf9xmQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/UMujmvoSubY" height="1" width="1"/&gt;</description>
	<pubDate>10 Jun 2011 15:04:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/UMujmvoSubY/capability-mapping-quick-start.html</link>
	<guid isPermaLink="false">http://www.cutter.com/consulting-and-training/capability-mapping-quick-start.html</guid>
	<feedburner:origLink>http://www.cutter.com/consulting-and-training/capability-mapping-quick-start.html</feedburner:origLink></item>
	<item>
	<title>Risk Management = Testing</title>
	<description>Estes, Don | E-Mail Advisors | 08 June 2011 | Enterprise Architecture; Business-IT Strategies
&lt;br/&gt;&lt;br/&gt;
If we create a suitably accurate and comprehensive set of tests at the outset of the project -- tests for both performance and business functionality, the two primary reasons for project failure -- and apply those tests continually throughout the project, then the project can never fail on either basis. In effect, I recommend applying a large-scale version of test-driven development, a key feature of agile programming methodologies.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110608.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fhjqkiqtyAQ:B0Kj36nBMq8: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=fhjqkiqtyAQ:B0Kj36nBMq8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fhjqkiqtyAQ:B0Kj36nBMq8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fhjqkiqtyAQ:B0Kj36nBMq8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fhjqkiqtyAQ:B0Kj36nBMq8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=fhjqkiqtyAQ:B0Kj36nBMq8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=fhjqkiqtyAQ:B0Kj36nBMq8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/fhjqkiqtyAQ" height="1" width="1"/&gt;</description>
	<pubDate>8 Jun 2011 14:32:08 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/fhjqkiqtyAQ/ea110608.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110608.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110608.html</feedburner:origLink></item>
	<item>
	<title>Architecting Sustainable IT: Use Your Green Thumb</title>
	<description>Rosen, Mike | E-Mail Advisors | 01 June 2011 | Enterprise Architecture; Business-IT Strategies 
&lt;br/&gt;&lt;br/&gt;
This week, in recognition of International Green IT Awareness Week, Cutter is addressing the topic of green or sustainable IT. The question I'll explore is how to take an architectural approach to going green. First, let me propose the following definitions.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110601.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WXkFUPfS2Cc:czqZ190jhjY: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=WXkFUPfS2Cc:czqZ190jhjY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WXkFUPfS2Cc:czqZ190jhjY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WXkFUPfS2Cc:czqZ190jhjY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WXkFUPfS2Cc:czqZ190jhjY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WXkFUPfS2Cc:czqZ190jhjY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WXkFUPfS2Cc:czqZ190jhjY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/WXkFUPfS2Cc" height="1" width="1"/&gt;</description>
	<pubDate>1 May 2011 15:18:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/WXkFUPfS2Cc/ea110601.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110601.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110601.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture Quick Start</title>
	<description>Ulrich, William M. | Consulting | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Business architecture is not just one more approach or technique; it is a shift in philosophy. In organizations where business architecture is embraced, the role of strategic visioning, issue analysis and transformation planning is shifted to the business. When the business takes ownership of the business vocabulary and accompanying views, the organization can break free of the silo-oriented shackles that curtail strategic planning, visioning, and funding, and obstruct initiative deployment. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/consulting-and-training/business-architecture-quick-start.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=78ItJWP7BnM:Pq950jILsUo: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=78ItJWP7BnM:Pq950jILsUo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=78ItJWP7BnM:Pq950jILsUo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=78ItJWP7BnM:Pq950jILsUo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=78ItJWP7BnM:Pq950jILsUo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=78ItJWP7BnM:Pq950jILsUo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=78ItJWP7BnM:Pq950jILsUo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/78ItJWP7BnM" height="1" width="1"/&gt;</description>
	<pubDate>31 May 2011 15:13:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/78ItJWP7BnM/business-architecture-quick-start.html</link>
	<guid isPermaLink="false">http://www.cutter.com/consulting-and-training/business-architecture-quick-start.html</guid>
	<feedburner:origLink>http://www.cutter.com/consulting-and-training/business-architecture-quick-start.html</feedburner:origLink></item>
	<item>
	<title>Providing the Architecture for Progressive Modernization</title>
	<description>Simmons, Scott | E-Mail Advisors | 25 May 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
A key tenet for modernizing core systems is to assess the current solution and to define the context for the to-be solution. While working with a large customer in Europe, my colleagues and I focused an eight-week effort on assessing the current environment and the readiness to renew core systems. The assessment revealed issues about product currency in operational environments and resulted in our recommendation to correct these infrastructure matters before embarking on a renewal. These tasks are ongoing as part of broader development initiatives. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110525.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=s7VgJ6a0eiI:WSzmzlN-kGk: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=s7VgJ6a0eiI:WSzmzlN-kGk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=s7VgJ6a0eiI:WSzmzlN-kGk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=s7VgJ6a0eiI:WSzmzlN-kGk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=s7VgJ6a0eiI:WSzmzlN-kGk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=s7VgJ6a0eiI:WSzmzlN-kGk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=s7VgJ6a0eiI:WSzmzlN-kGk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/s7VgJ6a0eiI" height="1" width="1"/&gt;</description>
	<pubDate>25 May 2011 14:40:53 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/s7VgJ6a0eiI/ea110525.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110525.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110525.html</feedburner:origLink></item>
	<item>
	<title>Chromebooks Will Shake Up Enterprise Computing</title>
	<description>Hall, Curt | E-Mail Advisors | 18 May 2011 | Enterprise Architecture; Business Technology Trends &amp; Impacts; Sourcing &amp; Vendor Relationships; Enterprise Risk Management &amp; Governance; Business Intelligence 
&lt;br/&gt;&lt;br/&gt;
Google's introduction of the Chromebook has serious implications for cloud computing and IT -- and threatens to shake up enterprise computing. Google is hoping that companies will find Chromebook's reduced maintenance and lower cost of ownership too good to resist. But Google does not expect companies to embrace Chromebook overnight. Rather, the company is betting that Chromebook adoption will gain momentum as organizations warm up to the concept -- just as has been the case with cloud computing, in general.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110518.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TBk-28aOvv0:qjYQ-lg6Nv8: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=TBk-28aOvv0:qjYQ-lg6Nv8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TBk-28aOvv0:qjYQ-lg6Nv8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TBk-28aOvv0:qjYQ-lg6Nv8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TBk-28aOvv0:qjYQ-lg6Nv8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TBk-28aOvv0:qjYQ-lg6Nv8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TBk-28aOvv0:qjYQ-lg6Nv8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/TBk-28aOvv0" height="1" width="1"/&gt;</description>
	<pubDate>18 May 2011 14:43:37 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/TBk-28aOvv0/ea110518.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110518.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110518.html</feedburner:origLink></item>
	<item>
	<title>Understand Application Layers and Tiers</title>
	<description>Rosen, Michael | E-Mail Advisors | 11 May 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In my last Advisor, I discussed the characteristics that you should expect from an enterprise application architecture (see "Are You Ready for New Media?" 27 April 2011). This week, I'll explore two fundamental concepts of the application architecture: layers and tiers. Figure 1 shows the relationship between these two concepts with respect to the application architecture.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110511.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=arE9YNUzTiA:9IIRgPizlWc: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=arE9YNUzTiA:9IIRgPizlWc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=arE9YNUzTiA:9IIRgPizlWc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=arE9YNUzTiA:9IIRgPizlWc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=arE9YNUzTiA:9IIRgPizlWc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=arE9YNUzTiA:9IIRgPizlWc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=arE9YNUzTiA:9IIRgPizlWc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/arE9YNUzTiA" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 19:05:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/arE9YNUzTiA/ea110511.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110511.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110511.html</feedburner:origLink></item>
	<item>
	<title>What Should and Should Not Be Moved to the Cloud: How Enterprise Architecture Settles the Question Webinar</title>
	<description>Rosen, Mike | Webinars/Multimedia | 11 May 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Everyone is talking about the cloud, but from many different perspectives. Some think it means virtualization, others think it means scalable infrastructure, and still others think it means software-as-a-service. Sometimes, the business has a different and dangerous perspective, thinking that the cloud provides a new way to source IT solutions without having to go through the IT department. At the same time, there are many other issues relating to the cloud and affecting its adoption such as integration, security, data integrity, reliability, accountability and responsibility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/webinar/2011/moving-to-the-cloud.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MivF4ICI0ZM:1_x4pCFd1s0: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=MivF4ICI0ZM:1_x4pCFd1s0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MivF4ICI0ZM:1_x4pCFd1s0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MivF4ICI0ZM:1_x4pCFd1s0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MivF4ICI0ZM:1_x4pCFd1s0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=MivF4ICI0ZM:1_x4pCFd1s0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=MivF4ICI0ZM:1_x4pCFd1s0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/MivF4ICI0ZM" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 19:02:41 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/MivF4ICI0ZM/moving-to-the-cloud.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/webinar/2011/moving-to-the-cloud.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/webinar/2011/moving-to-the-cloud.html</feedburner:origLink></item>
	<item>
	<title>Business Architecture: A Comprehensive Deployment Roadmap</title>
	<description>Ulrich, William M. | Consulting | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Length: 2.5 days
Course Delivery: Onsite
Content Provided: Training Material Hardcopy and PDF Format
Course Objectives:
Understand the vital impacts of poorly aligned business architectures
Provide a total view on how to establish a business architecture team and program
Learn how to create basic business architecture blueprints such as the capability map
Build an understanding on how to establish the business architecture knowledgebase
Learn how to establish or solidify your business architecture team
Understand the basics of business architecture / IT architecture mapping and alignment
Gain experience with engagement models required to deploy business architecture roadmaps
Walk through various scenarios, case studies and exercises for deploying business architecture
Deliver a set of "getting started" guidelines for business architecture
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/workshops/business-architecture-roadmap.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ESeqJOEpiFU:ZX23nQJkBWM: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=ESeqJOEpiFU:ZX23nQJkBWM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ESeqJOEpiFU:ZX23nQJkBWM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ESeqJOEpiFU:ZX23nQJkBWM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ESeqJOEpiFU:ZX23nQJkBWM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ESeqJOEpiFU:ZX23nQJkBWM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ESeqJOEpiFU:ZX23nQJkBWM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ESeqJOEpiFU" height="1" width="1"/&gt;</description>
	<pubDate>9 May 2011 17:23:31 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ESeqJOEpiFU/business-architecture-roadmap.html</link>
	<guid isPermaLink="false">http://www.cutter.com/workshops/business-architecture-roadmap.html</guid>
	<feedburner:origLink>http://www.cutter.com/workshops/business-architecture-roadmap.html</feedburner:origLink></item>
	<item>
	<title>Webinar: What Should and Should Not Be Moved to the Cloud: How Enterprise Architecture Settles the Question</title>
	<description>Rosen, Mike | Events | 11 May 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Everyone is talking about the cloud, but from many different perspectives. Some think it means virtualization, others think it means scalable infrastructure, and still others think it means software-as-a-service. Sometimes, the business has a different and dangerous perspective, thinking that the cloud provides a new way to source IT solutions without having to go through the IT department. At the same time, there are many other issues relating to the cloud and affecting its adoption such as integration, security, data integrity, reliability, accountability and responsibility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/moving-to-the-cloud.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:1X6UpSlkaqg: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=3Qw7MHeBTsQ:1X6UpSlkaqg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:1X6UpSlkaqg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:1X6UpSlkaqg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:1X6UpSlkaqg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:1X6UpSlkaqg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:1X6UpSlkaqg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3Qw7MHeBTsQ" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 14:17:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3Qw7MHeBTsQ/moving-to-the-cloud.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</feedburner:origLink></item>
	<item>
	<title>How Cloud 2.0 Offers a Way Out of Silicon's Limits</title>
	<description>Kellen, Vince | E-Mail Advisors | 05 May 2011 | Business Technology Trends &amp; Impacts; Business Intelligence; Business-IT Strategies; Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Let's face it. We are at the end of Moore's Law. The common version of this law says computing power doubles every 18 to 24 months. Advances in silicon engineering have made this possible. But this natural law of silicon is driven by the fundamentals of materials science and the laws of physics. Unless we find a way to change the gravitational constant of the universe or surpass the speed of light, we are likely to face another four decades of computing unlike the past four decades. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110505.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2W1PBSKP-H8:N4qr0mcgAvs: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=2W1PBSKP-H8:N4qr0mcgAvs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2W1PBSKP-H8:N4qr0mcgAvs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2W1PBSKP-H8:N4qr0mcgAvs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2W1PBSKP-H8:N4qr0mcgAvs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2W1PBSKP-H8:N4qr0mcgAvs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2W1PBSKP-H8:N4qr0mcgAvs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/2W1PBSKP-H8" height="1" width="1"/&gt;</description>
	<pubDate>5 May 2011 14:13:55 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/2W1PBSKP-H8/btt110505.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110505.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110505.html</feedburner:origLink></item>
	<item>
	<title>Webinar: What Should and Should Not Be Moved to the Cloud: How Enterprise Architecture Settles the Question</title>
	<description>Rosen, Mike | Events | 11 May 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Everyone is talking about the cloud, but from many different perspectives. Some think it means virtualization, others think it means scalable infrastructure, and still others think it means software-as-a-service. Sometimes, the business has a different and dangerous perspective, thinking that the cloud provides a new way to source IT solutions without having to go through the IT department. At the same time, there are many other issues relating to the cloud and affecting its adoption such as integration, security, data integrity, reliability, accountability and responsibility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/moving-to-the-cloud.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Zi2_TvCQwRI: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=3Qw7MHeBTsQ:Zi2_TvCQwRI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Zi2_TvCQwRI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Zi2_TvCQwRI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Zi2_TvCQwRI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Zi2_TvCQwRI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Zi2_TvCQwRI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3Qw7MHeBTsQ" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 14:52:24 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3Qw7MHeBTsQ/moving-to-the-cloud.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</feedburner:origLink></item>
	<item>
	<title>Are You Ready for New Media?</title>
	<description>Rosen, Mike | E-Mail Advisors | 27 April 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
This week I bring you another internationally inspired Advisor from my trip to Rome, where I'm teaching two seminars on enterprise architecture. For this trip, I decided to modernize and leave my trusty old paper Italian phrasebook at home in lieu of a modern, talking, iPhone app. Although there were quite a few to choose from, I started with the free app.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110427.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vfepuei4_Js:UMDlQnZD6_w: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=vfepuei4_Js:UMDlQnZD6_w:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vfepuei4_Js:UMDlQnZD6_w:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vfepuei4_Js:UMDlQnZD6_w:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vfepuei4_Js:UMDlQnZD6_w:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=vfepuei4_Js:UMDlQnZD6_w:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=vfepuei4_Js:UMDlQnZD6_w:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/vfepuei4_Js" height="1" width="1"/&gt;</description>
	<pubDate>27 Apr 2011 18:55:43 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/vfepuei4_Js/ea110427.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110427.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110427.html</feedburner:origLink></item>
	<item>
	<title>Webinar: What Should and Should Not Be Moved to the Cloud: How Enterprise Architecture Settles the Question</title>
	<description>Rosen, Mike | Events | 11 May 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Everyone is talking about the cloud, but from many different perspectives. Some think it means virtualization, others think it means scalable infrastructure, and still others think it means software-as-a-service. Sometimes, the business has a different and dangerous perspective, thinking that the cloud provides a new way to source IT solutions without having to go through the IT department. At the same time, there are many other issues relating to the cloud and affecting its adoption such as integration, security, data integrity, reliability, accountability and responsibility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/moving-to-the-cloud.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:U2GG78F5kqo: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=3Qw7MHeBTsQ:U2GG78F5kqo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:U2GG78F5kqo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:U2GG78F5kqo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:U2GG78F5kqo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:U2GG78F5kqo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:U2GG78F5kqo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3Qw7MHeBTsQ" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 15:49:07 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3Qw7MHeBTsQ/moving-to-the-cloud.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</feedburner:origLink></item>
	<item>
	<title>Cloud Standards Ramp Up, Gain Key Advocates</title>
	<description>Hall, Curt | E-Mail Advisors | 20 April 2011 | Enterprise Architecture; Business-IT Strategies; Business Intelligence 
&lt;br/&gt;&lt;br/&gt;
Cloud computing has emerged as an attractive alternative to on-premise IT, offering organizations cost savings and greater flexibility in how they license, develop, and manage applications and how they store and manage data. But the big "however" with cloud computing remains a lack of open -- and generally accepted -- set of standards, benchmarks, methodologies, and best practices. This absence is standing in the way of more widespread adoption of clouds by end-user organizations. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110420.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NGbK4fxB6FE:YKv459AOA2M: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=NGbK4fxB6FE:YKv459AOA2M:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NGbK4fxB6FE:YKv459AOA2M:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NGbK4fxB6FE:YKv459AOA2M:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NGbK4fxB6FE:YKv459AOA2M:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=NGbK4fxB6FE:YKv459AOA2M:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=NGbK4fxB6FE:YKv459AOA2M:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/NGbK4fxB6FE" height="1" width="1"/&gt;</description>
	<pubDate>20 Apr 2011 15:12:37 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/NGbK4fxB6FE/ea110420.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110420.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110420.html</feedburner:origLink></item>
	<item>
	<title>Successful Application Modernization and Rationalization: Part II -- Long-Term Strategic Approaches</title>
	<description>Estes, Don | Executive Summaries | 18 April 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In Part II of this two-part Executive Report series on modernization, author Don Estes focuses on strategies that deliver the greatest business value, examining both conventional and promising unconventional approaches in depth, with their respective pros and cons. Since conventionally modernized applications will inevitably become "legacy" again, the author also analyzes how rationalization approaches can avoid this fate. The report concludes with an outline methodology for selecting an optimal project strategy.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/summaries/2011/03/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gg1XsHu8RUQ:WYjuXbWF1AM: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=Gg1XsHu8RUQ:WYjuXbWF1AM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gg1XsHu8RUQ:WYjuXbWF1AM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gg1XsHu8RUQ:WYjuXbWF1AM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gg1XsHu8RUQ:WYjuXbWF1AM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Gg1XsHu8RUQ:WYjuXbWF1AM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Gg1XsHu8RUQ:WYjuXbWF1AM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Gg1XsHu8RUQ" height="1" width="1"/&gt;</description>
	<pubDate>18 Apr 2011 14:48:08 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Gg1XsHu8RUQ/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/summaries/2011/03/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/summaries/2011/03/index.html</feedburner:origLink></item>
	<item>
	<title>Successful Application Modernization and Rationalization: Part II -- Long-Term Strategic Approaches</title>
	<description>Estes, Don | Executive Reports | 18 April 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In Part II of this two-part Executive Report series on modernization, author Don Estes focuses on strategies that deliver the greatest business value, examining both conventional and promising unconventional approaches in depth, with their respective pros and cons. Since conventionally modernized applications will inevitably become "legacy" again, the author also analyzes how rationalization approaches can avoid this fate. The report concludes with an outline methodology for selecting an optimal project strategy.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/reports/2011/03/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=mIFh0a8nfQY:4ke3VG-HxgU: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=mIFh0a8nfQY:4ke3VG-HxgU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=mIFh0a8nfQY:4ke3VG-HxgU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=mIFh0a8nfQY:4ke3VG-HxgU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=mIFh0a8nfQY:4ke3VG-HxgU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=mIFh0a8nfQY:4ke3VG-HxgU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=mIFh0a8nfQY:4ke3VG-HxgU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/mIFh0a8nfQY" height="1" width="1"/&gt;</description>
	<pubDate>18 Apr 2011 14:42:28 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/mIFh0a8nfQY/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/03/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/03/index.html</feedburner:origLink></item>
	<item>
	<title>Webinar: What Should and Should Not Be Moved to the Cloud: How Enterprise Architecture Settles the Question</title>
	<description>Rosen, Mike | Events | 11 May 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Everyone is talking about the cloud, but from many different perspectives. Some think it means virtualization, others think it means scalable infrastructure, and still others think it means software-as-a-service. Sometimes, the business has a different and dangerous perspective, thinking that the cloud provides a new way to source IT solutions without having to go through the IT department. At the same time, there are many other issues relating to the cloud and affecting its adoption such as integration, security, data integrity, reliability, accountability and responsibility.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/moving-to-the-cloud.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Z677wsH-XJ0: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=3Qw7MHeBTsQ:Z677wsH-XJ0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Z677wsH-XJ0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Z677wsH-XJ0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Z677wsH-XJ0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=3Qw7MHeBTsQ:Z677wsH-XJ0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=3Qw7MHeBTsQ:Z677wsH-XJ0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/3Qw7MHeBTsQ" height="1" width="1"/&gt;</description>
	<pubDate>11 May 2011 15:09:53 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/3Qw7MHeBTsQ/moving-to-the-cloud.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/moving-to-the-cloud.html</feedburner:origLink></item>
	<item>
	<title>Lessons from La Tour d'Eiffel</title>
	<description>Rosen, Mike | E-Mail Advisors | 13 April 2011 | Enterprise Architecture; Agile Project Management; Enterprise Risk Management &amp; Governance 
&lt;br/&gt;&lt;br/&gt;
Last week, I was visiting Paris and got the chance to marvel at the Tour d'Eiffel, one of the world's most well-known and instantly recognizable structures. I also took the opportunity to learn a bit more about its fascinating history. For example, I learned that the Eiffel Tower is the world's most visited paid tourist attraction, reaching its 200,000,000th visitor in 2002, and having more than 2.6 million visitors in 2010 alone. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110413.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nM7Ew87zQbo:vsjFzbNZT5Q: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=nM7Ew87zQbo:vsjFzbNZT5Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nM7Ew87zQbo:vsjFzbNZT5Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nM7Ew87zQbo:vsjFzbNZT5Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nM7Ew87zQbo:vsjFzbNZT5Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=nM7Ew87zQbo:vsjFzbNZT5Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=nM7Ew87zQbo:vsjFzbNZT5Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/nM7Ew87zQbo" height="1" width="1"/&gt;</description>
	<pubDate>13 Apr 2011 14:23:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/nM7Ew87zQbo/ea110413.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110413.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110413.html</feedburner:origLink></item>
	<item>
	<title>Reuse Maturity Model: Establishing a Software Vocabulary</title>
	<description>Sharma, Nikhil; Mutha, Mohit; Upasani, Vinay; Marsh, Lawrence | E-Mail Advisors | 06 April 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Software development has been full of fast-paced advancements, with a focus on increasing efficiency and reducing cost/efforts for stakeholders. Applying these changes forms a crucial part of the reusability concern that has been at the forefront of new business initiatives or development. Reuse has been central to many of the development models as have such tenets as "don't reinvent the wheel" and "don't repeat yourself."
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110406.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XCfzuwkONzQ:7MsKL9QUqtk: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=XCfzuwkONzQ:7MsKL9QUqtk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XCfzuwkONzQ:7MsKL9QUqtk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XCfzuwkONzQ:7MsKL9QUqtk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XCfzuwkONzQ:7MsKL9QUqtk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XCfzuwkONzQ:7MsKL9QUqtk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XCfzuwkONzQ:7MsKL9QUqtk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/XCfzuwkONzQ" height="1" width="1"/&gt;</description>
	<pubDate>6 Apr 2011 14:46:39 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/XCfzuwkONzQ/ea110406.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110406.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110406.html</feedburner:origLink></item>
	<item>
	<title>About the Enterprise Architecture Practice</title>
	<description>Cutter Consortium | 30 March 2011 | 
&lt;br/&gt;&lt;br/&gt;
Cutter's EA Practice offers a rich menu of services that are designed to help your organization create and deploy an enterprise architecture that increases business opportunities, supports agility, and delivers value. From clarifying your strategic architectural approach to maximizing the benefits of the various EA frameworks, Cutter offers the consulting, training and research you need to make enterprise architecture a source of strategic competitive advantage.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content-and-analysis/resource-centers/enterprise-architecture.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hotvL46gXA8:17PxpKnOyjA: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=hotvL46gXA8:17PxpKnOyjA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hotvL46gXA8:17PxpKnOyjA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hotvL46gXA8:17PxpKnOyjA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hotvL46gXA8:17PxpKnOyjA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hotvL46gXA8:17PxpKnOyjA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hotvL46gXA8:17PxpKnOyjA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/hotvL46gXA8" height="1" width="1"/&gt;</description>
	<pubDate>30 Mar 2011 19:24:47 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/hotvL46gXA8/enterprise-architecture.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content-and-analysis/resource-centers/enterprise-architecture.html</guid>
	<feedburner:origLink>http://www.cutter.com/content-and-analysis/resource-centers/enterprise-architecture.html</feedburner:origLink></item>
	<item>
	<title>Users' Conference Spurs Impressions, Questions, and Answers</title>
	<description>Rosen, Mike | E-Mail Advisors | 30 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
I attended a users' conference last week for an enterprise architecture tool. Keeping with Cutter's vendor-neutrality policy, I won't go into detail about the product, but I do want to report on my overall impressions and answer some of the common questions that I heard there.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110330.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JjZxxtXUlmM:W3eD7m_Eq1Y: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=JjZxxtXUlmM:W3eD7m_Eq1Y:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JjZxxtXUlmM:W3eD7m_Eq1Y:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JjZxxtXUlmM:W3eD7m_Eq1Y:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JjZxxtXUlmM:W3eD7m_Eq1Y:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=JjZxxtXUlmM:W3eD7m_Eq1Y:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=JjZxxtXUlmM:W3eD7m_Eq1Y:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/JjZxxtXUlmM" height="1" width="1"/&gt;</description>
	<pubDate>29 Mar 2011 18:38:56 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/JjZxxtXUlmM/ea110330.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110330.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110330.html</feedburner:origLink></item>
	<item>
	<title>The Total Solution for Integrating Architecture and Agile Teams</title>
	<description>Rosen, Mike | E-Mail Advisors | 23 March 2011 | Enterprise Architecture; Business-IT Strategies; Agile Project Management
&lt;br/&gt;&lt;br/&gt;
Agile software development and agile project management have shown considerable success in helping organizations develop better software and better manage development projects in the face of changing requirements and evolving technologies. In one sense, agile is about managing rapidly changing project factors and requirements. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110323.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ns5cOS0fygI:z_f_3SwEVno: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=Ns5cOS0fygI:z_f_3SwEVno:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ns5cOS0fygI:z_f_3SwEVno:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ns5cOS0fygI:z_f_3SwEVno:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ns5cOS0fygI:z_f_3SwEVno:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Ns5cOS0fygI:z_f_3SwEVno:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Ns5cOS0fygI:z_f_3SwEVno:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Ns5cOS0fygI" height="1" width="1"/&gt;</description>
	<pubDate>23 Mar 2011 18:27:59 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Ns5cOS0fygI/ea110323.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110323.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110323.html</feedburner:origLink></item>
	<item>
	<title>"Out Sight, Out of Mind"? Not a Solution for Aging IT Infrastructure</title>
	<description>Orr, Ken | E-Mail Advisors | 17 March 2011 | Business Technology Trends &amp; Impacts; Enterprise Risk Management &amp; Governance; Business-IT Strategies; Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In the US and in industrial countries around the world, the recent economic crisis has triggered the first serious consideration of national spending priorities for more than a decade. Supposedly, every option is being explored and unfortunately, in many cases deficits are being balanced out by reduction in long-term investments in existing infrastructure. There are a few bright spots, however. For example, in the US, President Obama has included new money for high-speed rail. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110317.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=elC9oB3w1WU:RsbCIN8Tg-4: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=elC9oB3w1WU:RsbCIN8Tg-4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=elC9oB3w1WU:RsbCIN8Tg-4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=elC9oB3w1WU:RsbCIN8Tg-4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=elC9oB3w1WU:RsbCIN8Tg-4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=elC9oB3w1WU:RsbCIN8Tg-4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=elC9oB3w1WU:RsbCIN8Tg-4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/elC9oB3w1WU" height="1" width="1"/&gt;</description>
	<pubDate>17 Mar 2011 18:16:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/elC9oB3w1WU/btt110317.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110317.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110317.html</feedburner:origLink></item>
	<item>
	<title>Total Agile Management</title>
	<description>Gat, Israel; Rosen, Mike; Glazer, Hillel | Consulting | Agile Project Management; Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Agile software development and Agile project management have shown considerable success in helping organizations develop better software and better manage development projects in the face of changing requirements and evolving technologies. In the largest sense, Agile is about managing for change.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/consulting-and-training/total-agile-management.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IVxQopucohU:sODrEXS5bwo: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=IVxQopucohU:sODrEXS5bwo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IVxQopucohU:sODrEXS5bwo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IVxQopucohU:sODrEXS5bwo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IVxQopucohU:sODrEXS5bwo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=IVxQopucohU:sODrEXS5bwo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=IVxQopucohU:sODrEXS5bwo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/IVxQopucohU" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 17:36:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/IVxQopucohU/total-agile-management.html</link>
	<guid isPermaLink="false">http://www.cutter.com/consulting-and-training/total-agile-management.html</guid>
	<feedburner:origLink>http://www.cutter.com/consulting-and-training/total-agile-management.html</feedburner:origLink></item>
	<item>
	<title>Short-Term Tactical Approaches to Application Modernization and Rationalization, Part II: Solutions</title>
	<description>Estes, Don | E-Mail Advisors | 16 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In last week's Advisor (see "Short-Term Tactical Approaches to Application Modernization and Rationalization, Part I," 9 March 2011), I provided some background about the problems associated with many legacy modernization projects. So what are the solutions offered to deal with these problems? The performance problem we attack by building a performance model of the proposed solution that we can subject to stress tests before committing to that particular design. Simple, but very rarely done.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110316.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=E0ttplvsZwU:92-boDvpV2Q: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=E0ttplvsZwU:92-boDvpV2Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=E0ttplvsZwU:92-boDvpV2Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=E0ttplvsZwU:92-boDvpV2Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=E0ttplvsZwU:92-boDvpV2Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=E0ttplvsZwU:92-boDvpV2Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=E0ttplvsZwU:92-boDvpV2Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/E0ttplvsZwU" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 17:19:26 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/E0ttplvsZwU/ea110316.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110316.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110316.html</feedburner:origLink></item>
	<item>
	<title>Performing "Heart Surgery During Marathons": Core Banking System Modernization -- Part II</title>
	<description>Simmons, Scott | Executive Updates | 16 March 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
In Part I of this Executive Update series,1 we discussed modernizing core banking systems through the analogy of heart surgery as well as the approaches I have seen as banking IT strategies evolve in this era of change in the financial industry. In particular, we covered "putting shunts" in the "patient" through application transformation and integration. In this concluding part, we look at "heart bypass" and "valve replacement" -- that is, business process management (BPM) and master data management (MDM) -- compared with the traditional (and risky) "rip and replace" approaches to modernizing core banking. So let's start the lessons on "surgery."
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1105.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=EQSXG0Snr4s:ehh8FeIPhis: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=EQSXG0Snr4s:ehh8FeIPhis:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=EQSXG0Snr4s:ehh8FeIPhis:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=EQSXG0Snr4s:ehh8FeIPhis:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=EQSXG0Snr4s:ehh8FeIPhis:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=EQSXG0Snr4s:ehh8FeIPhis:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=EQSXG0Snr4s:ehh8FeIPhis:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/EQSXG0Snr4s" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 17:01:58 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/EQSXG0Snr4s/eau1105.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1105.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1105.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Overcoming the Enterprise Risk Management Paradox</title>
	<description>Charette, Robert N. | Events | 16 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
It has been nearly twenty years since the title "Chief Risk Officer" was coined by James Lam, which itself reflected over a decade's worth of extensive thinking into how to make a holistic enterprise view of risk management practical. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-paradox.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:zb6xdTo_rR8: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=9CFrSTUonak:zb6xdTo_rR8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:zb6xdTo_rR8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:zb6xdTo_rR8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:zb6xdTo_rR8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:zb6xdTo_rR8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:zb6xdTo_rR8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CFrSTUonak" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 16:57:25 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CFrSTUonak/risk-paradox.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-paradox.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-paradox.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Overcoming the Enterprise Risk Management Paradox</title>
	<description>Charette, Robert N. | Events | 16 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
It has been nearly twenty years since the title "Chief Risk Officer" was coined by James Lam, which itself reflected over a decade's worth of extensive thinking into how to make a holistic enterprise view of risk management practical. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-paradox.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:DhjrRKcTM3o: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=9CFrSTUonak:DhjrRKcTM3o:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:DhjrRKcTM3o:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:DhjrRKcTM3o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:DhjrRKcTM3o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:DhjrRKcTM3o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:DhjrRKcTM3o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CFrSTUonak" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 19:09:33 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CFrSTUonak/risk-paradox.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-paradox.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-paradox.html</feedburner:origLink></item>
	<item>
	<title>Short-Term Tactical Approaches to Application Modernization and Rationalization, Part I</title>
	<description>Estes, Don | E-Mail Advisors | 09 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
Do you have a new development project in planning that will replace an existing application? If so, then it is likely that you are planning a legacy modernization. According to a conversation with Capers Jones, 70% of "new" application development is to replace a legacy system. The first client-server applications are more than 25 years old, and we see an increasing number of projects that have nothing to do with COBOL or mainframes, though that is still the largest category because of history and cost. We've even seen five-year-old Java systems branded "legacy." 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110309.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=F-a-gWQmyvI:UZIz1vO189U: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=F-a-gWQmyvI:UZIz1vO189U:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=F-a-gWQmyvI:UZIz1vO189U:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=F-a-gWQmyvI:UZIz1vO189U:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=F-a-gWQmyvI:UZIz1vO189U:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=F-a-gWQmyvI:UZIz1vO189U:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=F-a-gWQmyvI:UZIz1vO189U:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/F-a-gWQmyvI" height="1" width="1"/&gt;</description>
	<pubDate>9 Mar 2011 19:04:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/F-a-gWQmyvI/ea110309.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110309.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110309.html</feedburner:origLink></item>
	<item>
	<title>Reuse Maturity Model: Establishing a Software Reuse Vocabulary</title>
	<description>Sharma, Nikhil; Mutha, Mohit; Upasani, Vinay; Marsh, Lawrence | Executive Updates | 04 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
This Executive Update is mainly targeted for business executives, architects, and program managers. It provides an overview about how the most commonly debated concern about reuse benefits can be planned, measured, and quantified. The Update establishes a vocabulary that can be used by various stakeholders to report/request the reuse benefits for any development initiative or software project. It also helps architects and designers plan up front for components that can be candidates for a particular reuse.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1104.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WCJzzFwnVVg:nWJOXnsEMk4: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=WCJzzFwnVVg:nWJOXnsEMk4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WCJzzFwnVVg:nWJOXnsEMk4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WCJzzFwnVVg:nWJOXnsEMk4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WCJzzFwnVVg:nWJOXnsEMk4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=WCJzzFwnVVg:nWJOXnsEMk4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=WCJzzFwnVVg:nWJOXnsEMk4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/WCJzzFwnVVg" height="1" width="1"/&gt;</description>
	<pubDate>4 Mar 2011 18:57:39 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/WCJzzFwnVVg/eau1104.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1104.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1104.html</feedburner:origLink></item>
	<item>
	<title>Reshaping Architecture: New Organizations to Watch</title>
	<description>Rosen, Mike | E-Mail Advisors | 02 March 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Two recently formed organizations have come to my attention lately that are (or should be) of interest to architects. The first is the Federation of Enterprise Architecture Professional Organizations (FEAPO), and the second is the Business Architecture Guild (BAG).
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110302.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DtJ3vDa-JI:T2OMkvraXfg: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=2DtJ3vDa-JI:T2OMkvraXfg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DtJ3vDa-JI:T2OMkvraXfg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DtJ3vDa-JI:T2OMkvraXfg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DtJ3vDa-JI:T2OMkvraXfg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=2DtJ3vDa-JI:T2OMkvraXfg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=2DtJ3vDa-JI:T2OMkvraXfg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/2DtJ3vDa-JI" height="1" width="1"/&gt;</description>
	<pubDate>2 Mar 2011 16:30:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/2DtJ3vDa-JI/ea110302.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110302.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110302.html</feedburner:origLink></item>
	<item>
	<title>Performing "Heart Surgery During Marathons": Core Banking System Modernization -- Part I</title>
	<description>Simmons, Scott | Executive Updates | 24 February 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
The subject of this Executive Update may seem odd. I am borrowing an analogy that one of my banking clients uses to describe the requirements for transforming the company's core banking systems. They are the "cardiovascular" IT system for banks -- providing solutions that drive revenue-generating operations, such as account management, deposits, loans, and credit cards. The current core systems are largely product-oriented applications that are 20-plus years old and mainframe-based. Most lack the flexibility and impede the ability for IT to respond to new business requirements. In short, based on my numerous engagements with banking clients worldwide, we are witnessing a sustained, concerted movement for modernizing the core system. This involves the process of transforming and/or replacing these key applications. As per the title of this Update, "heart surgery" refers to the need to maintain and manage the current core banking solutions while working to transform the core system functionality.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1103.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TmTztartqlg:FIIGGQCXzzE: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=TmTztartqlg:FIIGGQCXzzE:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TmTztartqlg:FIIGGQCXzzE:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TmTztartqlg:FIIGGQCXzzE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TmTztartqlg:FIIGGQCXzzE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=TmTztartqlg:FIIGGQCXzzE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=TmTztartqlg:FIIGGQCXzzE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/TmTztartqlg" height="1" width="1"/&gt;</description>
	<pubDate>24 Feb 2011 14:12:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/TmTztartqlg/eau1103.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1103.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1103.html</feedburner:origLink></item>
	<item>
	<title>Developing a Useful Direction for Cloud Computing</title>
	<description>Baudoin, Claude R. | E-Mail Advisors | 23 February 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
For every vendor presentation claiming that cloud computing is an unprecedented revolution, there is an analyst paper denouncing the hyperbole. Every new example of IT goes through this phase, just as surely as a child goes through the "terrible twos" -- and at about the same age.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110223.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ps5WEeJKJzs:0tMpocGnwIo: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=ps5WEeJKJzs:0tMpocGnwIo:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ps5WEeJKJzs:0tMpocGnwIo:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ps5WEeJKJzs:0tMpocGnwIo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ps5WEeJKJzs:0tMpocGnwIo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ps5WEeJKJzs:0tMpocGnwIo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ps5WEeJKJzs:0tMpocGnwIo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ps5WEeJKJzs" height="1" width="1"/&gt;</description>
	<pubDate>23 Feb 2011 18:47:46 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ps5WEeJKJzs/ea110223.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110223.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110223.html</feedburner:origLink></item>
	<item>
	<title>Press Release: Stat of the Week -- Which EA framework does your organization use?</title>
	<description>Cutter Consortium | 22 February 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
EA Practice Director Mike Rosen wasn't surprised to see that many organizations use a combination of frameworks for EA. He writes, "As a general characterization of the top three frameworks, TOGAF is strong in architectural process, Zachman is strong in providing a conceptual model for thinking about the enterprise, and DoDAF/MoDAF is strong in the specification of explicit architectural deliverables (models) based on an underlying metamodel. So perhaps it not surprising that 29% of organizations have adopted a hybrid approach that combines the strength of two or three of these frameworks together." 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/press/110222.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aktDu7d9Ntw:WhVZxcB903Q: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=aktDu7d9Ntw:WhVZxcB903Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aktDu7d9Ntw:WhVZxcB903Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aktDu7d9Ntw:WhVZxcB903Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aktDu7d9Ntw:WhVZxcB903Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=aktDu7d9Ntw:WhVZxcB903Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=aktDu7d9Ntw:WhVZxcB903Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/aktDu7d9Ntw" height="1" width="1"/&gt;</description>
	<pubDate>22 Feb 2011 18:42:51 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/aktDu7d9Ntw/110222.html</link>
	<guid isPermaLink="false">http://www.cutter.com/press/110222.html</guid>
	<feedburner:origLink>http://www.cutter.com/press/110222.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Overcoming the Enterprise Risk Management Paradox</title>
	<description>Charette, Robert N. | Events | 16 March 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
It has been nearly twenty years since the title "Chief Risk Officer" was coined by James Lam, which itself reflected over a decade's worth of extensive thinking into how to make a holistic enterprise view of risk management practical. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-paradox.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:X6lLJbg6cRg: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=9CFrSTUonak:X6lLJbg6cRg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:X6lLJbg6cRg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:X6lLJbg6cRg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:X6lLJbg6cRg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:X6lLJbg6cRg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:X6lLJbg6cRg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CFrSTUonak" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 18:40:45 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CFrSTUonak/risk-paradox.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-paradox.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-paradox.html</feedburner:origLink></item>
	<item>
	<title>Too Many Applications to Deploy to Your Project? Automate Them</title>
	<description>Teti, Frank | E-Mail Advisors | 16 February 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
While IT people have a propensity to make projects out of anything, not perceiving features of an application environment in more detail, and in enough implementation detail, is a flaw in the planning process -- a rookie mistake. In many ways, technologists are obsessed with automating certain features of an application environment, but when it comes to deployment, all brainstorming seems to cease. This isn't a very enterprise-wide or Gestalt view of the world, where the "essence or shape of an entity's complete form" is understood by the application designers. In other words, an understanding of the project's coding effort, including deployment automation, should be viewed as a stiff requirement.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110216.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_JqT84jWhZA:XV-xk8R07VU: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=_JqT84jWhZA:XV-xk8R07VU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_JqT84jWhZA:XV-xk8R07VU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_JqT84jWhZA:XV-xk8R07VU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_JqT84jWhZA:XV-xk8R07VU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_JqT84jWhZA:XV-xk8R07VU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_JqT84jWhZA:XV-xk8R07VU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_JqT84jWhZA" height="1" width="1"/&gt;</description>
	<pubDate>16 Feb 2011 18:15:55 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_JqT84jWhZA/ea110216.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110216.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110216.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Overcoming the Enterprise Risk Management Paradox</title>
	<description>Charette, Robert N. | Events | 16 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
It has been nearly twenty years since the title "Chief Risk Officer" was coined by James Lam, which itself reflected over a decade's worth of extensive thinking into how to make a holistic enterprise view of risk management practical. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-paradox.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:k7ySVAneP54: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=9CFrSTUonak:k7ySVAneP54:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:k7ySVAneP54:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:k7ySVAneP54:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:k7ySVAneP54:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:k7ySVAneP54:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:k7ySVAneP54:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CFrSTUonak" height="1" width="1"/&gt;</description>
	<pubDate>11 Feb 2011 18:21:20 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CFrSTUonak/risk-paradox.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-paradox.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-paradox.html</feedburner:origLink></item>
	<item>
	<title>Information Requirements: The Missing Link Between Business and Data Architectures</title>
	<description>Rau, Ken | Executive Updates | 10 February 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
If you ask a "process owner" without prompting what specific information is required to properly execute the activities of the process for which he or she is responsible, then the process owner will rattle off a slew of items. However, any attempt to assume these items are attributes of the data architecture and assign them to entities will prove frustrating. Consider my recent interview about process modeling with a pharmaceutical marketing director responsible for consumer education and publicity about the subprocess (activity) Conduct Trade Shows:
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1102.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_SI6fFBNxEc:jkGUDHd6_18: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=_SI6fFBNxEc:jkGUDHd6_18:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_SI6fFBNxEc:jkGUDHd6_18:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_SI6fFBNxEc:jkGUDHd6_18:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_SI6fFBNxEc:jkGUDHd6_18:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_SI6fFBNxEc:jkGUDHd6_18:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_SI6fFBNxEc:jkGUDHd6_18:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_SI6fFBNxEc" height="1" width="1"/&gt;</description>
	<pubDate>10 Feb 2011 17:43:30 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_SI6fFBNxEc/eau1102.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1102.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1102.html</feedburner:origLink></item>
	<item>
	<title>Ken Olsen: Remembering a Pioneer</title>
	<description>Rosen, Mike | E-Mail Advisors | 09 February 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
I was saddened to hear that computer industry pioneer Ken Olsen, founder of Digital Equipment Corporation (DEC), died on Sunday, a few weeks shy of his 85th birthday. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110209.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=odmKkQwK0KY:R_mMKOHP2JU: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=odmKkQwK0KY:R_mMKOHP2JU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=odmKkQwK0KY:R_mMKOHP2JU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=odmKkQwK0KY:R_mMKOHP2JU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=odmKkQwK0KY:R_mMKOHP2JU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=odmKkQwK0KY:R_mMKOHP2JU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=odmKkQwK0KY:R_mMKOHP2JU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/odmKkQwK0KY" height="1" width="1"/&gt;</description>
	<pubDate>9 Feb 2011 17:23:27 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/odmKkQwK0KY/ea110209.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110209.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110209.html</feedburner:origLink></item>
	<item>
	<title>Successful Application Modernization and Rationalization: Part I -- Short-Term Tactical Approaches</title>
	<description>Estes, Don | Executive Summaries | 01 January 2011 | Enterprise Architecture
&lt;br/&gt;&lt;br/&gt;
Part I of this two-part Executive Report series by Don Estes provides a blueprint for guaranteed success in legacy modernization. The first stage of a project must reproduce the business functionality of the legacy application and pass rigorous acceptance testing validated against the legacy system. Then a second stage can provide enhanced functionality by refactoring the results of the first stage. A variety of conventional and unconventional approaches are discussed in depth with their respective pros and cons.

http://www.cutter.com/content/architecture/fulltext/reports/2011/01/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lhf1PJd84Pc:gztOvXunGf4: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=lhf1PJd84Pc:gztOvXunGf4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lhf1PJd84Pc:gztOvXunGf4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lhf1PJd84Pc:gztOvXunGf4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lhf1PJd84Pc:gztOvXunGf4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=lhf1PJd84Pc:gztOvXunGf4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=lhf1PJd84Pc:gztOvXunGf4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/lhf1PJd84Pc" height="1" width="1"/&gt;</description>
	<pubDate>1 Jan 2011 19:27:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/lhf1PJd84Pc/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/reports/2011/01/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/reports/2011/01/index.html</feedburner:origLink></item>
	<item>
	<title>C-Suite and Sour: Innovation Myth-Busting</title>
	<description>May, Thornton | E-Mail Advisors | 03 February 2011 | Innovation; Business-IT Strategies
&lt;br/&gt;&lt;br/&gt;
In a series of workshops conducted in 12 US and three European cities as well as one in Asia, I asked more than 1,500 CIOs to answer the following question: When you, your CEO, and your CFO hear the word "innovation," what is the first thing that leaps to mind?
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/innovation/fulltext/advisor/2011/iea110203.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZHiw9jfvDEw:K3ohyztm_uI: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=ZHiw9jfvDEw:K3ohyztm_uI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZHiw9jfvDEw:K3ohyztm_uI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZHiw9jfvDEw:K3ohyztm_uI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZHiw9jfvDEw:K3ohyztm_uI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ZHiw9jfvDEw:K3ohyztm_uI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ZHiw9jfvDEw:K3ohyztm_uI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ZHiw9jfvDEw" height="1" width="1"/&gt;</description>
	<pubDate>3 Feb 2011 19:08:05 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ZHiw9jfvDEw/iea110203.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/innovation/fulltext/advisor/2011/iea110203.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/innovation/fulltext/advisor/2011/iea110203.html</feedburner:origLink></item>
	<item>
	<title>To Cohere or Adhere: Objects, Relationships, and Architectures</title>
	<description>Rau, Kenneth | E-Mail Advisors | 02 February 2011 | Enterprise Architecture; Business-IT Strategies
&lt;br/&gt;&lt;br/&gt;
In designing and documenting architectures, be they business, data, application, or technology architectures, enterprise architects are prone to focus first and foreÂ­most on the objects that compose the architecture in question. This is both human nature (nouns before verbs) and a logical approach to design.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110202.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_OW0vrZz8Js:QPNJyJd217g: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=_OW0vrZz8Js:QPNJyJd217g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_OW0vrZz8Js:QPNJyJd217g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_OW0vrZz8Js:QPNJyJd217g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_OW0vrZz8Js:QPNJyJd217g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_OW0vrZz8Js:QPNJyJd217g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_OW0vrZz8Js:QPNJyJd217g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_OW0vrZz8Js" height="1" width="1"/&gt;</description>
	<pubDate>2 Feb 2011 19:05:47 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_OW0vrZz8Js/ea110202.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110202.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110202.html</feedburner:origLink></item>
	<item>
	<title>The Decision for Goodwill (and its Many Happy Returns)</title>
	<description>Pritchard, Carl | E-Mail Advisors | 26 January 2011 | Business-IT Strategies 
&lt;br/&gt;&lt;br/&gt;
"And therefore ... though it has never put a scrap of gold or silver in my pocket, I believe that it has done me good, and will do me good; and I say, God bless it!" (Charles Dickens) 

Although it may seem out of season, the quote above (from A Christmas Carol) captures the spirit of a very effective decision-making process. For those unfamiliar with the tale, the quote is made by Fred Holywell (Ebenezer Scrooge's nephew) as an impassioned plea for the charitable spirit of the holiday. But I would contend that Fred's assessment of his charity is grossly in error. In fact, I would suggest that his contention that "[t]here are many things from which I might have derived good, but by which I have not profited" is a failure to recognize a powerful business concept: the return on goodwill.
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/alignment/fulltext/advisor/2011/bit110126.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=clIBQvvfgEk:QnKWdEjosFI: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=clIBQvvfgEk:QnKWdEjosFI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=clIBQvvfgEk:QnKWdEjosFI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=clIBQvvfgEk:QnKWdEjosFI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=clIBQvvfgEk:QnKWdEjosFI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=clIBQvvfgEk:QnKWdEjosFI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=clIBQvvfgEk:QnKWdEjosFI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/clIBQvvfgEk" height="1" width="1"/&gt;</description>
	<pubDate>26 Jan 2011 18:37:54 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/clIBQvvfgEk/bit110126.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/alignment/fulltext/advisor/2011/bit110126.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/alignment/fulltext/advisor/2011/bit110126.html</feedburner:origLink></item>
	<item>
	<title>Some Steps Toward Designing Architectural Views</title>
	<description>Rosen, Mike | E-Mail Advisors | 26 January 2011 | Enterprise Architecture; Business-IT Strategies 
&lt;br/&gt;&lt;br/&gt;
In my last Advisor (see "Understand the Value Equation," 12 January 2011), I talked about the architecture value equation and the role of architectural views in creating value. To refresh your memory, the equation says that if you make it easier for someone to do their job using architecture, then theyâ€™ll use it. To achieve that requires the appropriate view. First, we need to understand what outcomes we are trying to achieve with architecture. Next, we need to understand what processes are involved (such as portfolio management, strategic planning, analysis and design, implementation) and what roles (people) are responsible for performing them. Then, we need to understand what perspective and skills the people with these roles have, and what the individual steps in the process are. Last but not least, we need to determine the steps in the process where architecture has the most leverage and opportunity to influence the outcome. Finally, we design an architectural view that supports those process steps, maximizes the leverage, and is meaningful to the person performing the process. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110126.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XKHQL2REfTU:ZCm4tixTKsM: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=XKHQL2REfTU:ZCm4tixTKsM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XKHQL2REfTU:ZCm4tixTKsM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XKHQL2REfTU:ZCm4tixTKsM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XKHQL2REfTU:ZCm4tixTKsM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=XKHQL2REfTU:ZCm4tixTKsM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=XKHQL2REfTU:ZCm4tixTKsM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/XKHQL2REfTU" height="1" width="1"/&gt;</description>
	<pubDate>26 Jan 2011 18:28:29 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/XKHQL2REfTU/ea110126.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110126.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110126.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Overcoming the Enterprise Risk Management Paradox</title>
	<description>Charette, Robert N. | Events | 16 March 2011 | Enterprise Architecture 
&lt;br/&gt;&lt;br/&gt;
In this webinar, we will take an in-depth look at where enterprise risk management has been, where it is today, and where it needs to go if it wishes to become relevant to organizations today, and more importantly, tomorrow. 
&lt;br/&gt;&lt;br/&gt;
http://www.cutter.com/events/multimedia/risk-paradox.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:5Cgk0iRjktU: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=9CFrSTUonak:5Cgk0iRjktU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:5Cgk0iRjktU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:5Cgk0iRjktU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:5Cgk0iRjktU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=9CFrSTUonak:5Cgk0iRjktU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=9CFrSTUonak:5Cgk0iRjktU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/9CFrSTUonak" height="1" width="1"/&gt;</description>
	<pubDate>16 Mar 2011 19:49:07 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/9CFrSTUonak/risk-paradox.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/risk-paradox.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/risk-paradox.html</feedburner:origLink></item>
	<item>
	<title>[Untitled]</title>
	<pubDate>26 Jan 2011 19:34:12 GMT</pubDate>
	</item>
	<item>
	<title>Green Business Process Management</title>
	<description>Unhelkar, Bhuvan | E-Mail Advisors | 20 January 2011 | Business Technology Trends &amp; Impacts 

Business process management (BPM) is a well-established industry practice encompassing process modeling, reengineering, and optimization of processes -- their measurements as well as their mergers and elimination. Green business process management (Green BPM) encompasses all of the aforementioned aspects of BPM that includes both internal and external processes of an organization from a green perspective. The premise and the promise of Green BPM is that considerable carbon savings can be achieved if an organization changes the way it does things. Such an approach does not undermine the other major carbon-reduction initiatives, such as virtualization of data servers and engendering attitude change in employees. However, similar to the lean approach to business optimization (I outlined this in one of my earlier Advisors1), the greening effort in an organization benefits highly by rearranging and reengineering the processes that include organizational activities, tasks, their sequencing, and their utility to business goals. 

http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110120.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dXd6PmAp2YM:YgJnbbLcIeU: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=dXd6PmAp2YM:YgJnbbLcIeU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dXd6PmAp2YM:YgJnbbLcIeU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dXd6PmAp2YM:YgJnbbLcIeU:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dXd6PmAp2YM:YgJnbbLcIeU:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=dXd6PmAp2YM:YgJnbbLcIeU:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=dXd6PmAp2YM:YgJnbbLcIeU:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/dXd6PmAp2YM" height="1" width="1"/&gt;</description>
	<pubDate>20 Jan 2011 19:29:31 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/dXd6PmAp2YM/btt110120.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110120.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110120.html</feedburner:origLink></item>
	<item>
	<title>Theories Help Us Understand How Software Teams Are Complex Adaptive Systems</title>
	<description>Appelo, Jurgen | E-Mail Advisors | 20 January 2011 | Agile Project Management; Enterprise Risk Management &amp; Governance 

A complex system is a system composed of interconnected parts that as a whole exhibit one or more properties (behaviors) not obvious from the properties of the individual parts. We call a complex system adaptive when its behavior changes as a result of experience.

http://www.cutter.com/content/project/fulltext/advisor/2011/apm110120.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wPvBaCNVbxY:LkYSYdhYa2A: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=wPvBaCNVbxY:LkYSYdhYa2A:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wPvBaCNVbxY:LkYSYdhYa2A:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wPvBaCNVbxY:LkYSYdhYa2A:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wPvBaCNVbxY:LkYSYdhYa2A:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=wPvBaCNVbxY:LkYSYdhYa2A:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=wPvBaCNVbxY:LkYSYdhYa2A:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/wPvBaCNVbxY" height="1" width="1"/&gt;</description>
	<pubDate>20 Jan 2011 19:25:11 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/wPvBaCNVbxY/apm110120.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/project/fulltext/advisor/2011/apm110120.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/project/fulltext/advisor/2011/apm110120.html</feedburner:origLink></item>
	<item>
	<title>Thinking About Systems, Not Programs; Databases, Not Objects</title>
	<description>Orr, Ken | E-Mail Advisors | 19 January 2011 | Enterprise Architecture; Business-IT Strategies; Business Intelligence 
Happy New Year. The last decade was certainly an interesting one, but one that I wouldn't want to relive -- too much conflict, too much hype, too little real dialog, too little data .... You get my point. My holidays were unusually busy, including a lot of travel, a lot of family, and a lot of time to think and some time to read and collect my thoughts. What I've been thinking about increasingly is that we have forgotten about the distinction between systems and programs. 
http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110119.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=I0pHv675CgE:NhED7y18oOs: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=I0pHv675CgE:NhED7y18oOs:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=I0pHv675CgE:NhED7y18oOs:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=I0pHv675CgE:NhED7y18oOs:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=I0pHv675CgE:NhED7y18oOs:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=I0pHv675CgE:NhED7y18oOs:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=I0pHv675CgE:NhED7y18oOs:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/I0pHv675CgE" height="1" width="1"/&gt;</description>
	<pubDate>19 Jan 2011 17:19:12 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/I0pHv675CgE/ea110119.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110119.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110119.html</feedburner:origLink></item>
	<item>
	<title>Is There Something Happening Here? (Yes, and Itâ€™s About Control)</title>
	<description>Kellen, Vince | E-Mail Advisors | 13 January 2011 | Business Technology Trends &amp;amp; Impacts; Business-IT Strategies; Enterprise Architecture; Business Intelligence &lt;BR&gt;&lt;BR&gt;The last decade of bubble-induced growth was book-ended by the twin events of 9/11 and the great recession. This next decade, with this recession as one of its very own bookends, looks like it might unleash demons all its own. Where this will lead isn't exactly clear. &lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110113.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LJZ1NelfPI8:QwkxVlTiYDY: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=LJZ1NelfPI8:QwkxVlTiYDY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LJZ1NelfPI8:QwkxVlTiYDY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LJZ1NelfPI8:QwkxVlTiYDY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LJZ1NelfPI8:QwkxVlTiYDY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=LJZ1NelfPI8:QwkxVlTiYDY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=LJZ1NelfPI8:QwkxVlTiYDY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/LJZ1NelfPI8" height="1" width="1"/&gt;</description>
	<pubDate>13 Jan 2011 18:32:19 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/LJZ1NelfPI8/btt110113.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110113.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2011/btt110113.html</feedburner:origLink></item>
	<item>
	<title>Intelligent Application Deployment: The Last Automation Frontier</title>
	<description>Teti, Frank | Executive Updates | 13 January 2011 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;All lifecycle methodologies initiate themselves with some concept of requirement. That is true whether they are waterfall-like, OO (e.g., RUP), or even the parsimonious agile methodology. In business applications, forward engineering usually involves further automating some back-office or mission-critical application, and the requirements for the system may be satisfied, so to speak, with a custom or package solution. In either case, the development team is usually challenged with trying to establish an understanding of the business model and how the new application will integrate with existing or other satellite applications.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1101.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=udMgpyPhAqM:qrbnDSNW6aM: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=udMgpyPhAqM:qrbnDSNW6aM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=udMgpyPhAqM:qrbnDSNW6aM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=udMgpyPhAqM:qrbnDSNW6aM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=udMgpyPhAqM:qrbnDSNW6aM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=udMgpyPhAqM:qrbnDSNW6aM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=udMgpyPhAqM:qrbnDSNW6aM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/udMgpyPhAqM" height="1" width="1"/&gt;</description>
	<pubDate>13 Jan 2011 18:23:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/udMgpyPhAqM/eau1101.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1101.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2011/eau1101.html</feedburner:origLink></item>
	<item>
	<title>An Executive Guide to Information Systems Transformation Webinar</title>
	<description>Ulrich, William M. | Webinars/Multimedia | 13 January 2011 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Do you consider information systems transformation as tactical, limited to helping enterprises achieve incremental IT productivity gains? If this is the case, your organization is likely to be missing out on a wide range of powerful business-IT transformation opportunities. Information systems transformation is delivering more strategic value than ever. &lt;BR&gt;&lt;BR&gt;Information Systems Transformation concepts offer organizations the ability to transform complex IT architectures to achieve critical business requirements. As traditional Greenfield, middleware and off-the-shelf solutions hit the wall, information systems transformation concepts have become essential to achieving synchronized and sustainable business-IT alignment. Organizations are using these concepts to enable the move to a customer centric business model, streamlining merger and acquisition deployment, and moving to more streamlined, transparent business deployments. Join us at this important webinar as William Ulrich outlines practical approaches to business-driven, IT architecture transformation using real world case studies and examples.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/webinar/2011/is-transformation.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=KIdxuCuFs8M:_2Bnd531N70: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=KIdxuCuFs8M:_2Bnd531N70:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=KIdxuCuFs8M:_2Bnd531N70:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=KIdxuCuFs8M:_2Bnd531N70:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=KIdxuCuFs8M:_2Bnd531N70:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=KIdxuCuFs8M:_2Bnd531N70:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=KIdxuCuFs8M:_2Bnd531N70:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/KIdxuCuFs8M" height="1" width="1"/&gt;</description>
	<pubDate>14 Jan 2011 18:22:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/KIdxuCuFs8M/is-transformation.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/webinar/2011/is-transformation.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/webinar/2011/is-transformation.html</feedburner:origLink></item>
	<item>
	<title>Understand the Value Equation</title>
	<description>Rosen, Mike | E-Mail Advisors | 12 January 2011 | Enterprise Architecture; Business-IT Strategies &lt;BR&gt;&lt;BR&gt;Architects face many challenges in their jobs. Among them are creating architecture and applying architecture. I've said many times that creating architecture alone does not create value. Rather, the value from architecture comes when it is applied. In other words, value is delivered when architecture is used to influence the outcome of decision making, analysis, design, or implementation. Yet another challenge is that architects are often not the people who are responsible for doing the applying. So we face a conundrum: we don't create value until someone else uses the architecture. That begs the obvious question of how to get other people to use the architecture.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110112.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oNoiCrxguy8:CYKpxrGz33g: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=oNoiCrxguy8:CYKpxrGz33g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oNoiCrxguy8:CYKpxrGz33g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oNoiCrxguy8:CYKpxrGz33g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oNoiCrxguy8:CYKpxrGz33g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=oNoiCrxguy8:CYKpxrGz33g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=oNoiCrxguy8:CYKpxrGz33g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/oNoiCrxguy8" height="1" width="1"/&gt;</description>
	<pubDate>12 Jan 2011 18:16:35 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/oNoiCrxguy8/ea110112.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110112.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110112.html</feedburner:origLink></item>
	<item>
	<title>EA New Year's Resolutions, Sixth Edition</title>
	<description>Rosen, Mike | E-Mail Advisors | 05 January 2011 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;Welcome to the sixth anniversary edition of my Enterprise Architect's "New Year's Resolutions." I hope this Advisor will give you food for thought and some inspiration for architectural growth in 2011.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110105.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gBrrveVTFsw:nfBWs7wP1ZI: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=gBrrveVTFsw:nfBWs7wP1ZI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gBrrveVTFsw:nfBWs7wP1ZI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gBrrveVTFsw:nfBWs7wP1ZI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gBrrveVTFsw:nfBWs7wP1ZI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gBrrveVTFsw:nfBWs7wP1ZI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gBrrveVTFsw:nfBWs7wP1ZI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/gBrrveVTFsw" height="1" width="1"/&gt;</description>
	<pubDate>5 Jan 2011 18:04:09 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/gBrrveVTFsw/ea110105.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110105.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2011/ea110105.html</feedburner:origLink></item>
	<item>
	<title>EA for Business Analysts: Making the Right Connections</title>
	<description>Allen, Paul | Executive Updates | 17 December 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Organizations are increasingly coming to recognize the contribution that an effective business analysis function can make to their operations. In a global environment that seems to be in a constant state of fast-moving change, business analysts have the potential to assess environmental issues and develop effective responses. An effective business architecture is required to frame these responses as part of a well-formed overall enterprise architecture (EA). At the same time, while business architecture brings much-needed structure to the party, the reality is that it often becomes decoupled from the practicalities of business analysis. It must enable business analysts with much more practical and relevant guidance than is commonly the case. For example, the business architecture needs to encourage business analysts to pay much greater attention to such factors as the organization's operating model, core context strategy, and impact analysis. This Executive Update presents some overall techniques for doing just that, helping business analysts make the right connections at the EA level.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1023.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b7hUEklUs_Q:FIWH5Slgn2U: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=b7hUEklUs_Q:FIWH5Slgn2U:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b7hUEklUs_Q:FIWH5Slgn2U:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b7hUEklUs_Q:FIWH5Slgn2U:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b7hUEklUs_Q:FIWH5Slgn2U:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=b7hUEklUs_Q:FIWH5Slgn2U:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=b7hUEklUs_Q:FIWH5Slgn2U:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/b7hUEklUs_Q" height="1" width="1"/&gt;</description>
	<pubDate>17 Dec 2010 15:10:14 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/b7hUEklUs_Q/eau1023.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1023.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1023.html</feedburner:origLink></item>
	<item>
	<title>Enterprise Architecture 2010: Part II -- EA Effectiveness</title>
	<description>Rosen, Michael | Executive Updates | 09 December 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;This is the second in a series of Executive Updates that examines enterprise architecture (EA). Part I addressed questions about the practices of EA organizations.1 This Update focuses on the perceived effectiveness of EA. Part III will look at EA programs and organization. Each is based on data from a Cutter Consortium survey conducted in the summer of 2010.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1022.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y5wO9gLHA5Y:ZpVLPh0glew: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=Y5wO9gLHA5Y:ZpVLPh0glew:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y5wO9gLHA5Y:ZpVLPh0glew:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y5wO9gLHA5Y:ZpVLPh0glew:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y5wO9gLHA5Y:ZpVLPh0glew:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=Y5wO9gLHA5Y:ZpVLPh0glew:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=Y5wO9gLHA5Y:ZpVLPh0glew:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/Y5wO9gLHA5Y" height="1" width="1"/&gt;</description>
	<pubDate>9 Dec 2010 15:09:15 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/Y5wO9gLHA5Y/eau1022.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1022.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1022.html</feedburner:origLink></item>
	<item>
	<title>Achieving Real Value-Add From Your Business-Driven Enterprise Architecture: Realizing the Void</title>
	<description>Boettger, Skip | Executive Reports | 01 July 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;In astrophysics, dark matter is responsible for the universe not flying apart, thus encouraging the growth and stability of the universe's cohesiveness and structure. In the business-driven enterprise architecture (BDEA), the "dark matter" of the BDEA is what is ultimately responsible to ensure complete integrity and cohesiveness of a true overall integrated enterprise architecture that is completely known. The dark matter of the BDEA comprises proper identification and clarification of value chains and value streams. As we explore in this Executive Report by Skip Boettger, the lack of proper attention to this dark matter creates a "void," compromising the integrity of the BDEA and making it impossible to achieve true accountable integration in the business-driven enterprise.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/architecture/fulltext/reports/2010/07/index.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hgtsSw0-ZN0:xFnsGOLj9oc: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=hgtsSw0-ZN0:xFnsGOLj9oc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hgtsSw0-ZN0:xFnsGOLj9oc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hgtsSw0-ZN0:xFnsGOLj9oc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hgtsSw0-ZN0:xFnsGOLj9oc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=hgtsSw0-ZN0:xFnsGOLj9oc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=hgtsSw0-ZN0:xFnsGOLj9oc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/hgtsSw0-ZN0" height="1" width="1"/&gt;</description>
	<pubDate>1 Jul 2010 14:46:02 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/hgtsSw0-ZN0/index.html</link>
	<guid isPermaLink="false">http://www.cutter.com/architecture/fulltext/reports/2010/07/index.html</guid>
	<feedburner:origLink>http://www.cutter.com/architecture/fulltext/reports/2010/07/index.html</feedburner:origLink></item>
	<item>
	<title>Top 5 Intriguing Enterprise Architecture Articles of 2010</title>
	<description>Coburn, Karen | E-Mail Advisors | 22 December 2010 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;This week, we're taking a look back at five of the most read articles in Cutter's Enterprise Architecture practice over this past year. Each article offers unique insight into the challenges of creating and deploying a successful enterprise architecture. Look for these lists from each of our nine practice areas for a compilation of Cutter's 45 most intriguing articles of the year. And look for the next issue of this E-Mail Advisor on 5 January.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101222.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=FziljIB5R4w:WbvrGMy1g2Q: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=FziljIB5R4w:WbvrGMy1g2Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=FziljIB5R4w:WbvrGMy1g2Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=FziljIB5R4w:WbvrGMy1g2Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=FziljIB5R4w:WbvrGMy1g2Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=FziljIB5R4w:WbvrGMy1g2Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=FziljIB5R4w:WbvrGMy1g2Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/FziljIB5R4w" height="1" width="1"/&gt;</description>
	<pubDate>22 Dec 2010 18:52:17 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/FziljIB5R4w/ea101222.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101222.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101222.html</feedburner:origLink></item>
	<item>
	<title>Security Architecture: Another Very Bad Week (or Two) for Secrets; An Even Worse Week for the Internet</title>
	<description>Orr, Ken | E-Mail Advisors | 15 December 2010 | Enterprise Architecture; Business Technology Trends &amp;amp; Impacts &lt;BR&gt;&lt;BR&gt;An old boss of mine used to say, "If you don't want your worst enemy to read it, don't write it down." I've thought of that quote often over the last week or so as the WikiLeaks fiasco has played out. A great deal of what has been leaked is venal, but not really secret. From a foreign policy standpoint, it is a bad idea to belittle counterparties with great power, but writing that stuff down is the root of all of the problems.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101215.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=R35s118VpaM:Qq4jgYHCggg: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=R35s118VpaM:Qq4jgYHCggg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=R35s118VpaM:Qq4jgYHCggg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=R35s118VpaM:Qq4jgYHCggg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=R35s118VpaM:Qq4jgYHCggg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=R35s118VpaM:Qq4jgYHCggg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=R35s118VpaM:Qq4jgYHCggg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/R35s118VpaM" height="1" width="1"/&gt;</description>
	<pubDate>15 Dec 2010 19:28:44 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/R35s118VpaM/ea101215.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101215.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101215.html</feedburner:origLink></item>
	<item>
	<title>The New Pork Belly: Buying, Selling Commodity Computing Units</title>
	<description>Kellen, Vince | E-Mail Advisors | 09 December 2010 | Business Technology Trends &amp;amp; Impacts; Business Intelligence; Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Imagine, if you will, that all owners of data centers and agents representing buyers of computing cycles get together daily and buy and sell commodity computing units (we'll call them containers) in an open exchange. Now imagine another group of buyers and sellers who are not just exchanging those containers, but buying and selling options on the containers -- the right to buy or sell those containers at a future date. This exchange would be trading the 21st-century equivalent to the pork belly. Pork bellies were introduced as a commodity in the early 1960s in the Chicago Mercantile Exchange in tradable units of 40,000 pounds.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/trends/fulltext/advisor/2010/btt101209.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k9BnQsZaLQc:8-Oh7h8bgCA: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=k9BnQsZaLQc:8-Oh7h8bgCA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k9BnQsZaLQc:8-Oh7h8bgCA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k9BnQsZaLQc:8-Oh7h8bgCA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k9BnQsZaLQc:8-Oh7h8bgCA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=k9BnQsZaLQc:8-Oh7h8bgCA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=k9BnQsZaLQc:8-Oh7h8bgCA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/k9BnQsZaLQc" height="1" width="1"/&gt;</description>
	<pubDate>9 Dec 2010 19:20:51 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/k9BnQsZaLQc/btt101209.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/trends/fulltext/advisor/2010/btt101209.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/trends/fulltext/advisor/2010/btt101209.html</feedburner:origLink></item>
	<item>
	<title>Basic Rules Unlock Keys to Event Analysis</title>
	<description>Rau, Kenneth | E-Mail Advisors | 08 December 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Event analysis is a counterintuitive but "easy to understand and use" approach for designing or redesigning processes and systems. If used consistently and extensively, it simplifies architectures, increases structural parallelism, identifies needed controls, and expedites the eventual enhancements of applications, middleware, and operating systems. Event analysis strongly complements rules-based systems, business modeling, data design, and structured analysis. In short, if you are not using event analysis in conjunction with enterprise, business, application, and technical architectures, you're doing it the hard way.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101208.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cf3yJ_Mm5RQ:r9a0O7Z5zAc: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=cf3yJ_Mm5RQ:r9a0O7Z5zAc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cf3yJ_Mm5RQ:r9a0O7Z5zAc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cf3yJ_Mm5RQ:r9a0O7Z5zAc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cf3yJ_Mm5RQ:r9a0O7Z5zAc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=cf3yJ_Mm5RQ:r9a0O7Z5zAc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=cf3yJ_Mm5RQ:r9a0O7Z5zAc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/cf3yJ_Mm5RQ" height="1" width="1"/&gt;</description>
	<pubDate>8 Dec 2010 19:18:05 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/cf3yJ_Mm5RQ/ea101208.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101208.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101208.html</feedburner:origLink></item>
	<item>
	<title>Webinar: Information Systems Transformation</title>
	<description>Ulrich, William M. | Events | 13 January 2011 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Join William Ulrich to explore practical approaches to business-driven, IT architecture transformation using real world case studies and examples.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/events/multimedia/is-transformation.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=amydW87hHe8:k1WgBx4XDqA: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=amydW87hHe8:k1WgBx4XDqA:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=amydW87hHe8:k1WgBx4XDqA:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=amydW87hHe8:k1WgBx4XDqA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=amydW87hHe8:k1WgBx4XDqA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=amydW87hHe8:k1WgBx4XDqA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=amydW87hHe8:k1WgBx4XDqA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/amydW87hHe8" height="1" width="1"/&gt;</description>
	<pubDate>6 Dec 2010 17:02:54 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/amydW87hHe8/is-transformation.html</link>
	<guid isPermaLink="false">http://www.cutter.com/events/multimedia/is-transformation.html</guid>
	<feedburner:origLink>http://www.cutter.com/events/multimedia/is-transformation.html</feedburner:origLink></item>
	<item>
	<title>Empire of Air: Making Levels of Abstraction More Concrete</title>
	<description>Rosen, Mike | E-Mail Advisors | 01 December 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Recently, I was working with some clients to create conceptual architectural models, and the discussion turned to the common levels of abstraction that we reference in architecture; namely, conceptual, logical, and physical. In the discussion, it turned out that we were skirting around a typical confusion associated with this model, and also that it would make a good topic for an Advisor.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101201.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-x-xNYn04V8:MMJ-WLoOlJM: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=-x-xNYn04V8:MMJ-WLoOlJM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-x-xNYn04V8:MMJ-WLoOlJM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-x-xNYn04V8:MMJ-WLoOlJM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-x-xNYn04V8:MMJ-WLoOlJM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=-x-xNYn04V8:MMJ-WLoOlJM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=-x-xNYn04V8:MMJ-WLoOlJM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/-x-xNYn04V8" height="1" width="1"/&gt;</description>
	<pubDate>1 Dec 2010 16:58:34 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/-x-xNYn04V8/ea101201.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101201.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101201.html</feedburner:origLink></item>
	<item>
	<title>Why Bring Agile and SOA Together?</title>
	<description>Dooley, Brian J. | E-Mail Advisors | 24 November 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Agile and service-oriented architecture (SOA) share similar goals, and both represent the current end point of lengthy processes of evolution. SOA and its concepts are derived from innumerable attempts through the years to develop reusable code and to segment individual software development projects into modules through OO programming. Agile's heritage is in innumerable attempts to make development more efficient and more likely to reach a successful business conclusion, an evolution that began in the 1970s with The Mythical Man Month.1 Agile incorporates techniques that shorten the development cycle (sprints), always produces working code, and provides aids to collaboration and transparency in operations to ensure that everyone is moving in the same direction and is able to proceed.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101124.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_lOAIQQNeus:fbvrT8OdL1s: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=_lOAIQQNeus:fbvrT8OdL1s:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_lOAIQQNeus:fbvrT8OdL1s:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_lOAIQQNeus:fbvrT8OdL1s:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_lOAIQQNeus:fbvrT8OdL1s:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=_lOAIQQNeus:fbvrT8OdL1s:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=_lOAIQQNeus:fbvrT8OdL1s:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/_lOAIQQNeus" height="1" width="1"/&gt;</description>
	<pubDate>24 Nov 2010 16:37:03 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/_lOAIQQNeus/ea101124.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101124.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101124.html</feedburner:origLink></item>
	<item>
	<title>An EA Way of Thinking</title>
	<description>Konkol, Sebastian | Executive Updates | 22 November 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Enterprise architecture (EA) is a way of thinking about the IT assets that a company possesses. It consists of various tools and is built on concepts that can be used in many ways, but the "EA way of thinking" should be applied consistently and appropriately. In a recent project, my colleagues and I applied available EA tools to assure success in the implementation and rollout of a major information system. &lt;BR&gt;&lt;BR&gt;With this Executive Update, I will share some insights about our approach -- applying an "EA way of thinking." As we all know, reality has its own plans and customs, and they usually are a bit different from ours; we will always have something to learn.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1021.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=G2Idds7t1c0:H8WKAvJDE_k: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=G2Idds7t1c0:H8WKAvJDE_k:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=G2Idds7t1c0:H8WKAvJDE_k:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=G2Idds7t1c0:H8WKAvJDE_k:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=G2Idds7t1c0:H8WKAvJDE_k:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=G2Idds7t1c0:H8WKAvJDE_k:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=G2Idds7t1c0:H8WKAvJDE_k:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/G2Idds7t1c0" height="1" width="1"/&gt;</description>
	<pubDate>22 Nov 2010 16:33:02 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/G2Idds7t1c0/eau1021.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1021.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1021.html</feedburner:origLink></item>
	<item>
	<title>Event Analysis: The Right Way to Design Processes and Systems</title>
	<description>Rau, Kenneth | Executive Updates | 19 November 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;Event analysis is a counterintuitive but "easy to understand and use" approach for designing or redesigning processes and systems. If used consistently and extensively, it simplifies architectures, increases structural parallelism, identifies needed controls, and expedites the eventual enhancements of applications, middleware, and operating systems. Event analysis strongly complements rules-based systems, business modeling, data design, and structured analysis. In short, if you are not using event analysis in conjunction with enterprise, business, application, and technical architectures, you're doing it the hard way.&lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1020.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gMLSjHd6hJQ:lkNUKFFpoJ0: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=gMLSjHd6hJQ:lkNUKFFpoJ0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gMLSjHd6hJQ:lkNUKFFpoJ0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gMLSjHd6hJQ:lkNUKFFpoJ0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gMLSjHd6hJQ:lkNUKFFpoJ0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=gMLSjHd6hJQ:lkNUKFFpoJ0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=gMLSjHd6hJQ:lkNUKFFpoJ0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/gMLSjHd6hJQ" height="1" width="1"/&gt;</description>
	<pubDate>19 Nov 2010 18:13:50 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/gMLSjHd6hJQ/eau1020.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1020.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/updates/2010/eau1020.html</feedburner:origLink></item>
	<item>
	<title>How to Measure Success: Use EA to Define Architecture</title>
	<description>Rosen, Mike | E-Mail Advisors | 17 November 2010 | Enterprise Architecture &lt;BR&gt;&lt;BR&gt;This summer, Cutter conducted a survey of EA programs with the subscribers to our Enterprise Architecture practice. Among other issues, we looked into the perceived effectiveness of EA programs. Unfortunately, the results were a little disappointing. &lt;BR&gt;&lt;BR&gt;http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101117.html&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ktN5t-ksthg:bN1Vp49goLg: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=ktN5t-ksthg:bN1Vp49goLg:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ktN5t-ksthg:bN1Vp49goLg:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ktN5t-ksthg:bN1Vp49goLg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ktN5t-ksthg:bN1Vp49goLg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?a=ktN5t-ksthg:bN1Vp49goLg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/CutterConsortiumEnterpriseArchitecture?i=ktN5t-ksthg:bN1Vp49goLg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/CutterConsortiumEnterpriseArchitecture/~4/ktN5t-ksthg" height="1" width="1"/&gt;</description>
	<pubDate>17 Nov 2010 18:07:10 GMT</pubDate>
	<link>http://feedproxy.google.com/~r/CutterConsortiumEnterpriseArchitecture/~3/ktN5t-ksthg/ea101117.html</link>
	<guid isPermaLink="false">http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101117.html</guid>
	<feedburner:origLink>http://www.cutter.com/content/architecture/fulltext/advisor/2010/ea101117.html</feedburner:origLink></item>
	</channel>
</rss>

