<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Enterprise Architecture in Higher Education &#187; taxonomy</title>
	<atom:link href="http://leodesousa.ca/tag/taxonomy/feed/" rel="self" type="application/rss+xml" />
	<link>http://leodesousa.ca</link>
	<description>a practical approach by Leo de Sousa</description>
	<lastBuildDate>Sun, 29 Jan 2012 21:45:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Is it really &#8220;Zachman&#8217;s Fatal Flaw&#8221;?</title>
		<link>http://leodesousa.ca/2010/07/is-it-really-zachmans-fatal-flaw/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=is-it-really-zachmans-fatal-flaw</link>
		<comments>http://leodesousa.ca/2010/07/is-it-really-zachmans-fatal-flaw/#comments</comments>
		<pubDate>Mon, 12 Jul 2010 17:06:13 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[strategic planning]]></category>
		<category><![CDATA[capability maturity model]]></category>
		<category><![CDATA[taxonomy]]></category>
		<category><![CDATA[zachman]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=952</guid>
		<description><![CDATA[My friend Nick Malik wrote a post - Zachman&#8217;s Fatal Flaw: No Row for Customer.  Here is my response &#8230; Do I believe that Zachman&#8217;s Framework is fatally flawed?  No. It all depends on your perspective and that to me is defined by your EA maturity.  How we view and evaluate models and frameworks depends <a href='http://leodesousa.ca/2010/07/is-it-really-zachmans-fatal-flaw/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2010/07/is-it-really-zachmans-fatal-flaw/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>What good looks like &#8230; follow-up</title>
		<link>http://leodesousa.ca/2009/05/what-good-looks-like-follow-up/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=what-good-looks-like-follow-up</link>
		<comments>http://leodesousa.ca/2009/05/what-good-looks-like-follow-up/#comments</comments>
		<pubDate>Tue, 26 May 2009 02:40:37 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[application]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[guiding principles]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[solutions architecture]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=288</guid>
		<description><![CDATA[Alan Inglis posted about What good looks like from a solutions architecture perspective.  How do you create a solution for a new project without creating architecture that already exists or making the same mistakes that previous projects made? This is a must read post and I recommend it. Alan described 10 artefacts that he would expect <a href='http://leodesousa.ca/2009/05/what-good-looks-like-follow-up/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2009/05/what-good-looks-like-follow-up/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Making E2AF Accessible</title>
		<link>http://leodesousa.ca/2009/02/making-e2af-accessible/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=making-e2af-accessible</link>
		<comments>http://leodesousa.ca/2009/02/making-e2af-accessible/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 22:57:44 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=232</guid>
		<description><![CDATA[My EA colleague Mike Kavis posted a &#8220;Free E2AF Cheat Sheet&#8221; for all of us to leverage. Thanks Mike! For those of you who don&#8217;t know Mike has been leveraging the E2AF to build out the enterprise architecture of his startup company.  Following Mike in his journey using a  &#8221;learning lab&#8221; for EA has been insightful and <a href='http://leodesousa.ca/2009/02/making-e2af-accessible/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2009/02/making-e2af-accessible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thinking about frameworks and geometry</title>
		<link>http://leodesousa.ca/2009/01/think-about-frameworks-and-geometry/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=think-about-frameworks-and-geometry</link>
		<comments>http://leodesousa.ca/2009/01/think-about-frameworks-and-geometry/#comments</comments>
		<pubDate>Fri, 16 Jan 2009 02:30:05 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[taxonomy]]></category>
		<category><![CDATA[zachman]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=49</guid>
		<description><![CDATA[Mike Kavis&#8216; got me thinking about EA frameworks with his Twitter posts about the E2AF. The Zachman Framework was my first introduction to an EA framework in 2004 and it continues to be a significant reference model for how I think about EA. Here is a slide of the Zachman Framework Version 2.  The geometry of Zachman sits in one and <a href='http://leodesousa.ca/2009/01/think-about-frameworks-and-geometry/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2009/01/think-about-frameworks-and-geometry/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Application Portfolio Concepts</title>
		<link>http://leodesousa.ca/2007/06/application-portfolio-concepts/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=application-portfolio-concepts</link>
		<comments>http://leodesousa.ca/2007/06/application-portfolio-concepts/#comments</comments>
		<pubDate>Wed, 27 Jun 2007 15:35:03 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=16</guid>
		<description><![CDATA[We have just completed the second update of our Application Portfolio. The results are very interesting. I want to thank all the IT Services staff who contributed to making this piece of our EA real! Here is a table with some of the significant changes from November 2006 to May 2007: Attribute Nov 2006 May <a href='http://leodesousa.ca/2007/06/application-portfolio-concepts/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2007/06/application-portfolio-concepts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EA Model V.2</title>
		<link>http://leodesousa.ca/2007/06/ea-model-v2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ea-model-v2</link>
		<comments>http://leodesousa.ca/2007/06/ea-model-v2/#comments</comments>
		<pubDate>Sat, 23 Jun 2007 06:36:15 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[it governance]]></category>
		<category><![CDATA[itsm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[taxonomy]]></category>
		<category><![CDATA[zachman]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=13</guid>
		<description><![CDATA[Two years ago, Dave Cresswell and I came up with a graphic to represent Enterprise Architecture @ BCIT. We needed a simple graphic to communicate EA and also knew that showing our senior Executive the Zachman Framework was too complex. Here is first draft EA model: and Version 1 : At that point, I was <a href='http://leodesousa.ca/2007/06/ea-model-v2/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2007/06/ea-model-v2/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Enterprise Architecture Taxonomy</title>
		<link>http://leodesousa.ca/2007/06/enterprise-archtiecture-taxonomy/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=enterprise-archtiecture-taxonomy</link>
		<comments>http://leodesousa.ca/2007/06/enterprise-archtiecture-taxonomy/#comments</comments>
		<pubDate>Tue, 19 Jun 2007 23:21:27 +0000</pubDate>
		<dc:creator>Leo de Sousa</dc:creator>
				<category><![CDATA[enterprise architecture]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://leodesousa.ca/?p=10</guid>
		<description><![CDATA[Here is the taxonomy I use for categorizing the EA artifacts we create. Comments? Enterprise Architecture Taxonomy (Element-Domain-Component-Artifact) Architecture Element The high level architectural description for Applications, Business, Business Continuity, Data, Infrastructure, Presentation and Security containing Architecture Domains. (i.e. An element contains domains) Architecture Domain The summary level of architecture describing the models used for <a href='http://leodesousa.ca/2007/06/enterprise-archtiecture-taxonomy/'>[...]</a>]]></description>
		<wfw:commentRss>http://leodesousa.ca/2007/06/enterprise-archtiecture-taxonomy/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

