anthropics / beam
Goals & Controls

Traffic lights for selected metrics.

Intro
Learn more...
  • For more insights in the value of trend analysis, Sokrates recommends reading the section "Explicitly link metrics to goals" in the article An Appropriate Use of Metrics, (MartinFowler.com), e.g.:
    • "We would like our code to be less complex and easier to change. Therefore we should aim to write short methods (less than 15 lines) with a low conditional complexity (less than 20 is good). We should also aim to have a small handful of parameters (up to four) so that methods remain as focused as possible."
Keep the system simple and easy to change
Aim at keeping the system size modest (less than 200,000 LOC is good), duplication low (less than 5% is good), files small (no files longer than 1000 LOC is good), and units simple (no units with more than 25 decision points is good).
Status Metric Desired Range
[from - to] ±tolerance		 Current Value Description
FAILED LINES_OF_CODE_MAIN [0 - 200000] ±20000 802,493 Total number of lines of main code
IGNORED: the metric not found DUPLICATION_PERCENTAGE [0 - 5] ±1 - System duplication
FAILED VERY_HIGH_RISK_FILE_SIZE_COUNT [0 - 0] ±1 92 The number of very large files
FAILED CONDITIONAL_COMPLEXITY_VERY_HIGH_RISK_COUNT [0 - 0] ±1 16 Number of very complex units