How-to: Using Cyclomatic Compexity and LCOM4 to determine code risks

[Mike Van]

LCOM4 and Cyclomatic Complexity is a new blog posting showing users how they can use Sonar statistics to pinpoint problem areas in source-code.  Please look at it and let me know if you agree with the approach.

[Fabrice Bellingard-4]

Hi Mike,

thanks for the link, and for the blog post also!

CC and LCOM are indeed useful metrics to find which class should be refactored. 

As you're talking about Sonar as a tool to track down those metrics and identify the hot spots, maybe you could enhance your post by listing some features of Sonar that developers can use to effectively find their way in their code:

• The drilldown page to list classes/files by top CC or LCOM
• Hotspot widget, to highlight classes/files with the highest CC or LCOM
• Timeline widget, to show the evolution of both CC and LCOM on a specific resource
• And soon, a cloud widget to better and more easily find classes/files with high CC and LCOM (this one being the widget that would help the most when using your approach)

Best regards,

Fabrice BELLINGARD | SonarSource
http://sonarsource.com

On Tue, Aug 14, 2012 at 2:05 AM, Mike Van <[hidden email]> wrote:

http://os-tech.blogspot.com/2012/08/improving-code-quality-lcom4-and.html
LCOM4 and Cyclomatic Complexity  is a new blog posting showing users how
they can use Sonar statistics to pinpoint problem areas in source-code.
Please look at it and let me know if you agree with the approach.



-----
Committer, Apache Software Foundation (Kalumet)
Contributor, Apache Software Foundation (Karaf, Cellar)
--
View this message in context: http://sonar.15.n6.nabble.com/How-to-Using-Cyclomatic-Compexity-and-LCOM4-to-determine-code-risks-tp5001937.html
Sent from the Sonar user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Fabrice Bellingard-4]

For reference, the JIRA ticket for the cloud widget: http://jira.codehaus.org/browse/SONAR-3113

Best regards,

Fabrice BELLINGARD | SonarSource
http://sonarsource.com

On Tue, Aug 14, 2012 at 9:41 AM, Fabrice Bellingard <[hidden email]> wrote:

Hi Mike,

thanks for the link, and for the blog post also!

CC and LCOM are indeed useful metrics to find which class should be refactored. 

As you're talking about Sonar as a tool to track down those metrics and identify the hot spots, maybe you could enhance your post by listing some features of Sonar that developers can use to effectively find their way in their code:

• The drilldown page to list classes/files by top CC or LCOM
• Hotspot widget, to highlight classes/files with the highest CC or LCOM
• Timeline widget, to show the evolution of both CC and LCOM on a specific resource
• And soon, a cloud widget to better and more easily find classes/files with high CC and LCOM (this one being the widget that would help the most when using your approach)

Best regards,

Fabrice BELLINGARD | SonarSource
http://sonarsource.com

On Tue, Aug 14, 2012 at 2:05 AM, Mike Van <[hidden email]> wrote:

http://os-tech.blogspot.com/2012/08/improving-code-quality-lcom4-and.html
LCOM4 and Cyclomatic Complexity  is a new blog posting showing users how
they can use Sonar statistics to pinpoint problem areas in source-code.
Please look at it and let me know if you agree with the approach.



-----
Committer, Apache Software Foundation (Kalumet)
Contributor, Apache Software Foundation (Karaf, Cellar)
--
View this message in context: http://sonar.15.n6.nabble.com/How-to-Using-Cyclomatic-Compexity-and-LCOM4-to-determine-code-risks-tp5001937.html
Sent from the Sonar user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email