<?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>The Highlander Principle &#187; Business Architecture</title>
	<atom:link href="http://www.highlanderprinciple.com/category/business-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.highlanderprinciple.com</link>
	<description>One IT Architecture</description>
	<lastBuildDate>Mon, 12 Sep 2011 09:39:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Web 2.0 Architecture</title>
		<link>http://www.highlanderprinciple.com/2010/06/web-20-architecture/</link>
		<comments>http://www.highlanderprinciple.com/2010/06/web-20-architecture/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 14:50:43 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Cloud]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[saas]]></category>
		<category><![CDATA[soa]]></category>
		<category><![CDATA[web 2.0]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=69</guid>
		<description><![CDATA[<p>I have just finished reading Web 2.0 Architecture: What Entrepreneurs and Architects need to know. A rather good book which pulls together content from an awful lot of places.</p>
<p>My thinking on the topic is that Web 2.0 is a bit of a marketing type term that does not solidly define anything; here is my take [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2010/06/web-20-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Do we really need an IT Risk Control Department?</title>
		<link>http://www.highlanderprinciple.com/2009/11/do-we-really-need-a-it-risk-control-department/</link>
		<comments>http://www.highlanderprinciple.com/2009/11/do-we-really-need-a-it-risk-control-department/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 10:31:07 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=205</guid>
		<description><![CDATA[<p>In my experiences the difference between companies that have an effective risk control function and those that don’t is night and day. Businesses take risks, good businesses take measured risks. The same approach applies to the IT department.</p>
<p>A good risk controller needs to have the confidence of the business combined with complete respect from the [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/11/do-we-really-need-a-it-risk-control-department/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Windows 2008 DirectAccess and Active Directory: The Contradiction Burger</title>
		<link>http://www.highlanderprinciple.com/2009/11/windows-2008-directaccess-and-active-directory-the-contradiction-burger/</link>
		<comments>http://www.highlanderprinciple.com/2009/11/windows-2008-directaccess-and-active-directory-the-contradiction-burger/#comments</comments>
		<pubDate>Thu, 26 Nov 2009 21:59:04 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=201</guid>
		<description><![CDATA[<p>According to my good friend Martin Williams there is a take away restaurant in the North West where you can get a Vegetarian burger topped with Bacon and Cheese. It’s called the contradiction burger.</p>
<p>I think the new DirectAccess feature in Windows 2008 R2 is brilliant, however, the early documentation is a little short in terms [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/11/windows-2008-directaccess-and-active-directory-the-contradiction-burger/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DirectAccess in Windows 2008 R2 with Windows 7</title>
		<link>http://www.highlanderprinciple.com/2009/11/directaccess-in-windows-2008-r2-with-windows-7/</link>
		<comments>http://www.highlanderprinciple.com/2009/11/directaccess-in-windows-2008-r2-with-windows-7/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 07:21:31 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=195</guid>
		<description><![CDATA[<p>I remember a few years ago Microsoft created linkage between product releases (to generate cumulative sales?). I believe the trio were Exchange, Vista and Office. While the cumulative features had merit I don’t think there was a strong enough business driver.</p>
<p>So now we have a similar linkage between Windows 2008 and Windows 7. This time [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/11/directaccess-in-windows-2008-r2-with-windows-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to establish a TOGAF9 Enterprise Architecture Practice &#8211; Phase A</title>
		<link>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-a/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-a/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 17:15:31 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[All the rest]]></category>
		<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=146</guid>
		<description><![CDATA[<p>TOGAF has a method called the ADM (Architectural Development Method), the good news is that the same method applies to defining any Architecture (including setting up the Architecture Practice itself).</p>
<p>The ADM breaks down into phases that are run iteratively (not always in a set sequence). So lets get started with Phase A:</p>
<p>Phase A &#8211; Setting [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-a/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to establish a TOGAF9 Enterprise Architecture Practice &#8211; Phase B</title>
		<link>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-b/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-b/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 17:15:07 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[All the rest]]></category>
		<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=150</guid>
		<description><![CDATA[<p>TOGAF breaks down Architecture into the following pillars:</p>

Business Architecture
Application and Data Architecture
Technology Architecture

<p>Phase B on our quest to establish an EA practice focuses on Business Architecture:</p>

Terminology: Define a set of standards so that everyone is talking consistent language (formal term here is Ontology)
Process: The ADM (architectural development method) is open to be tuned to suit [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-b/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to establish a TOGAF9 Enterprise Architecture Practice &#8211; Phase C</title>
		<link>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-c/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-c/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 17:14:48 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[All the rest]]></category>
		<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=153</guid>
		<description><![CDATA[<p>TOGAF uses a term “Enterprise Continuum” and I wish they would think of a different phrase as it throws me each time. It’s important we know exactly what it is as it’s the key deliverable for Phase C.</p>
<p>It relates to three elements:</p>

Architecture Continuum
Solutions Continuum
Architecture Repository

<p>Consider the repository as a folder full of documents, the usual [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to establish an TOGAF9 Enterprise Architecture Practice &#8211; Phase D to H</title>
		<link>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-d-to-h/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-d-to-h/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 16:47:01 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[All the rest]]></category>
		<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=157</guid>
		<description><![CDATA[<p>The good news is that most of the legwork to get the ball rolling is done in phases A to C. Here is what is left:</p>
<p>Phase D: Define the technology that is used within the EA practice, ideally a TOGAF aware repository. If nothing else set standards for people to follow; for example always create [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice-phase-d-to-h/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to establish a TOGAF 9 Enterprise Architecture Practice</title>
		<link>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 20:44:29 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[All the rest]]></category>
		<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=138</guid>
		<description><![CDATA[<p>Let’s start by establishing what does an EA practice do for your organisation. The EA practice should identify</p>

Where are you?
Where do you want to be?
How do you get there?

<p>The reason the methodology is so important is that all three of these answers are always changing. The wind of change blows in for a huge array [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/how-to-establish-a-togaf9-ea-practice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is the Half Life of the IT Industry?</title>
		<link>http://www.highlanderprinciple.com/2009/10/what-is-the-half-life-of-the-it-industry/</link>
		<comments>http://www.highlanderprinciple.com/2009/10/what-is-the-half-life-of-the-it-industry/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 18:19:01 +0000</pubDate>
		<dc:creator>Mark Preston</dc:creator>
				<category><![CDATA[Application Architecture]]></category>
		<category><![CDATA[Business Architecture]]></category>
		<category><![CDATA[Management]]></category>

		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=126</guid>
		<description><![CDATA[<p>For those not into Nuclear Physics; Half Life is defined as the amount of time for the atoms in a radioactive substance to decay to half the level they started with.</p>
<p>The IT Industry may enjoy a minor boom once the effects of the global recession diminish but ultimately I suspect we are heading for a [...]]]></description>
		<wfw:commentRss>http://www.highlanderprinciple.com/2009/10/what-is-the-half-life-of-the-it-industry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

