So you want to be a Rockstar in your team
Then listen now to what I say
Just get Understand
analyzer
Then take some time and learn how to play
Am sure this is how The Byrds would endorse
this tool. Recently, I ran some trials with the tool and was very impressed
with the visuals that they provide and spread of static code analysis they have
to offer.
Typically, we would expect the following 3
essentials from a static code analysis tool:
(1) Lines of code
(2) Cyclometric complexity
(3) Inter-dependencies of the various elements
Following are the charts that the tool provides
as a first cut analysis of your code base:
(1) Directory structure based on LOC
(2.1) Most complex functions / classes / files based on McCabe Cyclometric Metrix
(2.2)
Largest functions / classes / files (3) Inter-dependencies between various elements
Equipped with such a graphical overview, team architects can get a broad understanding of the system and then drill down further with the tool to identify the potential key areas that needs refactoring. Highly recommended for the Architecture Runaway owner in your team!
Reference:
(1) https://www.scitools.com/
(2) Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code: Alan MacCormack, John Rusnak, Carliss Baldwin
No comments:
Post a Comment