<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - coverage tag</title>
  <link>http://www.codingthearchitecture.com/tags/coverage/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Wed, 16 May 2012 08:01:04 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Code Metrics</title>
    <link>http://www.codingthearchitecture.com/2006/12/15/code_metrics.html</link>
    
      
      
        <description>
          &lt;p&gt;There&#039;s nothing particularly new about code metrics but they perhaps have an increasing relevance as development teams become geographically and ideologically separated from those charged with code quality and an increasing degree of freedom is granted to Agile development teams which should be both monitored and publicised.&lt;/p&gt;
&lt;p&gt;In this article I&#039;ll discuss my recent experiences with metrics ranging from simple line counts to complexity, duplication and test coverage.&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.codingthearchitecture.com/2006/12/15/code_metrics.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>How do you deliver software architecture?</category>
    
    <comments>http://www.codingthearchitecture.com/2006/12/15/code_metrics.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/12/15/code_metrics.html</guid>
    <pubDate>Fri, 15 Dec 2006 13:40:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

