Agile FAQs
  About   Slides   Home  

 
Managed Chaos
Naresh Jain’s Random Thoughts on Software Development and Adventure Sports
     
`
 
Discovering...
Industrial Logic

Microblog Feed
    Previous Feeds...
    Recent Thoughts

    Mob Programming
    Mob Programming
    Daily Scrum Simulation
    Daily Scrum Simulation
    Recent Comments
    Categories
    Archives
    March 2010
    M T W T F S S
    « Feb    
    1234567
    891011121314
    15161718192021
    22232425262728
    293031  
    RSS Feed
    Add to Technorati Favorites

    Another Project Rescue Report

    Monday, February 9th, 2009

    Some time back, I spent 1 Week helping a project (Server written in Java) clear its Technical Debt. The code base is tiny because it leverages lot of existing server framework to do its job. This server handles extremely high volumes of data & request and is a very important part of our server infrastructure. Here are some results:

    Topic Before After
    Project Size Production Code

    • Package =1
    • Classes =4
    • Methods = 15 (average 3.75/class)
    • LOC = 172 (average 11.47/method and 43/class)
    • Average Cyclomatic Complexity/Method = 3.27

    Test Code

    • Package =0
    • Classes = 0
    • Methods = 0
    • LOC = 0
    Production Code

    • Package = 4
    • Classes =13
    • Methods = 68 (average 5.23/class)
    • LOC = 394 (average 5.79/method and 30.31/class)
    • Average Cyclomatic Complexity/Method = 1.58

    Test Code

    • Package = 6
    • Classes = 11
    • Methods = 90
    • LOC =458
    Code Coverage
    • Line Coverage: 0%
    • Block Coverage: 0%

    Old Code Coverage Report

    • Line Coverage: 96%
    • Block Coverage: 97%

    New Code Coverage Report

    Cyclomatic Complexity

    Cyclomatic Complexity report before Refactoring

    Cyclomatic Complexity report after Refactoring

    Obvious Dead Code Following public methods:

    • class DatabaseLayer: releasePool()

    Total: 1 method in 1 class

    Following public methods:

    • class DFService: overloaded constructor

    Total: 1 method in 1 class

    Note: This method is required by the tests.

    Automation
    Version Control Usage
    • Average Commits Per Day = 0
    • Average # of Files Changed Per Commit = 12
    • Average Commits Per Day = 7
    • Average # of Files Changed Per Commit = 4
    Coding Convention Violation 96 0

    Another similar report.

    • Share/Bookmark

    Project Rescue Report

    Monday, February 2nd, 2009

    Recently I spent 2 Weeks helping a project clear its Technical Debt. Here are some results:

    Topic Before After
    Project Size Production Code

    • Package = 7
    • Classes = 23
    • Methods = 104 (average 4.52/class)
    • LOC = 912 (average 8.77/method and 39.65/class)
    • Average Cyclomatic Complexity/Method = 2.04

    Test Code

    • Package = 1
    • Classes = 10
    • Methods = 92
    • LOC = 410
    Production Code

    • Package = 4
    • Classes = 20
    • Methods = 89 (average 4.45/class)
    • LOC = 627 (average 7.04/method and 31.35/class)
    • Average Cyclomatic Complexity/Method = 1.79

    Test Code

    • Package = 4
    • Classes = 18
    • Methods = 120
    • LOC = 771
    Code Coverage
    • Line Coverage: 46%
    • Block Coverage: 43%

    Coverage report before Refactoring

    • Line Coverage: 94%
    • Block Coverage: 96%

    Coverage report after refactoring

    Cyclomatic Complexity

    Cyclomatic Complexity report before Refactoring

    Cyclomatic Complexity report after Refactoring

    Obvious Dead Code Following public methods:

    • class CryptoUtils: String getSHA1HashOfString(String), String encryptString(String), String decryptString(String)
    • class DbLogger: writeToTable(String, String)
    • class DebugUtils: String convertListToString(java.util.List), String convertStrArrayToString(String)
    • class FileSystem: int getNumLinesInFile(String)

    Total: 7 methods in 4 classes

    Following public methods:

    • class BackgroundDBWriter: stop()

    Total: 1 method in 1 class

    Note: This method is required by the tests.

    Automation
    Version Control Usage
    • Average Commits Per Day = 1
    • Average # of Files Changed Per Commit = 2
    • Average Commits Per Day = 4
    • Average # of Files Changed Per Commit = 9

    Note: Since we are heavily refactoring, lots of files are touched for each commit. But the frequency of commit is fairly high to ensure we are not taking big leaps.

    Coding Convention Violation 976 0

    Something interesting to watch out is how the production code becomes more crisp (fewer packages, classes and LOC) and how the amount of test code becomes greater than the production code.

    Another similar report.

    • Share/Bookmark
        Licensed under
    Creative Commons License
    Design by vikivix