Automated Code Review

Added by Megan May, last edited by Alan Berg on Jun 03, 2008  (view change)

Introduction

A method for code reviewing based on ISO 9126-1 standard.

Static code review checks off line for bug patterns. In theory if used appropriately the methodology will push up the average code quality of the target source.
See: Presentation and Magazine article and the code the code

Reports

Cleaning up

Details

SCOREBOARD

    *Note: All Java classes with the word test at the beginning or end of name are excluded from measurement (since tag 010) 
    *Note: Since 2-2-3-003 Complexity includes coupling rules.
    *Note: Since 2-3-006 Upgraded PMD 3.7 to 3.8

TAG Caught Serializable Thread Complex Unused
2-3 753 449 34 3720 1169
2-3-009 753 449 34 3720 1169
2-3-008 753 449 34 3720 1169
2-3-007 753 449 34 3718 1169
2-3-006 753 449 34 3717 1169
2-3-005 753 449 57 2183 1177
2-3-004 772 449 57 2187 1328
2-3-003 786 449 57 2187 1328
2-3-002 790 450 57 2182 1375
2-3-001 806 450 57 2185 1391
2-2-1 733 405 52 2013 1300
2-2-1-003 733 405 52 2013 1300
2-2-1-001 666 397 53 692 1266
2 2 release 769 392 56 726 1332
011 719 391 54 719 1276
010 719 391 54 719 1276
008 782 392 56 725 1329
007 795 392 56 721 1329
006 826 374 56 717 1340
005 836 374 56 715 1345
004 829 374 58 751 1383

    Caught:           Caught and not acted on
    Serializable:    Potential serializable issues
    Thread:           Thread safety
    Complexity:     Overly complex regions of code
    Unused:           Code that should be expanded or removed

Aged reports

Contact

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Jun 20, 2006

    Scott Amerson says:

    This is extremely useful information, thanks!

    This is extremely useful information, thanks!