<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-6149953344722382854.post5306688002875510873..comments</id><updated>2009-12-02T12:00:25.869-06:00</updated><title type='text'>Comments on Agility is Sensible: Why Reference Architecture(s)? (Part 1)</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.agilityissensible.com/feeds/5306688002875510873/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html'/><author><name>AAB</name><uri>http://www.blogger.com/profile/07464006705601227120</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>5</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6149953344722382854.post-1755948861345260786</id><published>2009-12-02T11:10:39.798-06:00</published><updated>2009-12-02T11:10:39.798-06:00</updated><title type='text'>For my uses, a reference architecture represents a...</title><content type='html'>For my uses, a reference architecture represents an &amp;quot;exemplar&amp;quot; for a particular category of architectures.  In other words, it combines the best practices and accepted approaches to making architectural decisions. Thus, it seems natural (at least to me) to think about different reference architectures for different uses, even within the same category.  At the same time I believe that there exist multiple views or perspectives applicable to any particular reference architecture.  These perspectives are useful for discussing the reference architectures within and between different groups. The perspectives also provide a backdrop for decision making around architectural strategies.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/1755948861345260786'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/1755948861345260786'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html?showComment=1259773839798#c1755948861345260786' title=''/><author><name>dhestand</name><uri>http://www.blogger.com/profile/16347856481245495706</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html' ref='tag:blogger.com,1999:blog-6149953344722382854.post-5306688002875510873' source='http://www.blogger.com/feeds/6149953344722382854/posts/default/5306688002875510873' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-6149953344722382854.post-4211252911745196715</id><published>2009-11-23T10:53:14.260-06:00</published><updated>2009-11-23T10:53:14.260-06:00</updated><title type='text'>I might contend that you've defined the artifacts ...</title><content type='html'>I might contend that you&amp;#39;ve defined the artifacts OF a reference architecture, but not the architecture itself. The original did indeed focus on the true elements of a reference architecture: &amp;quot;a template, based on the generalization of a set of successful solutions&amp;quot;&lt;br /&gt;&lt;br /&gt;A reference architecture is a heuristic, not an algorithm. You&amp;#39;re defining the algorithm (see the diagram http://www.fastforwardblog.com/2009/09/16/e2-0-unleashing-the-potential/)&lt;br /&gt;&lt;br /&gt;Including sample algorithms clearly helps define the potential and sharing such all together is indeed relevant, but the entire purpose of the heuristic is to extrapolate ACROSS the possible solutions.&lt;br /&gt;&lt;br /&gt;The problem with reuse, as was recommended by another commenter is that almost every solution has to make a set of assumptions that rule out other assumptions relevant to other contexts. THAT is the entire justification for reference architectures -- that the reuse is not in the pieces but in the heuristics of the pieces.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/4211252911745196715'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/4211252911745196715'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html?showComment=1258995194260#c4211252911745196715' title=''/><author><name>Paula Thornton</name><uri>http://www.blogger.com/profile/00561529494321993583</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html' ref='tag:blogger.com,1999:blog-6149953344722382854.post-5306688002875510873' source='http://www.blogger.com/feeds/6149953344722382854/posts/default/5306688002875510873' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-6149953344722382854.post-4587157483708291092</id><published>2009-11-21T23:34:39.825-06:00</published><updated>2009-11-21T23:34:39.825-06:00</updated><title type='text'>It all depends on what it's 'referring' to : )

Ac...</title><content type='html'>It all depends on what it&amp;#39;s &amp;#39;referring&amp;#39; to : )&lt;br /&gt;&lt;br /&gt;Actually the real answer is fundamentally an architectural one -- something technologists are pretty bad at. Take a page from commercial construction. A series of architectural perspectives are brought together for a total package to define the structure, infastructure, environment, interior, exterior and landscaping of a building. Each of these major areas often require different specialties.&lt;br /&gt;&lt;br /&gt;What we lack is a true guild of cross-architectural perspectives. Indeed, while Zachman was eventually persuaded to look at 6 different dimensions (the columns), his framework is a look at the 6 dimensions from a TECHICAL perspective. To be complete, Zachman&amp;#39;s Framework would need to be repeated from the perspective of each of the columns in his existing framework...extending his 2D perspective to 3D.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/4587157483708291092'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/4587157483708291092'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html?showComment=1258868079825#c4587157483708291092' title=''/><author><name>Paula Thornton</name><uri>http://www.blogger.com/profile/00561529494321993583</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html' ref='tag:blogger.com,1999:blog-6149953344722382854.post-5306688002875510873' source='http://www.blogger.com/feeds/6149953344722382854/posts/default/5306688002875510873' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-6149953344722382854.post-5882558250628446418</id><published>2009-11-20T08:38:53.008-06:00</published><updated>2009-11-20T08:38:53.008-06:00</updated><title type='text'>Matt - 

Good point on predefined structure.  It l...</title><content type='html'>Matt - &lt;br /&gt;&lt;br /&gt;Good point on predefined structure.  It lends more credence to the idea that Information Technology has its own set of structures, semi-autonomous from lines of business - a business operating model of IT, if you will.  Predefined problem solutions are nothing more than bricks and patterns.  And while a lot of organizations invest into creation of these bricks and patterns, most miss a crucial link in the value chain: a process of describing problems in a consistent way that allows for new projects to properly reuse existing investments.&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;&lt;br /&gt;AAB&lt;br /&gt;&lt;br /&gt;p.s.  My definition of fun may be slightly different, but then that is the point as well - everyone has a different perspective.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/5882558250628446418'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/5882558250628446418'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html?showComment=1258727933008#c5882558250628446418' title=''/><author><name>AAB</name><uri>http://www.blogger.com/profile/07464006705601227120</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='11687084631105462989'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html' ref='tag:blogger.com,1999:blog-6149953344722382854.post-5306688002875510873' source='http://www.blogger.com/feeds/6149953344722382854/posts/default/5306688002875510873' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-6149953344722382854.post-7365516656319946550</id><published>2009-11-19T20:16:03.749-06:00</published><updated>2009-11-19T20:16:03.749-06:00</updated><title type='text'>These endless conversations about EA definitions a...</title><content type='html'>These endless conversations about EA definitions are fun aren&amp;#39;t they? &lt;br /&gt;&lt;br /&gt;I like your definition because it does highlight the fact that you still have to ask &amp;#39;a reference architecture for what?&amp;#39;  &lt;br /&gt;&lt;br /&gt;The only thing I&amp;#39;d say is that &amp;#39;predefined problem solutions&amp;#39; isn&amp;#39;t really right in my mind.  &lt;br /&gt;&lt;br /&gt;It&amp;#39;s not that the problem solutions are predefined but rather it wouldn&amp;#39;t be a solution if it didn&amp;#39;t cover the components of the [solution] reference architecture.&lt;br /&gt;&lt;br /&gt;So a reference architecture is a predefined structure for for a specific type of architecture to fit into.... maybe</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/7365516656319946550'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6149953344722382854/5306688002875510873/comments/default/7365516656319946550'/><link rel='alternate' type='text/html' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html?showComment=1258683363749#c7365516656319946550' title=''/><author><name>Matthew</name><uri>http://www.blogger.com/profile/12199459552191461436</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agilityissensible.com/2009/10/why-reference-architectures-part-1.html' ref='tag:blogger.com,1999:blog-6149953344722382854.post-5306688002875510873' source='http://www.blogger.com/feeds/6149953344722382854/posts/default/5306688002875510873' type='text/html'/></entry></feed>