<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Maintainability Index Range and Meaning</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx</link><description>Another question: The maintainability index has been re-set to lie between 0 and 100. How and why was this done? The metric originally was calculated as follows (based on the work in Carnegie Mellon University although we modified the Halstead Volume</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Daily Dose of Links - 20071121 &amp;laquo; Daily Geek Bits</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6455324</link><pubDate>Wed, 21 Nov 2007 16:20:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6455324</guid><dc:creator>Daily Dose of Links - 20071121 « Daily Geek Bits</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://alvinashcraft.wordpress.com/2007/11/21/daily-dose-of-links-20071121/"&gt;http://alvinashcraft.wordpress.com/2007/11/21/daily-dose-of-links-20071121/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Maintainability Index Range and Meaning</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6456333</link><pubDate>Wed, 21 Nov 2007 17:46:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6456333</guid><dc:creator>redsolo</dc:creator><description>&lt;p&gt;Why dont you consider unit testing coverage to be a part of the maintability index? A method can be complex but as long as there are unit tests for it, it is much simpler to maintain.&lt;/p&gt;
</description></item><item><title>Izindaba #19</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6478017</link><pubDate>Fri, 23 Nov 2007 08:06:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6478017</guid><dc:creator>From the software development trenches</dc:creator><description>&lt;p&gt;Time for another weekly round-up of developer news that focuses on .NET, agile and general development&lt;/p&gt;
</description></item><item><title>re: Maintainability Index Range and Meaning</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6552872</link><pubDate>Tue, 27 Nov 2007 18:20:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6552872</guid><dc:creator>Jeff</dc:creator><description>&lt;p&gt;Can you please compare in a few words what's the main difference between the &amp;quot;Analyze&amp;quot; menu, to other 3rd party source code analysis tools (Checkmarx, RATS, LINT, etc...)?&lt;/p&gt;
&lt;p&gt;Does the analysis engine provide data flow analysis?&lt;/p&gt;
&lt;p&gt;Is it possible to add custom metrics (locs per funcs ...)?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Jeff&lt;/p&gt;
</description></item><item><title>VSTS Links - 11/28/2007</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6579569</link><pubDate>Wed, 28 Nov 2007 17:28:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6579569</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;The Visual Studio Code Analysis Team Blog on Maintainability Index Range and Meaning. Willy-Peter Schaub...&lt;/p&gt;
</description></item><item><title>re: Maintainability Index Range and Meaning</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6601419</link><pubDate>Thu, 29 Nov 2007 22:18:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6601419</guid><dc:creator>conorm</dc:creator><description>&lt;p&gt;In answer to some of the questions posted:&lt;/p&gt;
&lt;p&gt;Q: Does the analysis engine provide data flow analysis?&lt;/p&gt;
&lt;p&gt;A: No, at this time we do not perform true data flow analysis. &amp;nbsp;We are looking at that for a future version.&lt;/p&gt;
&lt;p&gt;Q: Is it possible to add custom metrics?&lt;/p&gt;
&lt;p&gt;A: Not at this time, see &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/fxcop/archive/2007/11/15/code-metrics-customization.aspx"&gt;http://blogs.msdn.com/fxcop/archive/2007/11/15/code-metrics-customization.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Maintainability Index Range and Meaning</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6601469</link><pubDate>Thu, 29 Nov 2007 22:23:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6601469</guid><dc:creator>conorm</dc:creator><description>&lt;p&gt;Q: Why dont you consider unit testing coverage to be a part of the maintability index? A method can be complex but as long as there are unit tests for it, it is much simpler to maintain.&lt;/p&gt;
&lt;p&gt;A: I like the idea of including unit test coverage in a metric although I don't necessarily buy the idea that code with more tests is more maintainable. Low maintainability suggests high cyclomatic and computational complexity (halstead volume) which means there are a lot of paths and a lot of operators. &amp;nbsp;If you make a change to that code which requires new tests and changes existing tests then you have to work out what the appropriate changes are, work out what the new tests should cover (and make sure they do), validate that the test results are correct etc. &amp;nbsp;All of which is more work and more potential for error (including false passes).&lt;/p&gt;
</description></item><item><title>Determining Code Complexity</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#6792619</link><pubDate>Tue, 18 Dec 2007 00:49:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6792619</guid><dc:creator>Are you thinking what I'm thinking?</dc:creator><description>&lt;p&gt;Having inherited a lot of code in past lives as a development lead or dev manager, determining code complexity&lt;/p&gt;
</description></item><item><title>Полезные ссылки 15.01.2007</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#7116361</link><pubDate>Tue, 15 Jan 2008 09:48:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7116361</guid><dc:creator>Віктор Шатохін [MSFT]</dc:creator><description>&lt;p&gt;Чем отличается Visual Studio 2008 Standard Edition от Visual Studio 2008 Professional Edition &lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/en-us/vs2008/products/bb980920.aspx"&gt;http://msdn2.microsoft.com/en-us/vs2008/products/bb980920.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Hay cosas inútiles, cosas totalmente inútiles y Métricas de Código (sobre todo para desarrollo con SharePoint)</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#8837233</link><pubDate>Wed, 06 Aug 2008 15:54:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8837233</guid><dc:creator>SkunkWorks</dc:creator><description>&lt;p&gt;Todos tenemos de esas cosas que nos enervan... cuando empieza a llover (y nos mojamos) en un d&amp;#237;a de sol&lt;/p&gt;
</description></item><item><title>Hay cosas inútiles, cosas totalmente inútiles y Métricas de Código (sobre todo para desarrollo con SharePoint)</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#8837234</link><pubDate>Wed, 06 Aug 2008 15:55:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8837234</guid><dc:creator>SkunkWorks</dc:creator><description>&lt;p&gt;Todos tenemos de esas cosas que nos enervan... cuando empieza a llover (y nos mojamos) en un d&amp;#237;a de sol&lt;/p&gt;
</description></item><item><title>Know your tools better: Questions from Attendees</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#8965681</link><pubDate>Fri, 26 Sep 2008 01:30:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8965681</guid><dc:creator>Fuziness and Cognizance... </dc:creator><description>&lt;p&gt;Virtual Tech Days day one, session one. I delivered a talk titled &amp;amp;quot;know your tools better&amp;amp;quot;.&lt;/p&gt;
</description></item><item><title>Code Metrics</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#9067136</link><pubDate>Thu, 13 Nov 2008 22:27:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9067136</guid><dc:creator>Babu George's Blog</dc:creator><description>&lt;p&gt;One of the challenges, I always faced was the availability of approaches for quantification of the aspects&lt;/p&gt;
</description></item><item><title>Should Code Metrics stress me out?</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#9186602</link><pubDate>Tue, 09 Dec 2008 10:30:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9186602</guid><dc:creator>Willy-Peter Schaub's Cave of Chamomile Simplicity</dc:creator><description>&lt;p&gt;In&amp;amp;#160; &lt;a rel="nofollow" target="_new" href="http://dotnet.org.za/willy/archive/2007/09/17/code-metrics-unraveling-what-it-all-means.aspx"&gt;http://dotnet.org.za/willy/archive/2007/09/17/code-metrics-unraveling-what-it-all-means.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Visual Studio Team System 2008 Development Edition with MSDN Premium Subscription</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#9399290</link><pubDate>Thu, 05 Feb 2009 20:48:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9399290</guid><dc:creator>Termékinformációk fejlesztőknek</dc:creator><description>&lt;p&gt;[ Nacsa S&amp;#225;ndor , 2009. janu&amp;#225;r 19. – febru&amp;#225;r 5.] Ez a Team System v&amp;#225;ltozat fejlett eszk&amp;#246;zrendszert k&amp;#237;n&amp;#225;l&lt;/p&gt;
</description></item><item><title>Métriques de VS2008</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#9476360</link><pubDate>Sat, 14 Mar 2009 20:47:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9476360</guid><dc:creator>Gabriel Mongeon</dc:creator><description>&lt;p&gt;Voici un article bien d&amp;#233;taill&amp;#233; expliquant le fonctionnement de Code Metrics de Visual Studio 2008. Et leur explication de leur calcul de l'indice de maintanibilit&amp;#233; bas&amp;#233;e sur la formule d'Halstead&lt;/p&gt;
</description></item><item><title>Code Metrics</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/20/maintainability-index-range-and-meaning.aspx#9486960</link><pubDate>Wed, 18 Mar 2009 17:33:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9486960</guid><dc:creator>Microsoft UK Developer Tools Team</dc:creator><description>&lt;p&gt;My first blog entry and it’s just a quick one; I’ve been curious about exactly how the code metrics in&lt;/p&gt;
</description></item></channel></rss>