<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx</link><description>I have to write an overview on "What is architecture" for an upcoming website that we are working on and so went out to look at some definitions. The first I remembered was one I used in an old overview of Enterprise Architecture that I wrote in 2002</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423330</link><pubDate>Tue, 28 Mar 2006 10:22:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423330</guid><dc:creator>Richard Veryard</dc:creator><description>I like the fact that you define architecture not as an artefact (organization, representation, description, structure) but as a practice (the use of ...).&lt;br&gt;&lt;br&gt;So when you refer to future architectures, I hope this means future architectural directions and practices, and not just future artefacts.</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423424</link><pubDate>Wed, 29 Mar 2006 00:11:32 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423424</guid><dc:creator>soccerdad</dc:creator><description>I would change it slightly:&lt;br&gt;&lt;br&gt;&amp;quot;...abstractions, models, and industry best practices...&amp;quot;.&lt;br&gt;&lt;br&gt;A key element of architecture is to apply lessons from past projects. In the civil engineering world, especially, it's important not to reinvent the wheel when well-defined requirements and best practices have been established.</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423454</link><pubDate>Wed, 29 Mar 2006 06:51:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423454</guid><dc:creator>Michael Platt</dc:creator><description>Agree totally, learning from history is something we do far too little of in IT.&lt;br&gt;&lt;br&gt;ike</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423462</link><pubDate>Wed, 29 Mar 2006 09:15:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423462</guid><dc:creator>Alan Bell</dc:creator><description>I like it - it does what it describes to the long winded 8&amp;#172;) wording below, abstracts it to simplify and communicate, and leaves me with a picture in my mind of what Architecture is all about.</description></item><item><title>The Definition of </title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423511</link><pubDate>Wed, 29 Mar 2006 17:23:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423511</guid><dc:creator>CraigBlog</dc:creator><description /></item><item><title>Do Architects Design?</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423531</link><pubDate>Wed, 29 Mar 2006 19:54:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423531</guid><dc:creator>Michael Platt's WebLog </dc:creator><description>Of course they do!! Craig blogged about my architecture definition and said that my definition didn't...</description></item><item><title>What is an Architect?</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423538</link><pubDate>Wed, 29 Mar 2006 20:42:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423538</guid><dc:creator>Michael Platt's WebLog </dc:creator><description>Arrgh, yet again I have been drawn into the &amp;amp;quot;what is an architect&amp;amp;quot; discussion! I knew it was a mistake...</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423667</link><pubDate>Thu, 30 Mar 2006 22:06:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423667</guid><dc:creator>Mike</dc:creator><description>I found quite a good definition of what a software architect has to do in the audio commentary of one of the Lord of the Rings movies. Peter Jackson described how the script always changed just days or hours before shooting and he compared the script writers to someone who &amp;quot;ferociously lays down tracks in front of a running train&amp;quot;.&lt;br&gt;&lt;br&gt;Software architects must ensure that their train (software project) goes in the right direction by laying down the tracks, that it stays on the rails and that it arrives at the destination in time. Passengers (programmers, managers, ...) have to feel comfortable and safe. The train should run smoothly, even in hard weather.&lt;br&gt;&lt;br&gt;Mike</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423674</link><pubDate>Fri, 31 Mar 2006 00:06:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423674</guid><dc:creator>Michael Platt</dc:creator><description>Like that!&lt;br&gt;Mike</description></item><item><title>re: What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423855</link><pubDate>Sat, 01 Apr 2006 06:50:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423855</guid><dc:creator>Peter Bakker</dc:creator><description>For me an architecture is a mix of a science, engineering and marketing. First an architect must understand why there is some kind of a problem. &amp;nbsp;Then an architect must understand how to solve the problem and how to implement the solution. And last but not least the architect must promote and sell the outcome of the previous stages and predict new trends.&lt;br&gt;&lt;br&gt;So, your short version definition fits rather well! I maybe would add a goal part by adding for example:&lt;br&gt;&lt;br&gt;Architecture is the use of abstractions and models to simplify and communicate complex structures and processes to improve understanding, implementation and forecasting. </description></item><item><title>Agile Cases  &amp;raquo; Blog Archive   &amp;raquo; Michael Platt&amp;#8217;s WebLog : What is Architecture: a Definition</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423856</link><pubDate>Sat, 01 Apr 2006 07:02:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423856</guid><dc:creator>Agile Cases  » Blog Archive   » Michael Platt’s WebLog : What is Architecture: a Definition</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://www.agilecases.com/2006/04/01/michael-platts-weblog-what-is-architecture-a-definition/"&gt;http://www.agilecases.com/2006/04/01/michael-platts-weblog-what-is-architecture-a-definition/&lt;/a&gt;</description></item><item><title> 
Linkblog for Friday, 31 March, 2006 &amp;raquo;  
Chandrasekhar Vallabhaneni 
 
</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#423908</link><pubDate>Sun, 02 Apr 2006 11:02:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423908</guid><dc:creator> 
Linkblog for Friday, 31 March, 2006 »  
Chandrasekhar Vallabhaneni 
 
</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://www.chanduonline.com/2006/03/31/linkblog-for-friday-31-march-2006/"&gt;http://www.chanduonline.com/2006/03/31/linkblog-for-friday-31-march-2006/&lt;/a&gt;</description></item><item><title>IBM on Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2006/03/27/423300.aspx#425445</link><pubDate>Mon, 17 Apr 2006 20:45:28 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425445</guid><dc:creator>Michael Platt's WebLog </dc:creator><description>&amp;amp;amp;nbsp;What is a software architecture? &amp;amp;amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://www-128.ibm.com/developerworks/rational/library/feb06/eeles/index.html"&gt;http://www-128.ibm.com/developerworks/rational/library/feb06/eeles/index.html&lt;/a&gt;...</description></item></channel></rss>