<?xml version="1.0"?>
<rss version="2.0">
<channel>

  
<title>Coding the Architecture - Reference Architectures</title>
<link>http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html</link>
<description> Some major architectural decisions, for a reasonable sized  project, will be made before the coding starts e.g. using an Enterprise Service Bus, data access methods, transaction handling etc. Your ability to achieve your non-functional requirements will ...</description>
<language>en</language>
<managingEditor>Robert Annett</managingEditor>
<lastBuildDate>Fri, 12 Oct 2007 08:09:00 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: Reference Architectures</title>
    <link>http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comment1200688496281</link>
    <description>
      AKA a Spike solution - http://www.extremeprogramming.org/rules/spike.html
    </description>
    <author>Javid Jamae</author>
    <comments>http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comment1200688496281</guid>
    <pubDate>Fri, 18 Jan 2008 20:34:56 GMT</pubDate>
  </item>
  
  <item>
    <title>Re: Reference Architectures</title>
    <link>http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comment1192176540747</link>
    <description>
      &lt;p&gt;In a similar manner to &lt;a href=&#034;http://www.codingthearchitecture.com/2007/06/21/the_tactical_solution.html&#034;&gt;tactical solutions&lt;/a&gt;, in my experience it is difficult to prevent the prototype from morphing into the production code.  However, in your post you imply that that the prototype should remain and be referred to during construction.  This seems a sound practice to recommend.  Particularly on an iteratively developed application - keeping the prototype for extension in subsequent build cycles strikes me as very valuable.
&lt;/p&gt;&lt;p&gt;
If you invest time in a worthwhile reference architecture, how difficult is it to keep it as a reference?  Do teams lose discipline and run with the prototype?  Do you have to watch for copy-pasters just borrowing the (not necessarily prod quality) prototype code?  I am interested in anyone&#039;s experiences of working with a reference architecture that remains distinct from the released application.&lt;/p&gt;

    </description>
    <author>Sergio Annecchiarico</author>
    <comments>http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/10/10/reference_architectures.html#comment1192176540747</guid>
    <pubDate>Fri, 12 Oct 2007 08:09:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
